=== matsubara is now known as matsubara-afk [02:08] I uploaded a package to my ppa, deleted it, and after a while uploaded it again - any reason it should be taking it's time to even appear on the page? [02:09] vadi2: using the same version number? [02:09] it's not a good idea [02:09] bump the version [02:09] well, I changed it [02:09] but I'm not sure if its newer [02:09] sec [02:09] 0.1~bzr69-0ubuntu1~ppa11 is old, 0.1~beta-pre1-ppa1 is new [02:10] (I just made them up really... didn't see a guide on how to make them proper. I'm the upstream myself) [02:10] 'bzr' sorts after 'beta' [02:10] the new one should maybe be [02:10] 0.1.beta~pre1~ppa1 [02:11] it's preview release 1 of the beta? [02:11] right [02:11] ok, I'll try with 0.1.beta~pre1~ppa1 [02:15] vadi2: It should be ~beta, not .beta [02:15] :( ok. are you sure? [02:15] didn't seem like lp liked the dot though [02:15] vadi2: Well, you want 0.1 to be newer than 0.1 beta, right? [02:16] not really - I just want it to be bigger than 0.1~bzr69-0ubuntu1~ppa11. after beta, we'll go to 1.0 (as it'll be a finished and usable program) [02:18] doh [02:18] That's a peculiar way to do it - have a series of betas that don't lead up to a final release [02:19] What's the upstream version number considered to be? [02:19] the syntax is "dput file.changes ppa-name"? [02:19] other way around [02:19] maxb: I am part of the upstream. before we had "pre-alpha", now "pre-beta", then "1.0". a bit odd.. [02:20] Hm. Well I guess there's nothing wrong with 0.1.beta if you guarantee there will never be an 0.1 final [02:21] I thought the 0.1 part was necessary for the package to work [02:21] huh? [02:22] I wouldnt've had a problem with naming the package version "pre-alpha~ppa1", I just added 0.1 because I thought the superceding rules wouldn't work otherwise [02:22] correct [02:23] I realized I messed up the dput syntax, that's why it didn't ask for my pass when uploading and didn't show on the lp page [02:23] that was probably my issue. oops [02:24] So, the upstream version is "pre-beta"? That's not a version, it's a description of a phase of development [02:24] yeah. [02:28] maxb: it works! === mthaddon_ is now known as mthaddon === Ursinha is now known as Jorjao === Jorjao is now known as Amelinha === Amelinha is now known as Ursinha [03:39] ya [03:41] hey [03:41] how ya been? [03:41] good [03:41] you? [03:41] ok [03:41] :) [03:41] trying to clean out some bugs [03:42] even though they're not fixed, they're minor [03:42] things like incorrect spelling on the website kinda things [03:42] or Alt+O bound to more than one thing [03:42] hmm [03:43] I love fixing minor bugs [03:43] and clean the pile [03:43] cleaning [03:43] must sleep :) [03:43] I would fix them... but trying to find someone to actually commit a change may be a huge pain [03:44] especially since I'd be dealing wiht languages I've never seen before [03:44] true [03:44] I'm just marking them invalid and saying screw it [03:45] eww [03:45] what should I do? [03:46] nothing [03:46] it just hurts [03:46] doesn't it? [03:46] it's [03:46] ya [03:46] it's incredibly painful; [03:46] :/ [03:46] I share the pain [03:47] you ever do the same thing? [03:47] I try not to do [03:47] but sometimes it happens [03:48] some of these have been out here for a year - and still exist [03:48] for me only a few things are less painful than marking an imperfection as won't fix [03:48] more painful, I mean [03:48] I really need to sleep :) [03:49] I can't set Won't Fix [03:49] I'm stuck with Invalid [03:49] MTecknology, I'd leave it there [03:49] but marking as invalid I don't know [03:49] don't you have any hope of having someone to fix them? [03:49] not after this long [03:50] maybe it's just a matter of bringing it to attention [03:50] I'll try to [03:50] :) [03:50] g'night [03:50] go away [03:50] hahahahahaha [03:50] now! [03:50] all right! [03:50] * MTecknology licks [03:50] bye :) [03:50] ttyl [03:50] good luck [03:51] ty [03:51] :) [03:51] * Ursinha wanders off [03:51] Ursinha: ? [03:52] ok, that's good then [04:16] hurray, I dropped 28 bugs from my name... [04:53] hi there. points to [04:53] but the latter is a broken link [04:54] can someone please tell me how to import the current mailman source in jaunty to my PPA? [05:34] Hmm, my translation has been in the import queue for 2 or 3 days, is that normal? [05:50] mrooney: wish I had an answer for you (I'm new-ish to launchpad)... do you happen to know how to copy a jaunty source package to ppa? [05:50] mrooney: the link from is dead [05:53] nope, sorry! [05:53] I guess I'll waste bandwidth and pull a local branch, then push back up [07:24] hi [07:24] how many translators are there on launchpad? [07:46] hi, I'm not sure if someone is intrested in this comment, but this "only show the first 80 comments for a bugreport" is a really bad design IMO [07:46] I'm almost all the time interested in the latest comments, [07:46] so I need to scroll down to the bottom, click the link (and wait) and scroll to the bottom again [07:47] I hope this is not the result of the performance improving efforts ;) [07:47] thekorn: it keeps people from posting comments that have already been covered [07:47] thekorn: subscribe to the bug and you'll get the latest comments as they come [07:51] tarheelcoxn, sorry, but how does this prevent people from writing comments that have already been covered? [07:53] thekorn: they see the comment they were going to post and don't post it [07:53] put another way, youtube puts most recent comments at the top. [07:55] yeah but youtube is fun, but a bugtracker is about information [07:55] and hiding information is bad [07:57] it doesn't hide the information [07:57] the core information you need (the bug's status) is right at the top [07:59] sorry, I don't agree with you here, we ask the affected people for more information, so our 'core information' is in their comments [07:59] speaking as a bug triager [08:01] so subscribe to the bug? [08:01] you'll get their comments by mail [08:02] another way of looking at it is that any bug with more than 80 comments is probably not very useful/digestible anyway [08:07] ok, if this is the reason for this "feature" than launchpad needs a ranking feature for comments, why can't comment 123 be the most important comment for this bugreport [08:09] I would agree - comment ranking would be a good idea === kiko-phone is now known as kiko [08:55] g'day all.. how do I delete/hide a launchpad project ? [08:57] sm: file a question on answers.launchpad.net/launchpad [08:58] thanks [09:04] I've been working on this for a long time and letting it really peel into my sleepy time.... [09:04] can somebody tell me if this looks good or not? https://blueprints.edge.launchpad.net/loco-drupal/+spec/7.x-2.1.0 [09:06] lol - I shoulda waited 1min so mpt caught that too.... [09:07] mpt: Do you think this looks good? https://blueprints.edge.launchpad.net/loco-drupal/+spec/7.x-2.1.0 [09:08] everyone sleeping? [09:09] MTecknology, you can register releases for a project from the project's Overview page [09:09] Then you can target blueprints representing actual features to release series [09:10] mpt: I have release series [09:10] From the release series you can register a release [09:10] (it's a bit hierarchical) [09:11] so the blueprint is made up right, except it's supposed to be applied to a series instead? [09:11] mpt: I have release series and each is linked to a branch [09:13] mpt: what am I doing wrong? [09:13] MTecknology, well it's entirely up to you, I'm just wondering why you're using blueprints to represent releases when Launchpad has actual releases built in :-) [09:14] e.g. you could have a 2.1.0 release instead of a 2.1.0 blueprint. === mrevell_ is now known as mrevell [09:16] mpt: I just liked how I could build it into a nice pretty picture explaining what we need to do to make the releases happen [09:17] fair enough [09:17] Launchpad should do a better job of that for releases, but doesn't yet [09:18] mpt: what is the original idea behind blueprints? [09:18] Tracking the implementation of features or major changes. [09:18] so am I close to using it right? [09:19] yep [09:19] :) [09:21] well - bed time [09:23] well - launchpad is awesome. [09:23] thanks everyone for creating it :D [09:23] g'night all === gmb changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Help contact: gmb | launchpad-users@lists.launchpad.net [10:04] When a build gets re-submitted to the buildds, is there any way to see history of previous attempts? [10:04] I've noticed a bunch of kde* packages in intrepid backports seemingly building over and over and over again on sparc/hppa/ia64source/watershed/3/+build/771642 [10:05] erm, oops, paste failure [10:05] I've noticed a bunch of kde* packages in intrepid backports seemingly building over and over and over again on sparc/hppa/ia64 [10:06] maxb: you can see builder history [10:08] I'm not convinced that does the job when it's the same build record being retried over and over [10:09] which packages, exactly? [10:09] they can only be retried if they fail [10:11] http://paste.ubuntu.com/116751/ - the ones shown pending there [10:12] They seem to build, then later I notice that the same package version has shown up as "Needs building" again [10:13] but, as you can see from the list, some of those packages on some architectures have settled in a chrootwait/failed state and are staying there [10:16] maxb: if you can find one that went from built to needs building, I would be very interested, otherwise it looks normal [10:17] I think the problem is that they're going to depwait, then un-depwaiting even though they still don't have the right deps === thekorn_ is now known as thekorn === Odd_Blok1 is now known as Odd_Bloke === rootard is now known as rootard_zzz === bac_afk is now known as bac [12:53] I hear rumours every now and then that it's possible for a project to have a PPA. How do I set that up? [12:53] soren: it's not possible. but it's in the pipeline [12:55] Alright. I'll just create a maintainer team for the project, then. [12:55] bigjools: Thanks. [12:55] np === beuno_ is now known as beuno === warp10_ is now known as warp10 === magcius_ is now known as magcius [14:46] hi there [14:46] can it be possible that rosetta ignore my po export requests? [14:48] sianis: Only if you requested them on "staging" (translations.staging.launchpad.net). [14:49] henninge: no, I don't [14:49] but we tries it out [14:49] tried [14:49] I don't get the po an other account get it [14:49] sianis: no, I meant that requests done on staging would be ignored ... ;-) [14:49] sianis: ?? [14:50] so, we request export with two account [14:50] but only one of them get email [14:51] sianis: well, it is possible that the emails get held up of filtered out as spam because they contain a link. [14:51] s/of/or/ [14:51] I requested it again twice [14:52] and I use gmail, and Spam is empty [14:52] sianis: twice means what? twice in the same place, twice with two different accounts? [14:53] twice with same account on launchpad.net [14:53] :) [14:54] sianis: I this the first time you used either account to request exports? [14:54] no I don't [14:55] I worked great by now [14:55] It [14:55] sianis: I was just wondering if the mail got held up by greylisting [14:55] sianis: ah, good to hear [14:56] but now it don't work [14:56] for 2-3 days [14:56] maybe I requested to many po? [14:56] sianis: but you said that you did get e-mail on the one account today, right? [14:57] sianis: no, there is no limit on that. [14:57] hmm [14:57] I have no idea [14:58] can you see my request query ? === vednis is now known as mars [15:06] sianis: can you please tell me where you are requesting the download exactly? Copy the link from your browser, please. [15:06] ok [15:07] henninge: https://translations.launchpad.net/ubuntu/jaunty/+source/ubuntu-docs/+pots/about-ubuntu/hu/+export [15:08] sianis: thanks, I am trying it myself now. [15:16] I'm trying to switch to launchpad from sourceforge for code hosting. We have lp:mixxx tracking our svn already but I'm trying to figure out if we're supposed to start pushing to that or if we need to make a new empty branch and work there. [15:16] sianis: Worked for me. [15:17] sianis: The mails took about 8 minutes to arrive. [15:17] henninge: I also requested it, nothing riht now [15:20] henninge: it is arrieved [15:20] strange :) [15:21] sianis: probably greylisting on your mail server or something similar. [15:21] sianis: I am glad that it worked for you now. [15:21] ok thx === kousu_ is now known as kousu [15:31] I think I corrupted the launchpad branch I am trying to move my code into. How do I delete it? [15:33] kousu: There's an option in the UI. [15:33] Odd_Bloke: on http://launchpad.net? [15:33] I can't find it [15:35] kousu: http://code.launchpad.net/~// or something similar. [15:35] Odd_Bloke: oooh the tiny Trash icon [15:35] kousu: Oh, right. [15:36] Yeah, the tiny Trash icon. :) [15:36] Next question: launchpad is already tracking our svn; if we want to switch to bzr do we use the tracked branch or do I make a new one and push our code into it? [15:37] kousu: I would think a new one, else the importer might become confused. [15:37] But IANA Launchpad Developer. [15:37] gmb: ^^ [15:38] Odd_Bloke: okay, thanks, I figured that. Couldn't find any docs that said for sure (and the initial push is going to take hooours) [15:38] * gmb reads the scrollback === thunderstruck is now known as gnomefreak [15:41] kousu: I wonder if there might be a better way. Hang on, I'll ask one of the codehosting team for you... [15:42] gmb: :D [15:42] kousu, hi [15:43] Hi [15:43] kousu, so you already have a code import of your svn trunk? [15:43] Yes, lp:mixxx [15:44] (though it's 20 days behind svn; there's SSL errors in the recent import logs) [15:44] kousu, let me take a look. I bet we can fix those. === deryck_ is now known as deryck [15:53] kousu, so I think the issues with your SSL errors will be fixed on the next import. [15:54] kousu, so once the import gets caught up, you can ask a question in launchpad-bazaar about stopping the import, and then just work on the bazaar branch. [15:55] rockstar: thanks! [15:55] Is that launchpad-bazaar@ or #launchpad-bazaar? [15:56] kousu, https://answers.edge.launchpad.net/launchpad-bazaar [16:00] thanks rockstar and gmb, launchpad is a great thing === kiko is now known as kiko-fud [16:01] Thansk kousu === matsubara_ is now known as matsubara-lunch [16:22] I have a patch made with 'bzr diff > file' - How can I apply this patch to my files? [16:24] I love how launchpad bundles together the change emails when I make a bunch of changes near the same time. +++ [16:25] nice, I'm missing that feature [16:25] I got 30 emails in 5hr [16:30] MTecknology, were they different bugs? [16:30] Hi - I've created two bzr branch holding mysql-dfsg-5.1 packaging bits (just the debian/ directory). These are based on Debian svn repository. When I try to push to lp:~ubuntu-core-dev/mysql-server/pkg-{ubuntu,debian}-5.1 it fails. [16:31] rockstar: ya [16:31] Probably because mysql-server is already using stacked branches [16:31] MTecknology, it won't bundle those emails. Just if you change a bug three times really quick (like if you forget to assign it to you when setting InProgress) [16:31] and the branches I'd like to push are not based on the upstream mysql-server ones. [16:31] oh [16:32] How can I handle this situation? [16:32] mathiaz, are you in ubuntu-core-dev ? [16:32] rockstar: yes [16:34] rockstar: http://paste.ubuntu.com/116915/ [16:34] mathiaz, looks like your two branches are different formats. [16:35] rockstar: yes - my branches are based on an svn repository [16:35] rockstar: which is different from what upstream mysql-server is using [16:36] so it seems I won't be able to push the packaging branches to lp:~ubuntu-core-dev/mysql-server/ [16:37] mathiaz, if you create new branches you can. [16:38] rockstar: from the website? [16:38] mathiaz, or just push. [16:38] You don't have to register the branch first. [16:38] rockstar: well push doesn't work [16:39] mathiaz, you're pushing to a branch that already exists. [16:40] rockstar: lp:~ubuntu-core-dev/mysql-server/pkg-debian-5.1/ [16:40] rockstar: ^^ doesn't exist [16:40] rockstar: mysql-server does and uses stacked branches === verterok_ is now known as verterok [16:41] mathiaz, this one? https://code.edge.launchpad.net/~ubuntu-core-dev/mysql-server/pkg-debian-5.1/ [16:41] mathiaz, ah, I see what you're saying. It shouldn't be trying to stack though. [16:43] mathiaz, could you file a bug on that? [16:43] rockstar: sure [16:44] rockstar: against launchpad? or another project? [16:44] mathiaz, launchpad-bazaar === matsubara-lunch is now known as matsubara [16:49] matsubara: hi [16:50] hello MTecknology [16:50] matsubara: guess what... [16:51] blueprints really do offer an insane amount of karma.... [16:52] That's because few people use them compared with the other Launchpad applications [16:52] (not that that's a good reason, necessarily, but it is the reason) [16:52] MTecknology: I'll close that bug then. thanks [16:53] yup [16:53] matsubara: it just takes a really long time to do [16:53] I mean for the karma to get added === sale_ is now known as sale [17:13] What is the correct way to translate a new series? I uploaded a new template and was expecting any already translated strings in the current series to carry over, but this didn't happen. [17:13] Do I export the translations from series A and upload them to series B? [17:14] Hm that doesn't seem like an option [17:20] any admins sitting around here? [17:21] mpt: stop doing that [17:21] I ask something you can help on and you pop in right after :P [17:21] MTecknology, stop doing what? [17:21] mpt: Can you help me change a version number? [17:22] MTecknology, probably not [17:22] oh [17:23] I figured you probably could from the lp hostmask [17:23] There may be a "Change details" link or similar on the thing you want to change [17:23] If there isn't, you'll need to file a request to change it [17:23] there is, but I can't change that portion of it [17:26] mrooney: yes, you should export all translations from one series and upload them into a new one [17:26] mrooney: we are working on making this automatic in the near future [17:27] danilos: but that won't stomp over my new TEMPLATE, right? [17:27] mrooney: depends on the setup and file names [17:27] mpt: what do you do for lp? [17:27] mrooney: you should not upload old template if you already have a new template up (i.e. you can put that in a tarball instead) [17:28] mrooney: Launchpad is smart enough to do the merge of all pofiles correctly with the new template [17:29] MTecknology: mpt it part of Canonical's design team and is a former member of the Launchpad team. He's a UI / design guru. [17:29] danilos: ahh I see, thanks! Can I upload just the translations without a template or will it be unhappy? [17:29] oh [17:29] And possibly a demigod, but I haven't established that beyond reasonable doubt yet. [17:29] :P [17:30] Oh... is LP actually going to be opened up to the public? [17:30] the source to it [17:30] MTecknology: For future reference, the "Help contact" in the topic is the person to go to. [17:30] Odd_Bloke: oh, I've never noticed that [17:31] MTecknology, yes, it will be open-sourced in July [17:31] wow [17:32] I wonder how many people will try to go from LP to their own servers... [17:33] is that part of the reason for opening it? reduce load? I was thinking about it and the load on those servers needs to be insane [17:34] Is it all being freed, or just the UI code? [17:34] Odd_Bloke: Everything except Soyuz and codehosting: http://blog.launchpad.net/general/how-we-are-open-sourcing-launchpad [17:37] nice [17:38] that secret sauce thing is why I was surprised to see it released at all [17:38] MTecknology: It's being opened because we always promised that we would open it, and we think we've now come to a point where we can open it *and* sustain a paid development team for it, which was one of the major objections to it being opened. [17:39] MTecknology: As far as load is concerned, well, we're working on making Launchpad much faster (that's our major 3.0 goal). Whether people will want to run their own instance or not I don't know, but I do know that Launchpad does require quite a bit of infrastructure. [17:40] Oh crap. [17:40] I made the mistake of reading comments on the internet. [17:40] I'm not going away, the thought of doing it myself is scary :P - my web server has a 400MHz proc :P === bac is now known as bac_lunch [17:40] somehow it does a good job though [17:40] Odd_Bloke: Generally not a good thing... why, what's perturbed you? [17:40] Odd_Bloke: me too - they're kinda irritating [17:41] the only comment of any value was the link to that other article [17:41] gmb: The number of complaints about Soyuz not being freed. [17:41] Ah. [17:42] Well, it's a contentious issue in some parts of the OSS world. [17:42] 9 is a good comment [17:42] can't imagine why [17:43] Well, I would prefer if it were free. But, equally, having a paid development team is probably vastly more useful to it at this point in time. [17:43] I'd be interested to see if a Soyuz-a-like is developed once everything else is free... [17:43] s/I'd/I'll/ [17:44] LOL! [17:44] ok - so sabdfl is good in an arguement === gmb changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Help contact: - | launchpad-users@lists.launchpad.net [18:05] I wish Soyuz was being opened, because it's part of the Ubuntu process that particularly interests me. (And has bugs I'd help in fixing). On the other hand, I wish people would stop getting uppity about it, when it's clearly Canonical's right to decide which bits of its work it releases. [18:08] on the bright side, you'll get to see the code for the Soyuz UI stuff [18:10] Meanwhile, how about you guys who do have the source get on to fixing those Packages-arch-specific processing bugs? :-) [18:17] cprov: any update on question #59622 (Re-publish libtest-perl-critic-perl in jaunty)? Is some information missing or is it somewhere in your work queue? [18:17] geser: No, I'm sorry, it's not happening in this cycle. [18:19] geser: scratch that, I just have to resurrect the binaries for you, will do that. [18:19] thanks [18:24] geser: let's talk about it [18:25] geser: the superseded publication is in intrepid and you want it to be resurrect in jaunty, right ? [18:25] geser: why you can't simply bump the version and do a new upload ? === bac_lunch is now known as bac [18:27] cprov: both intrepid and jaunty are affected, but for intrepid I should probably go through a SRU to add it back which is not really worth it [18:27] for jaunty I could reupload it if it's easier for you [18:27] geser: it is [18:28] geser: also the higher version might be beneficial [18:28] ok, will reupload it then [18:29] I'd have to request archive-admin permission to do what you are requesting (intrepid -> jaunty) [18:29] geser: it's better if we do that in the clearest way possible, with a new upload. [18:29] so in cases I find another missing deb the preferred solution is to reupload? [18:32] geser: if it's cross-series yes [18:32] geser: if it's in the development series (and it's not frozen) I can re-activate it easily. [18:33] ah, ok === thekorn_ is now known as thekorn [19:23] hi, following problem: i've don't know my email address anymore i used to register (i used a trash-email-address because my .eu-mail doesnt work, always wrong, verification hash doesn't fit... bug?) [19:26] daniel_tp, what is a trash-email-address? and which is your user id on lp? [19:28] danielkutik [19:31] Ursinha, for example: www.spam.la === merriam_ is now known as merriam [20:07] g'morning Earthlets [20:07] is there a way to see the translation status of all templates, such as on https://translations.launchpad.net/tangocms/trunk - to currently do this we have to go through every template to see. We'd like a general overview of how much translating has been done === _neversfelde is now known as neversfelde [20:27] danilos: are you around by any chance? I can't figure out how to move over my translations properly to a new series === salgado is now known as salgado-afk [20:28] I download the old series PO files, replaced the template with the new one, and upload that [20:28] and after getting the success email, there are still no translations showing up for that series [20:44] hmm..maybe I've figured it out... [21:00] Hello, I'm wondering if there's some way the ubuntu-docs team cam bugs on the ubuntu source package and bugs on the ubuntu-doc project better synchronised? [21:01] few or 0 bugs are ubuntu specific. The package is maintained in our bzr repo. [21:01] Currently we have to either check two different lists of bugs or change everything twice [21:02] bah, sorry for my english, I've open been speaking it 23 years now. [21:02] only, even. [21:02] irc destroys my ability to type [21:03] maybe thats it, I've been blaming the eeepc keyboard [21:05] anyway yes, we want to have a better workflow that gives us all bugs in one place and doesn't require lots of twiddling of lp buttons [21:31] * kfogel is away: back on later [22:21] How do I get my projects license reviewed? [22:23] MTecknology, you poke bac [22:23] * bac hides [22:23] bac: hi [22:23] MTecknology: gimme an URL [22:23] bac: don't worry, I'm still making sure I have it right [22:24] MTecknology: what is your project named? [22:24] loco-drupal [22:24]