[00:45] steveire: it will if the version in backports has a name newer than it [00:45] e.g. 1.1.10-1ubuntu1 or newer [00:46] jamesh: Is that consistent with backports naming schemes? [00:46] steveire: I don't know [00:46] you'd have to check Ubuntu's policies [00:46] It seems to be. Current latest in gutsy is 1.1.8-2ubuntu2~gutsy1 [00:46] I think they usually make sure they have a version number less than the package they've backported === kiko-afk is now known as kiko-zzz === barry is now known as barry-away === mars is now known as vednis === vednis is now known as mars === `23meg_ is now known as mgunes [03:26] New bug: #191732 in launchpad-bazaar "Branch summaries are incongruous on project Code page" [Undecided,New] https://launchpad.net/bugs/191732 === asac_ is now known as asac [05:26] Huh, weird. I'm reporting a bug, and just got "A summary is required" even though I entered a summary. And now I can't reproduce it. Very odd. [05:46] spiv: maybe you should provide a summary [05:47] jamesh: I tried that :) [05:47] In the end, it turns out the bug was already reported anyway. [06:04] im not sure i like this personalization that some LP mailing lists apparently use [06:18] pwnguin: Barry's post? It wasn't a mailing list post (although it was about mailing lists) [06:21] * Fujitsu presumes it's using some secret method of emailing all members of a team, which the rest of the world would love but can't have. [06:26] Fujitsu: mail merge [06:26] Fujitsu: it's a feature of Microsoft Word [06:26] if you are using Outlook, it works really well [06:26] heh [06:27] its rather annoying, as i presume its intended specifically for me [06:27] and requires some direct action hidden somewhere inside that wall of text =( [06:31] jamesh: Using some public datasource like +rdf? I presumed there might be some magic that was used to email even those who hid their email addresses, which would be very useful. [06:31] Fujitsu: it probably did use private data, yes. [06:32] So yes, it does use some secret method :( [06:32] but now we've got mailing lists we could use a less secret method ... [06:33] Doesn't one have to opt into mailing lists? [06:33] yeah [06:34] it would make sense to have a beta testers announce list though [06:34] One of the more recent needs I've seen for this feature was actually to tell people to join a mailing list. It was eventually done by abusing Malone. [06:34] It would, definitely. [08:43] morning === carlos_ is now known as carlos [09:56] How would someone define Launchpad in few words? [09:58] Syntux: a website to help manage free software projects [09:58] danke [09:59] the great source code supermarket! [10:24] hey folks [10:24] how exactly would branch removal work? :) [10:25] * pygi did read FAQ, yes, and there's no Delete branch magic as suggested there [10:28] pygi: It works, except if it has subscribers or is linked to anything else like a bug or blueprint. [10:28] Fujitsu, it doesn't have them: https://code.edge.launchpad.net/~mario-danic/+junk/mainline/ [10:33] pygi: I can't see why you can't delete that. [10:33] It meets all the requirements that I know of. [10:33] Fujitsu, perhaps because it's set as a branch for libisofs regardless of the thing that I removed it from a project? [10:34] it's weird, but oh well [10:34] Any update on the pending approval for bluez-gnome translation template. [10:34] pygi: I have delete buttons for things on various projects. [10:35] I believe there is meant to be a fix for this (the lack of indication as to what's stopping you from deleting it) soon. [10:35] then it's just weird [10:37] pygi: you can't delete a branch if it has any bug<->branch or blueprint<->branch links or is the main branch of any project release series [10:37] pygi: if you remove the links, etc, you can delete the branch [10:39] Ah, that's it. [10:39] It's the trunk for libisofs. [10:39] But that's not shown on the branch page. [10:40] Fujitsu, yes, I told you that above =) [10:40] but when I remove it from the project, ie. make it not be a branch of libisofs, the libisofs project still tracks it [10:40] I thought you just meant it was assigned to that project, not the trunk. [10:40] Try now. [10:40] Oh, bah. [10:41] Why does LP give me permission to see +source when I'm not allowed to do anything on it? [10:42] * pygi will try to go around the need to delete it with bzr upgrade magic [10:42] pygi: You need an admin or the owner of the project to remove the reference on https://launchpad.net/libisofs/trunk/+source. [10:43] ah, right, I forgot I wasnt the admin [10:43] will solve that soon :) [10:45] thanks for help Fujitsu [11:06] New bug: #191797 in launchpad-bazaar "+source shouldn't trick me into thinking I can change things" [Undecided,New] https://launchpad.net/bugs/191797 === barry-away is now known as barry [12:16] question: I have build the PPA in the team pages (http://launchpad.net/~libdc1394-dev) but the http://launchpad.net/libdc1394 project page doesn't have PPA and the link to the source package: https://edge.launchpad.net/ubuntu/hardy/+source/libdc1394-22 says that blah blah There is no current release of this source package in The Hardy Heron.... [12:16] how do you get that PPA build in the project page? [12:16] how do you link it there? [12:16] Fujitsu, I managed to do it, thank you jamesh as well :) [12:21] anyone here able to answer those questions? [12:22] cprov "elp!" [12:24] theseinfeld: you can't link projects & PPA in LP yet, I suggest you to add a link in the project description for now. [12:24] cprov alrighty then [12:24] cprov thank you again! [12:25] theseinfeld: np [12:25] how do you change the source package name? [12:26] for example: https://edge.launchpad.net/libdc1394/+distributions it shows 7.10 as libdc1394v2 as it should be libdc1394-22 [12:26] is this a bug? [12:26] :D [12:31] theseinfeld: It's not a bug. Links between packages and projects are maintained manually by various people. [12:31] thank you Fujitsu [12:32] Hm, there's no way to delete that link, unfortunately. [12:32] It's not published in Gutsy, so there's no delete button [12:34] yes [12:35] so, Fujitsu, that will be there forever? [12:35] :D [12:35] Or until I get around to filing a bug and someone fixes it. [12:36] That would be nice [12:36] Thank you Fujitsu === kiko-zzz is now known as kiko [12:53] hey Fujitsu, good to see you [13:36] Hello everyone. You may have seen me in here asking this question before, but I have now deterimined that the either 1) the PPAquickstart guide is wrong or 2) the distro override feature has not been implimented (even for beta testers) yet. [13:36] The passage from the PPA guide is as follows: You can use PPA to build sources from other distributions that use .deb packages. [13:36] Upload to ~/ubuntu/ and the suite you specify will override the suite named in the upload changelog. You can upload a source from any Debian-compatible distribution straight to your PPA with no changes required. [13:38] I have done a diff only upload to two targets via dput, the only difference between the two being one has ~rexbron/ubuntu/gutsy as the incomming and the gutsy package still get rejected due to the MD5 sums matching an existing package [13:38] Perhaps I should file a bug report? [13:40] rexbron: Give me a second, let me see if I can find someone to answer your question. [13:40] :) [13:42] rexbron: you have upload a diff for a orig that doesn't match the one published in ubuntu archive. [13:42] rexbron: download the ubuntu orig and re-generate the diff, it will all work. [13:43] cprov, this is for packages that are not in the ubuntu archives [13:43] rexbron: I don't see how exactly this error is related with the changesfile-override feature. [13:43] cprov, let me see if I can explain it better [13:44] rexbron: in this case the diff/dsc doesn't match the orig that you have uploaded to your PPA [13:44] cprov, but they do [13:44] my gutsy upload is being rejected due to the distro serise being listed as hardy [13:45] cprov, Here is the exact error message for the gutsy upload: [13:45] Rejected: [13:45] The source openlibraries - 0.4.0.svn20080111-0ubuntu1~ppa3 is already accepted in [13:45] ubuntu/hardy and you cannot upload the same version within the same distribution. [13:45] You have to modify the source version and re-upload. [13:46] rexbron: so, it's not a checksum error, as you've said. [13:46] it was uploaded via dput with an incomming listed as ~rexbron/ubuntu/gutsy [13:46] rexbron: that's simple, you can't have the same version uploaded twice to the same archive. [13:47] the checksums match, but the distro serise has not been changed [13:47] rexbron: it says "version X is already accepted in hardy", thus you can't not upload it again to gutsy. [13:48] cprov, could you look at https://help.launchpad.net/PPAQuickStart specifically the "using sources from other distrobutions" section and tell me if that works? [13:48] cprov, if it is a case that one must upload gutsy before hardy (makes sense from the distro pov but not so much from a ppa one) then the documentation makes no reference to that fact [13:49] rexbron: ubuntu, debian, xandros, etc are distributions ... dapper, gutsy, hardy are distroseries. You [13:49] 've got tricked by the changesfile field name [13:50] cprov, fine, then it is a misunderstand on my part, but I still think that it would be a logical extention of that feature. woud it not? [13:51] rexbron: the natural logic-extension is to allow users to copy-packages within their PPAs [13:51] rexbron: that's what we do in ubuntu primary archive [13:52] rexbron: do a single upload and copy source and/or binaries to other distroseries [13:52] Sure, that is what I am after [13:56] Hey, anyone wanna help push a Launchpad story on Digg? Take a look at http://digg.com/linux_unix/Launchpad_s_source_code_supermarket/ === statik` is now known as statik === mrevell is now known as mrevell-lunch [14:55] https://launchpad.net/ubuntu/hardy/+package/devscripts how do I report a bug against that? [14:57] CarlFK, launchpad.net/ubuntu/+filebug [14:57] then choose devscripts in the package chooser [14:57] then go! [14:58] gah. should I report a lp bug? [14:58] why? [14:58] why isn't there a link from the package page to the report a bug on this package? [14:58] CarlFK, if it's about that page not having a bugs facet, it's already reported [14:58] that page is a disaster [14:58] that would be why :) === salgado is now known as salgado-lunch === kiko is now known as kiko-fud === matsubara is now known as matsubara-lunch [15:26] New bug: #191852 in launchpad "Don't redirect http://lists.launchpad.net to the help wiki" [Undecided,New] https://launchpad.net/bugs/191852 [15:27] can someone look into adding a translation template for paprefs https://bugs.launchpad.net/ubuntu/+source/paprefs/+bug/191854 ? :] [15:27] Launchpad bug 191854 in paprefs "Translation template unavailable for paprefs" [Undecided,New] [15:28] carlos, my man, hi. Long time no see. Will you look into this please? :] === salgado-lunch is now known as salgado [15:58] TomaszD: hi === fabbione is now known as thegodfather === matsubara-lunch is now known as matsubara [16:10] http://thedailywtf.com/Articles/Manual-JIRA-.aspx [16:13] carlos, hello [16:28] how do you register a release for a package that you are responsible, but your are not a member of the motu team etc.? [16:28] see https://edge.launchpad.net/ubuntu/hardy/+source/libdc1394-22/+builds for reference... === carlos_ is now known as carlos [16:36] TomaszD: Hi, I cannot do anything about paprefs [16:37] TomaszD: it's a package from universe, so the only way to get your translation added to the package is that an ubuntu developer adds it directly to the package [16:37] carlos, how can I get a dev to include it? [16:38] TomaszD: basically what you did should be enough [16:38] ok [16:38] If you don't see any action, you could try at #ubuntu-devel to see whether any developer is able to handle that bug for you... [16:39] ok, I'll pester them [16:46] * theseinfeld is alone [16:48] theseinfeld: what's bothering you ? [16:50] cprov hehe... the slowness of the revu process? and incapacity to fix some launchpad issues :) [16:50] theseinfeld: the fact we present https://edge.launchpad.net/ubuntu/hardy/+source/libdc1394-22 can be considered a bug itself. I'm working a solution for this. [16:50] like the thing with the source [16:50] cpro the libdc1394-22 is one thing, but worse is the libdc1394v2 showing there :( [16:51] theseinfeld: I can't comment about revu ... but I can help you with LP [16:51] s/cpro/cprov/ [16:51] yeah... the beauty of revu :) [16:51] * theseinfeld loves when getting attention from cprov [16:52] theseinfeld: currently all known source-names are traversable, including PPA ones. We simply present the warning about the lack of publications in the specific context, which is causing confusion. [16:53] cprov btw, in PPA if I delete some source packages, they are still in the repository [16:53] cprov i guess I should submit a bug report to get them clean from the PPA? [16:53] theseinfeld: my guess is that https://edge.launchpad.net/ubuntu/+source/libdc1394-22 is also coming from a PPA [16:54] nope, cprov, I added it myself...don't ask how though, cause I don't remember. The v2 is coming from PPA [16:54] cprov can you clear the PPA for me? or should I fill a bug report? [16:54] theseinfeld: no, deletions will be executed 24 hours after the references to the files in question reach 0 [16:54] there are many packages that are there and they could be deleted as they are absolete [16:54] cprov hmm [16:55] cprov who is referencing those files? [16:55] * theseinfeld is wondering... [16:55] theseinfeld: did you re-use the orig in the subsequent uploads ? [16:56] I uploaded new orig with the 2.0.2 from SVN [16:56] theoretically, cprov, the old one should be clean to be removed... [16:56] if you go here though: https://edge.launchpad.net/~libdc1394-dev/+archive?field.name_filter=&field.status_filter=superseded [16:56] cprov you see a long list of packages dating from 2.0.0 [16:57] they show deleted, but they were still in the ppa.launchpad last time when I checked [16:57] cprov: yep, check this out: http://ppa.launchpad.net/libdc1394-dev/ubuntu/pool/main/libd/libdc1394v2/ [16:59] cprov if you can explain why this is there, you will solve a big mystery for me [17:00] **** launchpad meeting in #launchpad-meeting in t-1h [17:19] theseinfeld: uhm... the binaries generated by you source are not constant [17:20] constant? [17:20] cprov are you saying that there is a disturbance in the force? [17:20] * theseinfeld grins. [17:20] theseinfeld: see libdc1394v2 - 2.0.0-1ubuntu7, for instance [17:21] cprov that should be deleted [17:22] if I click on https://edge.launchpad.net/~libdc1394-dev/+archive/+delete-packages I only see the -22-2.0.2 [17:22] cprov, if you can delete all the ppa, I would appreciate [17:22] do you want me to submit a bug on ppa or QA? [17:22] so you do it in the right way? [17:23] theseinfeld, you can delete packages yourself, you know? [17:23] kiko-fud i know. there is something wrong going because they show deleted but they are still there [17:23] theseinfeld: the very old binaries were not even superseded. [17:23] ah I see [17:24] cprov they were my newbie mistakes [17:24] theseinfeld: the way we do deletions (source-driven) we miss/ignore them. [17:24] cprov how can we fix this? [17:24] complete removal and I reupload the latest one? [17:24] * cprov is thinking ... [17:24] cprov, can the script be used to delete then? [17:24] * theseinfeld is waiting for the big decission from cprov. [17:25] theseinfeld: no, let's learn with this first ... [17:25] kiko-fud: yes, we can manually delete the forgotten binaries using the cmd-line [17:25] kiko-fud: but it's sub-optimal ... [17:26] New bug: #191887 in rosetta "Translation import queue filter displays inactive projects" [Undecided,New] https://launchpad.net/bugs/191887 [17:26] theseinfeld: it's not hard to spot the problem, https://edge.launchpad.net/~libdc1394-dev/+archive?field.name_filter=libdc1394v2&field.status_filter=superseded [17:27] theseinfeld: if you inspect the details, the "files" will should up when they shouldn't [17:31] cprov it is true that it says that they have been removed...but why are they still there... [17:31] cprov I am a bit tired... I will look tomorrow and let you know... [17:33] cprov let me see if I got it wright: are you saying that because they are superseeded by another version they cannot be removed? [17:33] theseinfeld: everything marked as *removed* was in fact removed, I'm talking about the records that are not marked as removed ... [17:34] how can I mark them if they don't show in the ppa? [17:34] libdc1394v2 - 2.0.0-1ubuntu5 till libdc1394v2 - 2.0.0-1ubuntu7 [17:34] *exactly*, I'm filling a bug about it. [17:35] cprov thanks. Going for dinner :) [17:38] theseinfeld, kiko-fud: https://bugs.edge.launchpad.net/soyuz/+bug/191892 [17:38] Launchpad bug 191892 in soyuz "Unsuperseded binaries can't be deleted from PPAs" [Undecided,New] [17:46] New bug: #191891 in launchpad "OOPS accessing +expiringmembership for a person." [Undecided,New] https://launchpad.net/bugs/191891 === thekorn_ is now known as thekorn [17:50] New bug: #191892 in soyuz "Unsuperseded binaries can't be deleted from PPAs" [High,Triaged] https://launchpad.net/bugs/191892 === mrevell-lunch is now known as mrevell [17:56] **** launchpad meeting in #launchpad-meeting in t-4 minutes [17:58] hey dneary, thanks for your mail. [17:58] Hi mrevell [17:58] No problem [17:59] Both positive and negative, I guess [17:59] When the best thing someone can say about the project is "your tech support team is very nice", you should probably be worried ;) === kiko-fud is now known as kiko [18:05] New bug: #191899 in launchpad "OOPS renaming a team with a mailing list activated " [Undecided,New] https://launchpad.net/bugs/191899 [18:10] New bug: #191900 in malone "Bug tracker admin: don't auto-add the previous base url as an alias without telling the user" [Undecided,New] https://launchpad.net/bugs/191900 === barry is now known as barry-away === salgado is now known as salgado-phone [19:10] New bug: #191916 in launchpad-bazaar "some LaunchpadTransport methods access backing_transport unconditionally" [Undecided,New] https://launchpad.net/bugs/191916 === salgado-phone is now known as salgado [20:02] Goooooooooooooooooooood morning Launchpadders! [20:19] hey mpt === salgado is now known as salgado-afk [20:50] New bug: #191945 in launchpad "I got an error changing the mailing list contact address" [Undecided,New] https://launchpad.net/bugs/191945 [21:03] can I have a release deleted? [21:05] can someone delete https://edge.launchpad.net/gasp-code/unstable-0.2.x/0.2.0 ? [21:08] how do I mark a milestone as finished? there doesn't seem to be an option on the /+milestone/beta-1/+edit page [21:15] mrmonday: Does the `Change details' action not take you to a page with an Active flag? [21:15] Fujitsu, no [21:16] hey all, [21:17] mrmonday: are you a beta tester? [21:17] if not, try on the edge site [21:17] when registering a new project, at the very bottom it says 'Part Of' and 'Super-project. In Launchpad, we can setup a special "project group" that is an overarching initiative that includes several related projects.' - I'm wondering, how do I actually create this super-project thingy? [21:17] (i think a bug in this area got fixed recently) [21:18] AlexC_: You have to ask an admin. [21:18] how do I delete a release? I made it by mistake. [21:18] Fujitsu, ahh ok, where do I ask - on the mailing lists? [21:18] Fujitsu, or through the 'Answers' part of LP? [21:18] AlexC_: the lattter [21:18] *latter [21:18] mwhudson, thanks, it appears on the beta site :) [21:18] AlexC_: Answers. [21:18] ffm, Fujitsu awesome, thanks very much [21:18] ffm: The same. [21:18] mrmonday: good :) [21:19] ffm: Ask for it to be done on Answers. [21:21] Fujitsu: kk. === Martinp24 is now known as Martinp23 [22:21] New bug: #191966 in launchpad "Over-long project display name/title isn't prohibited" [Undecided,New] https://launchpad.net/bugs/191966 [22:22] hi [22:22] can anybody there browse https://launchpad.net/bugs/191065? [22:25] seb128: looks like a private bug [22:27] mwhudson: that I noticed ;-) I thought it was breaking the crash retracer ubuntu is using and wanted to untag it but I couldn't open it [22:27] mwhudson: but looks like the issue is not specific to this bug so that's alright === _Paracha is now known as Paracha === poolie__ is now known as poolie [22:55] who manages Translations? [22:56] carlos [22:57] poolie: danilo, jtv and I [22:57] poolie: btw, hi :-) [22:57] hi! [23:41] New bug: #191988 in soyuz "corresponding binary package to source package missing" [Undecided,New] https://launchpad.net/bugs/191988 === manfre is now known as Manfre-v-day