[06:49] <arand> how can I add another package to a newly created bug report: Bug #391949
[06:50] <wgrant> arand: "Also affects distribution...". Or do you want to change it to a different package, removing the old one?
[06:55] <arand> wgrant: I'd like to add nvidia-glx-96 along with current -71 as affected.
[06:57] <arand> Ah, figured it now, a bit odd to go for distro when I'm only adding anothe pkh
[07:53] <savvas> Is this error known on launchpad code? I see a piece of coding above the header: https://code.edge.launchpad.net/unetbootin/trunk http://img222.imageshack.us/img222/7985/screenshotznp.png
[07:56] <lifeless> looks like java script
[07:56] <wgrant> savvas: There have been about 7 bugs filed about that so far.
[07:56] <lifeless> and it doesn't show up for me
[07:56] <lifeless> try hitting ctrl-F5
[07:57] <wgrant> lifeless: You're an ~admin.
[07:57] <wgrant> It's only shown if you don't have launchpad.Edit on the series.
[07:57] <lifeless> wgrant: ah
[07:57] <lifeless> wgrant: thanks :)
[08:04] <savvas> thanks wgrant :)
[10:55] <drizztbsd> hi
[10:55] <drizztbsd> i have a problem :)
[10:58] <drizztbsd> The following source cannot be copied: dhcpcd 1:3.2.3-4~drizzt1 in karmic (a different source with the same version is published in the destination archive)
[10:58] <drizztbsd> but in https://launchpad.net/~timothy-redaelli/+archive/ppa i have not dhcpcd
[10:58] <wgrant> drizztbsd: Not even an old deleted one?
[10:58] <drizztbsd> yes, i have an old deleted one
[10:59] <wgrant> That would do it.
[10:59] <drizztbsd> should i wait some times to make the system purge?
[10:59] <wgrant> The error message is slightly wrong, but it means pretty much what it says.
[10:59] <drizztbsd> or should i make a (useless) version bump?
[10:59] <wgrant> I'm pretty sure you'll never be able to have a source with the same version, because of the confusion that will cause.
[11:00] <wgrant> Why is the version bump useless?
[11:00] <drizztbsd> ok. thanks. i will do a version bump
[11:00] <wgrant> It's a different package, isn't it?
[11:03] <wgrant> noodles775: Ahhhh, I'm glad the package pages are finally get redesigned.
[11:04] <noodles775> wgrant: you don't miss much do you ;). If you've got thoughts and suggestions, please add them!
[11:04] <noodles775> wgrant: sorry for the scant notes... I just created the page to upload the photos...
[11:05] <wgrant> noodles775: What's that table on the DSPR page?
[11:05]  * noodles775 looks
[11:06] <wgrant> I don't see how the tick/cross makes sense.
[11:06] <wgrant> Oh, are those representing the build status?
[11:08] <noodles775> wgrant: yes, trying to summarise all the binaries produced by the DSPR (and their states)
[11:08] <noodles775> Grr... forgot that f-spot doesn't rotate the original image...
[11:11] <wgrant> noodles775: I strongly dislike F-Spot's approach at dealing with photos.
[11:12] <wgrant> noodles775: Back to the build status... it's surely an implementation detail that the -doc is arch-all, and the build status is DAS-wide, so why show it in each row?
[11:12] <wgrant> I'd put a download link there, not a build status icon.
[11:15] <noodles775> wgrant: I thought that was what the dashes in intrepid-amd64/jaunty-lpia were indicating?
[11:17] <wgrant> noodles775: They make sense if it's a build status matrix.
[11:17] <wgrant> But the build statuses don't need to be represented in a matrix.
[11:18] <noodles775> wgrant: other thoughts on how could you summarise all the relevant information?
[11:19] <wgrant> noodles775: So, I'd put the build status in the header, next to the DAS name. The ticks/crosses/dashes then get replaced with download or DASBPR:+index links, with the -doc package's intrepid/amd64 and jaunty/lpia columns somehow indicating that they are special.
[11:25] <noodles775> wgrant: I don't see how you could put the status in the header without collapsing multiple statuses (and hence not seeing which build failed etc.), but I'm probably not visualising your thoughts well...
[11:25] <noodles775> if you've got a minute markup the image in gimp and I'll upload your version to the page too.
[11:25] <noodles775> (sorry, *you* can upload your version :) )
[11:25] <wgrant> noodles775: Sure.
[11:26] <noodles775> thanks!
[11:27] <wgrant> But there's only one Build per DAS on that page, so there's only one status per DAS, so there should be no problem with putting it in each column header.
[11:27] <wgrant> But let me attack it with GIMP.
[11:28] <wgrant> noodles775: Ah, actually, that image is rotated. But Firefox doesn't respect the EXIF data. I smell a bug.
[11:28] <noodles775> aha!
[11:37]  * wgrant waits for slow Australian uploads...
[11:38] <noodles775> heh
[11:38] <wgrant> noodles775: https://dev.launchpad.net/SoyuzPackageUI?action=AttachFile&do=get&target=package_release_details_wgrant.jpg
[11:38] <wgrant> Those squares are my realistic imitations of the LP binary package icons.
[11:38] <wgrant> And the lighter ones are my badly thought out way to represent that they're not really from that build.
[11:41] <wgrant> (those package icons are links to the DASBPR)
[11:44] <noodles775> bigjools: Regarding wgrant's mockup-suggestion above... do you remember why we needed to display the status in each row... I remember there being lots of discussion around that matrix display, but can't remember why?
[11:44] <wgrant> I thought there must have been a reason for it.
[11:44] <wgrant> But I can't see why... it's all or nothing, apart from arch-indeps.
[11:44] <noodles775> Yeah, I'm pretty sure there was, but can't remember...
[11:46] <noodles775> beuno might have some thoughts too... I think he was keen for download links there too from memory ^^^
[11:47] <wgrant> I'm torn over whether to give a view or download link. Maybe both, since the series name in the column header should make it wide enough.
[11:49] <wgrant> I guess if you don't link to the DASBPR view, you have to find some other place to link to it. That could be awkward.
[11:51] <noodles775> Unless it's possible to display/pull-in the relevant info in the drill-down for the binary?
[11:52] <wgrant> I guess.
[11:52] <wgrant> Speaking of that... how do you plan to do that?
[11:52] <wgrant> There are several possible choices for which data to show there.
[11:52] <wgrant> As the BPRs from different DASs don't have to be anything like each other.
[11:53] <noodles775> huh? It's all generated from the one source package right?
[11:53] <wgrant> Yes.
[11:54] <wgrant> But the binary information is generated by the source, not encoded in it.
[11:54] <wgrant> They should generally be pretty similar, but dependencies often differ.
[11:54] <noodles775> Just dependencies? or other things too?
[11:55] <wgrant> Anything can. But not much does.
[11:55] <noodles775> I guess it's a matter of (1) what is most useful for the user, while also (2) what is possible within the constraints
[11:55] <noodles775> aha
[11:56] <wgrant> It would be really nice if the data model was simple, with one build per architecture and all binary data matching. But that's not how things work :(
[11:58] <noodles775> Yup.
[13:49] <scut_tang> jml: hey. It seems my branch is banned?
[13:49] <scut_tang> jml: I am robin
[14:13] <salgado> scut_tang, I don't think jml is around at this time.  maybe I could help you?
[14:20] <bjsnider> how about adding support for html in ppa descriptions?
[14:23] <salgado> bjsnider, what exacly do you want HTML for?  just to add some hyperlinks or something else?
[14:23] <bjsnider> styling
[14:24] <bjsnider> maybe links
[14:24] <bjsnider> even just bold/italic/underline would be nice
[14:25] <salgado> that sounds feasible.  what do you think about that, bigjools?
[14:25]  * bigjools reads scrollback
[14:25] <bigjools> yes, it would be nice
[14:26] <bigjools> we could support a limited subset of HTML
[14:26] <wgrant> I think there are more appropriate markup languages.
[14:26] <bigjools> please file a bug
[14:27] <bigjools> please file a bug saying you need markup, without specifying HTML :)
[14:27] <bjsnider> if i get html i can proceed to the next step: world domination
[14:27] <bigjools> James Bond would win
[14:27] <wgrant> bigjools: While you're here... did you see noodles775's question earlier?
[14:28] <bigjools> sort of but I am missing a bunch of context
[14:28] <bjsnider> you all know to much now. i'll have to do something about that
[14:28] <wgrant> bigjools: Why does https://dev.launchpad.net/SoyuzPackageUI?action=AttachFile&do=get&target=package_release_details.jpg have all of the statuses split out?
[14:29] <wgrant> Rather than something like https://dev.launchpad.net/SoyuzPackageUI?action=AttachFile&do=get&target=package_release_details_wgrant.jpg
[14:31] <bigjools> I don't remember
[14:31] <bigjools> that was drawn up nearly 5 months ago!
[14:31] <wgrant> Oh, I see.
[14:32] <bigjools> I'm kinda busy with other stuff right now, can you ping me next week and I'll re-read stuff over the weekend
[14:32] <wgrant> Sure. Thanks.
[14:35] <bigjools> wgrant: any of your input would be great though, we're implementing this stuff after we open source
[14:42] <bjsnider> someone suggested using Markdown in bug 30002, which is a different bug than mine but a similar request
[14:42] <wgrant> bigjools: Although nobody seems to actually know exactly what is happening and when with regard to open sourcing any more...
[14:42] <bigjools> wgrant: why do you say that?
[14:43] <wgrant> bigjools: All the concrete dates have been removed from the wiki, August is cited as a possibility, and things change every few days.
[14:45] <bigjools> wgrant: well check with kfogel if you have questions, he's the person who edits that page
[14:46] <wgrant> bigjools: Thanks.
[14:46] <wgrant> kfogel: Around?
[15:24] <scut_tang> salgado: I am sorry to reply to you so late.
[15:24] <salgado> scut_tang, no worries
[15:27] <scut_tang> salgado: My situation is so complicated. jml knows more about that. Do you know when does he have time?
[15:28] <salgado> scut_tang, later today, probably. right now it's quite late on his side
[15:34] <scut_tang> salgado: OK, thank you ~
[16:45] <kfogel> wgrant: hey
[17:33] <mxpxpod> if the subversion structure has changed for a project that is being mirrored on launchpad, how do I change the URL?
[18:18] <mxpxpod> when I register a release URL pattern, can it have more than one * in it?
[18:32] <beuno> sinzui, ^
[18:37] <sinzui> mxpxpod: No, only one pattern. I believe there is a bug requesting support for multiples. The pattern is very flexible you can provide a general one that can match a lot of urls
[18:37] <mxpxpod> sinzui: I'm trying to match http://downloads.dojotoolkit.org/release-1.3.x/release-1.3.x-src.tar.gz
[18:38] <mxpxpod> sinzui: so I kind of need multiple *'s
[18:43] <sinzui> mxpxpod The is a regular expression, a python one.
[18:43] <mxpxpod> sinzui: oh, you can use regexps?
[18:43] <sinzui> mxpxpod:  The example is showing .*, and the code certainly is a Python RE
[18:45] <sinzui> http://downloads.dojotoolkit.org/release-1.3\..*/release-1.3\..*-src.tar.gz is overly precise. '.' is both in the name and in the pattern So the match is fuzzier than the explaination appears
[18:45] <mxpxpod> ah
[18:46] <mxpxpod> and how often are those checked?
[18:47] <sinzui> mxpxpod: I think the productreleasefinder extracts a safe place to start crawling pages, and it if find a link that patches that pattern, it downloads the file and attaches it to the series
[18:48] <mxpxpod> sinzui: so, you have to have the series already created?
[18:48] <sinzui> mxpxpod: it runs twice a day, but it is batched. A site should be scanned a couple times a week
[18:48] <mxpxpod> wait, that's not what I mean
[18:49] <mxpxpod> will it attach the files it finds to a release already created? or will it create releases for you?
[18:49] <sinzui> mxpxpod: series (where you set the url pattern) -> milestone -> release.
[18:49] <sinzui> The PRF will create the milestone if it does not find it.
[18:49] <mxpxpod> ah, cool
[18:49] <sinzui> mxpxpod: that too. It makes milestones and release as needed
[18:50] <sinzui> mxpxpod: The PRF has been borked for a few weeks A fill fix will land early next week
[18:52] <mxpxpod> sinzui: thank you
[19:12] <savvas> can someone fix the "Read about uploading" link to https://help.launchpad.net/Packaging/PPA#Uploading  instead of "PPA/Uploading"? The wiki page https://help.launchpad.net/Packaging/PPA/Uploading redirects to the first page, but as https://help.launchpad.net/Packaging/PPA#Uploading?action=show&redirect=Packaging%2FPPA%2FUploading and doesn't go to the bookmark #Uploading in firefox 3
[19:13] <savvas> (next to "Upload packages" at e.g. https://edge.launchpad.net/~medigeek/+archive/ppa )
[19:15] <matsubara> savvas, could you file a bug for that and I'll ask mrevell to take a look for the next release?
[19:15] <savvas> on my way :)
[19:15] <savvas> matsubara: against launchpad project?
[19:16] <savvas> I mean.. file the bug for launchpad project
[19:16] <matsubara> savvas, btw, add to the bug report that the link only appear to the owner of the PPA
[19:16] <matsubara> savvas, yep, file on launchpad and I'll take on from there
[19:17] <savvas> ok I'll let you know :)
[19:20] <matsubara> thanks savvas
[19:21] <fta> lol, debugging code visible in edge
[19:22] <fta> http://www.sofaraway.org/ubuntu/tmp/yui-lp.png
[19:23] <matsubara> fta, it's fixed and will be re-rolled tomorrow
[19:23] <matsubara> fta, bug 391594
[19:23] <savvas> matsubara: bug 392239
[19:24] <fta> ok
[19:24] <matsubara> thanks savvas
[19:24] <savvas> sure, anytime!
[19:29] <alkisg> In my PPA (https://launchpad.net/~ts.sch.gr/+archive/ppa) I have a package (sch-scripts - 9.04.6) which displays both "published" and "build status: building" - is this normal?
[19:30] <matsubara> alkisg, it shows up as published for me
[19:31] <alkisg> matsubara: I see the "building" icon in the "Build Status" column, and it doesn't display up with apt-get update... :(
[19:32] <alkisg> I tried refreshing the browser cache or using a different browser - I don't think it's a caching issue
[19:34] <matsubara> alkisg, can you file a bug on soyuz <https://launchpad.net/soyuz/+filebug> and attach a screenshot?
[19:34] <alkisg> matsubara: sure, thanks
[19:34] <matsubara> alkisg, thank you
[19:41] <alkisg> matsubara: https://bugs.launchpad.net/soyuz/+bug/392244 - thanks again
[19:42] <matsubara> thanks alkisg
[19:47] <mxpxpod> is there a way to move a project to another URL?
[19:48] <salgado> mxpxpod, you mean changing the last (the project's name) part of the URL?
[19:48] <mxpxpod> salgado: yes
[19:49] <salgado> mxpxpod, yes, that's possible but that would cause existing links to break
[19:49] <salgado> mxpxpod, what's the project you want to rename, and what would it be renamed to?
[19:50] <mxpxpod> salgado: oh, I was just wondering if it can be done
[19:53] <salgado> mxpxpod, ok, I asked because we can also add aliases to projects, so one project could have two different URLs
[19:54] <mxpxpod> oh, cool
[19:55] <mxpxpod> the reason I ask is that at the dojo toolkit, we're looking at hosting methods... but we have kind of a strange set up... dojo and the dojo utilities are part of the "core", which means they should be under the "dojo" project in launchpad
[19:56] <mxpxpod> but from what I can see, I can only register one thing with a project in dojo
[19:56] <mxpxpod> does that make sense?
[19:57] <salgado> mxpxpod, by project you mean a project group?
[19:57] <mxpxpod> I think so
[19:57] <salgado> mxpxpod, do you know what's the distinction between a project and a project group?
[19:58] <mxpxpod> I think so... firefox is a project, mozilla is the project group
[19:58] <salgado> yeah, that's it.
[19:58] <mxpxpod> so, it sounds like I need a "dojotoolkit" project group
[19:58] <salgado> that's what I was going to suggest
[20:00] <mxpxpod> how do I go about creating a project group?
[20:00] <salgado> mxpxpod, you need to request it at https://launchpad.net/launchpad/+addquestion
[20:00] <salgado> and then one of the admins will create it for you
[20:06] <mxpxpod> salgado: thank you
[20:09] <mxpxpod> salgado: now, I just wait? ;)
[20:13] <salgado> mxpxpod, yes. I'll assign it to the admins and you'll get an email once they've dealt with it
[20:21] <Irunongames> help
[20:21] <Irunongames> i need to make someone a admin
[20:22] <Irunongames> on my launchpad
[20:42] <bdmurray> Is there a limit to how many official tags that would display for a project?
[20:45] <beuno> bdmurray, off the top of my head, no
[21:00] <kfogel> wgrant: I just sent a mail to launchpad-users@ about the flexibility in the open-sourcing date.
[23:24] <SoulBlade> is there a preferred way to host a .zip file on launchpad?  it's basically a tgz and prebuilt binaries of source, so i dont really want to put it in with the source branch...
[23:25] <RAOF> SoulBlade: Throw it in the Downloads section?
[23:25] <SoulBlade> ooh a downloads section
[23:25] <SoulBlade> didnt even know there was one
[23:25] <SoulBlade> <-- not smart
[23:25] <thewrath> hey all
[23:28] <SoulBlade> err where do i go to actually upload the file?
[23:31] <SoulBlade> ah nm
[23:35] <lamalex> does anyone know the name of the project for code hosting on lp?
[23:35] <lamalex> i want to file a bug
[23:36] <RAOF> launchpad-code
[23:36] <RAOF> https://bugs.edge.launchpad.net/launchpad-code
[23:37] <lamalex> thanks RAOF
[23:42] <Kangarooo> can i ask question on launchpad and in where if question is about installing neatbeans and ruby on rails so i can programm RoR with Netbeans but in Ubuntu/Linux but with Canonical recomendet way/maintained way. So with apt-get or synaptic.
[23:49] <wgrant> beuno: Should I still assign CSS sprite bugs to you immediately?
[23:57] <thewrath> hey guys i am using cygwin and bzr
[23:57] <thewrath> but cygwin does not know how to handle ssh conenctions