[02:08] <vadi2> 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] <poolie> vadi2: using the same version number?
[02:09] <poolie> it's not a good idea
[02:09] <poolie> bump the version
[02:09] <vadi2> well, I changed it
[02:09] <vadi2> but I'm not sure if its newer
[02:09] <vadi2> sec
[02:09] <vadi2> 0.1~bzr69-0ubuntu1~ppa11 is old, 0.1~beta-pre1-ppa1 is new
[02:10] <vadi2> (I just made them up really... didn't see a guide on how to make them proper. I'm the upstream myself)
[02:10] <poolie> 'bzr' sorts after 'beta'
[02:10] <poolie> the new one should maybe be
[02:10] <poolie> 0.1.beta~pre1~ppa1
[02:11] <poolie> it's preview release 1 of the beta?
[02:11] <vadi2> right
[02:11] <vadi2> ok, I'll try with 0.1.beta~pre1~ppa1
[02:15] <maxb> vadi2: It should be ~beta, not .beta
[02:15] <vadi2> :( ok. are you sure?
[02:15] <vadi2> didn't seem like lp liked the dot though
[02:15] <maxb> vadi2: Well, you want 0.1 to be newer than 0.1 beta, right?
[02:16] <vadi2> 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] <vadi2> doh
[02:18] <maxb> That's a peculiar way to do it - have a series of betas that don't lead up to a final release
[02:19] <maxb> What's the upstream version number considered to be?
[02:19] <vadi2> the syntax is "dput file.changes ppa-name"?
[02:19] <maxb> other way around
[02:19] <vadi2> maxb: I am part of the upstream. before we had "pre-alpha", now "pre-beta", then "1.0". a bit odd..
[02:20] <maxb> 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] <vadi2> I thought the 0.1 part was necessary for the package to work
[02:21] <maxb> huh?
[02:22] <vadi2> 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] <maxb> correct
[02:23] <vadi2> 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] <vadi2> that was probably my issue. oops
[02:24] <maxb> So, the upstream version is "pre-beta"? That's not a version, it's a description of a phase of development
[02:24] <vadi2> yeah.
[02:28] <vadi2> maxb: it works!
[03:39] <MTecknology> ya
[03:41] <Ursinha> hey
[03:41] <MTecknology> how ya been?
[03:41] <Ursinha> good
[03:41] <Ursinha> you?
[03:41] <MTecknology> ok
[03:41] <Ursinha> :)
[03:41] <MTecknology> trying to clean out some bugs
[03:42] <MTecknology> even though they're not fixed, they're minor
[03:42] <MTecknology> things like incorrect spelling on the website kinda things
[03:42] <MTecknology> or Alt+O bound to more than one thing
[03:42] <Ursinha> hmm
[03:43] <Ursinha> I love fixing minor bugs
[03:43] <Ursinha> and clean the pile
[03:43] <Ursinha> cleaning
[03:43] <Ursinha> must sleep :)
[03:43] <MTecknology> I would fix them... but trying to find someone to actually commit a change may be a huge pain
[03:44] <MTecknology> especially since I'd be dealing wiht languages I've never seen before
[03:44] <Ursinha> true
[03:44] <MTecknology> I'm just marking them invalid and saying screw it
[03:45] <Ursinha> eww
[03:45] <MTecknology> what should I do?
[03:46] <Ursinha> nothing
[03:46] <Ursinha> it just hurts
[03:46] <Ursinha> doesn't it?
[03:46] <MTecknology> it's
[03:46] <MTecknology> ya
[03:46] <MTecknology> it's incredibly painful;
[03:46] <Ursinha> :/
[03:46] <Ursinha> I share the pain
[03:47] <MTecknology> you ever do the same thing?
[03:47] <Ursinha> I try not to do
[03:47] <Ursinha> but sometimes it happens
[03:48] <MTecknology> some of these have been out here for a year - and still exist
[03:48] <Ursinha> for me only a few things are less painful than marking an imperfection as won't fix
[03:48] <Ursinha> more painful, I mean
[03:48] <Ursinha> I really need to sleep :)
[03:49] <MTecknology> I can't set Won't Fix
[03:49] <MTecknology> I'm stuck with Invalid
[03:49] <Ursinha> MTecknology, I'd leave it there
[03:49] <Ursinha> but marking as invalid I don't know
[03:49] <Ursinha> don't you have any hope of having someone to fix them?
[03:49] <MTecknology> not after this long
[03:50] <Ursinha> maybe it's just a matter of bringing it to attention
[03:50] <MTecknology> I'll try to
[03:50] <Ursinha> :)
[03:50] <MTecknology> g'night
[03:50] <MTecknology> go away
[03:50] <Ursinha> hahahahahaha
[03:50] <MTecknology> now!
[03:50] <Ursinha> all right!
[03:50]  * MTecknology licks
[03:50] <Ursinha> bye :)
[03:50] <MTecknology> ttyl
[03:50] <Ursinha> good luck
[03:51] <MTecknology> ty
[03:51] <Ursinha> :)
[03:51]  * Ursinha wanders off
[03:51] <MTecknology> Ursinha: ?
[03:52] <MTecknology> ok, that's good then
[04:16] <MTecknology> hurray, I dropped 28 bugs from my name...
[04:53] <tarheelcoxn> hi there. <https://help.launchpad.net/Packaging/PPA#Copying packages> points to <https://launchpad.net/~ubuntu-mobile/+archive/+copy-packages>
[04:53] <tarheelcoxn> but the latter is a broken link
[04:54] <tarheelcoxn> can someone please tell me how to import the current mailman source in jaunty to my PPA?
[05:34] <mrooney> Hmm, my translation has been in the import queue for 2 or 3 days, is that normal?
[05:50] <tarheelcoxn> 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] <tarheelcoxn> mrooney: the link from <https://help.launchpad.net/Packaging/PPA#Copying packages> is dead
[05:53] <mrooney> nope, sorry!
[05:53] <tarheelcoxn> I guess I'll waste bandwidth and pull a local branch, then push back up
[07:24] <poolie> hi
[07:24] <poolie> how many translators are there on launchpad?
[07:46] <thekorn> 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] <thekorn> I'm almost all the time interested in the latest comments,
[07:46] <thekorn> so I need to scroll down to the bottom, click the link (and wait) and scroll to the bottom again
[07:47] <thekorn> I hope this is not the result of the performance improving efforts ;)
[07:47] <tarheelcoxn> thekorn: it keeps people from posting comments that have already been covered
[07:47] <tarheelcoxn> thekorn: subscribe to the bug and you'll get the latest comments as they come
[07:51] <thekorn> tarheelcoxn, sorry, but how does this prevent people from writing comments that have already been covered?
[07:53] <tarheelcoxn> thekorn: they see the comment they were going to post and don't post it
[07:53] <tarheelcoxn> put another way, youtube puts most recent comments at the top.
[07:55] <thekorn> yeah but youtube is fun, but a bugtracker is about information
[07:55] <thekorn> and hiding information is bad
[07:57] <tarheelcoxn> it doesn't hide the information
[07:57] <tarheelcoxn> the core information you need (the bug's status) is right at the top
[07:59] <thekorn> 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] <thekorn> speaking as a bug triager
[08:01] <tarheelcoxn> so subscribe to the bug?
[08:01] <tarheelcoxn> you'll get their comments by mail
[08:02] <mthaddon> another way of looking at it is that any bug with more than 80 comments is probably not very useful/digestible anyway
[08:07] <thekorn> 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] <mthaddon> I would agree - comment ranking would be a good idea
[08:55] <sm> g'day all.. how do I delete/hide a launchpad project ?
[08:57] <lifeless> sm: file a question on answers.launchpad.net/launchpad
[08:58] <sm> thanks
[09:04] <MTecknology> I've been working on this for a long time and letting it really peel into my sleepy time....
[09:04] <MTecknology> 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] <MTecknology> lol - I shoulda waited 1min so mpt caught that too....
[09:07] <MTecknology> mpt: Do you think this looks good? https://blueprints.edge.launchpad.net/loco-drupal/+spec/7.x-2.1.0
[09:08] <MTecknology> everyone sleeping?
[09:09] <mpt> MTecknology, you can register releases for a project from the project's Overview page
[09:09] <mpt> Then you can target blueprints representing actual features to release series
[09:10] <MTecknology> mpt: I have release series
[09:10] <mpt> From the release series you can register a release
[09:10] <mpt> (it's a bit hierarchical)
[09:11] <MTecknology> so the blueprint is made up right, except it's supposed to be applied to a series instead?
[09:11] <MTecknology> mpt: I have release series and each is linked to a branch
[09:13] <MTecknology> mpt: what am I doing wrong?
[09:13] <mpt> 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] <mpt> e.g. you could have a 2.1.0 release instead of a 2.1.0 blueprint.
[09:16] <MTecknology> 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] <mpt> fair enough
[09:17] <mpt> Launchpad should do a better job of that for releases, but doesn't yet
[09:18] <MTecknology> mpt: what is the original idea behind blueprints?
[09:18] <mpt> Tracking the implementation of features or major changes.
[09:18] <MTecknology> so am I close to using it right?
[09:19] <mpt> yep
[09:19] <MTecknology> :)
[09:21] <MTecknology> well - bed time
[09:23] <MTecknology> well - launchpad is awesome.
[09:23] <MTecknology> thanks everyone for creating it :D
[09:23] <MTecknology> g'night all
[10:04] <maxb> When a build gets re-submitted to the buildds, is there any way to see history of previous attempts?
[10:04] <maxb> 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] <maxb> erm, oops, paste failure
[10:05] <maxb> 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] <bigjools> maxb: you can see builder history
[10:08] <maxb> I'm not convinced that does the job when it's the same build record being retried over and over
[10:09] <bigjools> which packages, exactly?
[10:09] <bigjools> they can only be retried if they fail
[10:11] <maxb> http://paste.ubuntu.com/116751/ - the ones shown pending there
[10:12] <maxb> They seem to build, then later I notice that the same package version has shown up as "Needs building" again
[10:13] <maxb> 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] <bigjools> maxb: if you can find one that went from built to needs building, I would be very interested, otherwise it looks normal
[10:17] <maxb> I think the problem is that they're going to depwait, then un-depwaiting even though they still don't have the right deps
[12:53] <soren> 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] <bigjools> soren: it's not possible. but it's in the pipeline
[12:55] <soren> Alright. I'll just create a maintainer team for the project, then.
[12:55] <soren> bigjools: Thanks.
[12:55] <bigjools> np
[14:46] <sianis> hi there
[14:46] <sianis> can it be possible that rosetta ignore my po export requests?
[14:48] <henninge> sianis: Only if you requested them on "staging" (translations.staging.launchpad.net).
[14:49] <sianis> henninge: no, I don't
[14:49] <sianis> but we tries it out
[14:49] <sianis> tried
[14:49] <sianis> I don't get the po an other account get it
[14:49] <henninge> sianis: no, I meant that requests done on staging would be ignored ... ;-)
[14:49] <henninge> sianis: ??
[14:50] <sianis> so, we request export with two account
[14:50] <sianis> but only one of them get email
[14:51] <henninge> sianis: well, it is possible that the emails get held up of filtered out as spam because they contain a link.
[14:51] <henninge> s/of/or/
[14:51] <sianis> I requested it again twice
[14:52] <sianis> and I use gmail, and Spam is empty
[14:52] <henninge> sianis: twice means what? twice in the same place, twice with two different accounts?
[14:53] <sianis> twice with same account on launchpad.net
[14:53] <sianis> :)
[14:54] <henninge> sianis: I this the first time you used either account to request exports?
[14:54] <sianis> no I don't
[14:55] <sianis> I worked great by now
[14:55] <sianis> It
[14:55] <henninge> sianis: I was just wondering if the mail got held up by greylisting
[14:55] <henninge> sianis: ah, good to hear
[14:56] <sianis> but now it don't work
[14:56] <sianis> for 2-3 days
[14:56] <sianis> maybe I requested to many po?
[14:56] <henninge> sianis: but you said that you did get e-mail on the one account today, right?
[14:57] <henninge> sianis: no, there is no limit on that.
[14:57] <sianis> hmm
[14:57] <sianis> I have no idea
[14:58] <sianis> can you see my request query ?
[15:06] <henninge> sianis: can you please tell me where you are requesting the download exactly? Copy the link from your browser, please.
[15:06] <sianis> ok
[15:07] <sianis> henninge: https://translations.launchpad.net/ubuntu/jaunty/+source/ubuntu-docs/+pots/about-ubuntu/hu/+export
[15:08] <henninge> sianis: thanks, I am trying it myself now.
[15:16] <kousu> 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] <henninge> sianis: Worked for me.
[15:17] <henninge> sianis: The mails took about 8 minutes to arrive.
[15:17] <sianis> henninge: I also requested it, nothing riht now
[15:20] <sianis> henninge: it is arrieved
[15:20] <sianis> strange :)
[15:21] <henninge> sianis: probably greylisting on your mail server or something similar.
[15:21] <henninge> sianis: I am glad that it worked for you now.
[15:21] <sianis> ok thx
[15:31] <kousu> I think I corrupted the launchpad branch I am trying to move my code into. How do I delete it?
[15:33] <Odd_Bloke> kousu: There's an option in the UI.
[15:33] <kousu> Odd_Bloke: on http://launchpad.net?
[15:33] <kousu> I can't find it
[15:35] <Odd_Bloke> kousu: http://code.launchpad.net/~<you>/<project>/<branch name> or something similar.
[15:35] <kousu> Odd_Bloke: oooh the tiny Trash icon
[15:35] <Odd_Bloke> kousu: Oh, right.
[15:36] <Odd_Bloke> Yeah, the tiny Trash icon. :)
[15:36] <kousu> 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] <Odd_Bloke> kousu: I would think a new one, else the importer might become confused.
[15:37] <Odd_Bloke> But IANA Launchpad Developer.
[15:37] <Odd_Bloke> gmb: ^^
[15:38] <kousu> 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
[15:41] <gmb> kousu: I wonder if there might be a better way. Hang on, I'll ask one of the codehosting team for you...
[15:42] <kousu> gmb: :D
[15:42] <rockstar> kousu, hi
[15:43] <kousu> Hi
[15:43] <rockstar> kousu, so you already have a code import of your svn trunk?
[15:43] <kousu> Yes, lp:mixxx
[15:44] <kousu> (though it's 20 days behind svn; there's SSL errors in the recent import logs)
[15:44] <rockstar> kousu, let me take a look.  I bet we can fix those.
[15:53] <rockstar> kousu, so I think the issues with your SSL errors will be fixed on the next import.
[15:54] <rockstar> 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] <kousu> rockstar: thanks!
[15:55] <kousu> Is that launchpad-bazaar@ or #launchpad-bazaar?
[15:56] <rockstar> kousu, https://answers.edge.launchpad.net/launchpad-bazaar
[16:00] <kousu> thanks rockstar and gmb, launchpad is a great thing
[16:01] <gmb> Thansk kousu
[16:22] <MTecknology> I have a patch made with 'bzr diff > file' - How can I apply this patch to my files?
[16:24] <jblount> I love how launchpad bundles together the change emails when I make a bunch of changes near the same time. +++
[16:25] <MTecknology> nice, I'm missing that feature
[16:25] <MTecknology> I got 30 emails in 5hr
[16:30] <rockstar> MTecknology, were they different bugs?
[16:30] <mathiaz> 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] <MTecknology> rockstar: ya
[16:31] <mathiaz> Probably because mysql-server is already using stacked branches
[16:31] <rockstar> 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] <mathiaz> and the branches I'd like to push are not based on the upstream mysql-server ones.
[16:31] <MTecknology> oh
[16:32] <mathiaz> How can I handle this situation?
[16:32] <rockstar> mathiaz, are you in ubuntu-core-dev ?
[16:32] <mathiaz> rockstar: yes
[16:34] <mathiaz> rockstar: http://paste.ubuntu.com/116915/
[16:34] <rockstar> mathiaz, looks like your two branches are different formats.
[16:35] <mathiaz> rockstar: yes - my branches are based on an svn repository
[16:35] <mathiaz> rockstar: which is different from what upstream mysql-server is using
[16:36] <mathiaz> so it seems I won't be able to push the packaging branches to lp:~ubuntu-core-dev/mysql-server/
[16:37] <rockstar> mathiaz, if you create new branches you can.
[16:38] <mathiaz> rockstar: from the website?
[16:38] <rockstar> mathiaz, or just push.
[16:38] <rockstar> You don't have to register the branch first.
[16:38] <mathiaz> rockstar: well push doesn't work
[16:39] <rockstar> mathiaz, you're pushing to a branch that already exists.
[16:40] <mathiaz> rockstar: lp:~ubuntu-core-dev/mysql-server/pkg-debian-5.1/
[16:40] <mathiaz> rockstar: ^^ doesn't exist
[16:40] <mathiaz> rockstar: mysql-server does and uses stacked branches
[16:41] <rockstar> mathiaz, this one? https://code.edge.launchpad.net/~ubuntu-core-dev/mysql-server/pkg-debian-5.1/
[16:41] <rockstar> mathiaz, ah, I see what you're saying.  It shouldn't be trying to stack though.
[16:43] <rockstar> mathiaz, could you file a bug on that?
[16:43] <mathiaz> rockstar: sure
[16:44] <mathiaz> rockstar: against launchpad? or another project?
[16:44] <rockstar> mathiaz, launchpad-bazaar
[16:49] <MTecknology> matsubara: hi
[16:50] <matsubara> hello MTecknology
[16:50] <MTecknology> matsubara: guess what...
[16:51] <MTecknology> blueprints really do offer an insane amount of karma....
[16:52] <mpt> That's because few people use them compared with the other Launchpad applications
[16:52] <mpt> (not that that's a good reason, necessarily, but it is the reason)
[16:52] <matsubara> MTecknology: I'll close that bug then. thanks
[16:53] <MTecknology> yup
[16:53] <MTecknology> matsubara: it just takes a really long time to do
[16:53] <MTecknology> I mean for the karma to get added
[17:13] <mrooney> 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] <mrooney> Do I export the translations from series A and upload them to series B?
[17:14] <mrooney> Hm that doesn't seem like an option
[17:20] <MTecknology> any admins sitting around here?
[17:21] <MTecknology> mpt: stop doing that
[17:21] <MTecknology> I ask something you can help on and you pop in right after :P
[17:21] <mpt> MTecknology, stop doing what?
[17:21] <MTecknology> mpt: Can you help me change a version number?
[17:22] <mpt> MTecknology, probably not
[17:22] <MTecknology> oh
[17:23] <MTecknology> I figured you probably could from the lp hostmask
[17:23] <mpt> There may be a "Change details" link or similar on the thing you want to change
[17:23] <mpt> If there isn't, you'll need to file a request to change it <https://answers.launchpad.net/launchpad>
[17:23] <MTecknology> there is, but I can't change that portion of it
[17:26] <danilos> mrooney: yes, you should export all translations from one series and upload them into a new one
[17:26] <danilos> mrooney: we are working on making this automatic in the near future
[17:27] <mrooney> danilos: but that won't stomp over my new TEMPLATE, right?
[17:27] <danilos> mrooney: depends on the setup and file names
[17:27] <MTecknology> mpt: what do you do for lp?
[17:27] <danilos> 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] <danilos> mrooney: Launchpad is smart enough to do the merge of all pofiles correctly with the new template
[17:29] <gmb> 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] <mrooney> danilos: ahh I see, thanks! Can I upload just the translations without a template or will it be unhappy?
[17:29] <MTecknology> oh
[17:29] <gmb> And possibly a demigod, but I haven't established that beyond reasonable doubt yet.
[17:29] <MTecknology> :P
[17:30] <MTecknology> Oh... is LP actually going to be opened up to the public?
[17:30] <MTecknology> the source to it
[17:30] <Odd_Bloke> MTecknology: For future reference, the "Help contact" in the topic is the person to go to.
[17:30] <MTecknology> Odd_Bloke: oh, I've never noticed that
[17:31] <mpt> MTecknology, yes, it will be open-sourced in July
[17:31] <MTecknology> wow
[17:32] <MTecknology> I wonder how many people will try to go from LP to their own servers...
[17:33] <MTecknology> 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] <Odd_Bloke> Is it all being freed, or just the UI code?
[17:34] <gmb> Odd_Bloke: Everything except Soyuz and codehosting: http://blog.launchpad.net/general/how-we-are-open-sourcing-launchpad
[17:37] <MTecknology> nice
[17:38] <MTecknology> that secret sauce thing is why I was surprised to see it released at all
[17:38] <gmb> 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] <gmb> 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] <Odd_Bloke> Oh crap.
[17:40] <Odd_Bloke> I made the mistake of reading comments on the internet.
[17:40] <MTecknology> I'm not going away, the thought of doing it myself is scary :P - my web server has a 400MHz proc :P
[17:40] <MTecknology> somehow it does a good job though
[17:40] <gmb> Odd_Bloke: Generally not a good thing... why, what's perturbed you?
[17:40] <MTecknology> Odd_Bloke: me too - they're kinda irritating
[17:41] <MTecknology> the only comment of any value was the link to that other article
[17:41] <Odd_Bloke> gmb: The number of complaints about Soyuz not being freed.
[17:41] <gmb> Ah.
[17:42] <gmb> Well, it's a contentious issue in some parts of the OSS world.
[17:42] <MTecknology> 9 is a good comment
[17:42] <MTecknology> can't imagine why
[17:43] <Odd_Bloke> 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] <Odd_Bloke> I'd be interested to see if a Soyuz-a-like is developed once everything else is free...
[17:43] <Odd_Bloke> s/I'd/I'll/
[17:44] <MTecknology> LOL!
[17:44] <MTecknology> ok - so sabdfl is good in an arguement
[18:05] <maxb> 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] <bigjools> on the bright side, you'll get to see the code for the Soyuz UI stuff
[18:10] <maxb> Meanwhile, how about you guys who do have the source get on to fixing those Packages-arch-specific processing bugs? :-)
[18:17] <geser> 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] <cprov> geser: No, I'm sorry, it's not happening in this cycle.
[18:19] <cprov> geser: scratch that, I just have to resurrect the binaries for you, will do that.
[18:19] <geser> thanks
[18:24] <cprov> geser: let's talk about it
[18:25] <cprov> geser: the superseded publication is in intrepid and you want it to be resurrect in jaunty, right ?
[18:25] <cprov> geser: why you can't simply bump the version and do a new upload ?
[18:27] <geser> 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] <geser> for jaunty I could reupload it if it's easier for you
[18:27] <cprov> geser: it is
[18:28] <cprov> geser: also the higher version might be beneficial
[18:28] <geser> ok, will reupload it then
[18:29] <cprov> I'd have to request archive-admin permission to do what you are requesting (intrepid -> jaunty)
[18:29] <cprov> geser: it's better if we do that in the clearest way possible, with a new upload.
[18:29] <geser> so in cases I find another missing deb the preferred solution is to reupload?
[18:32] <cprov> geser: if it's cross-series yes
[18:32] <cprov> geser: if it's in the development series (and it's not frozen) I can re-activate it easily.
[18:33] <geser> ah, ok
[19:23] <daniel_tp> 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] <Ursinha> daniel_tp, what is a trash-email-address? and which is your user id on lp?
[19:28] <daniel_tp> danielkutik
[19:31] <daniel_tp> Ursinha, for example: www.spam.la
[20:07] <AlexC_> g'morning Earthlets
[20:07] <AlexC_> 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
[20:27] <mrooney> danilos: are you around by any chance? I can't figure out how to move over my translations properly to a new series
[20:28] <mrooney> I download the old series PO files, replaced the template with the new one, and upload that
[20:28] <mrooney> and after getting the success email, there are still no translations showing up for that series
[20:44] <mrooney> hmm..maybe I've figured it out...
[21:00] <dsas_> 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] <dsas_> few or 0 bugs are ubuntu specific. The package is maintained in our bzr repo.
[21:01] <dsas_> Currently we have to either check two different lists of bugs or change everything twice
[21:02] <dsas_> bah, sorry for my english, I've open been speaking it 23 years now.
[21:02] <dsas_> only, even.
[21:02] <mwhudson> irc destroys my ability to type
[21:03] <dsas_> maybe thats it, I've been blaming the eeepc keyboard
[21:05] <dsas_> 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] <MTecknology> How do I get my projects license reviewed?
[22:23] <beuno> MTecknology, you poke bac
[22:23]  * bac hides
[22:23] <MTecknology> bac: hi
[22:23] <bac> MTecknology: gimme an URL
[22:23] <MTecknology> bac: don't worry, I'm still making sure I have it right
[22:24] <bac> MTecknology: what is your project named?
[22:24] <MTecknology> loco-drupal
[22:24] <MTecknology> I know the license isn't right yet
[22:26] <bac> MTecknology: how do you expect it to change?
[22:27] <MTecknology> I'm not sure. I'm just running around and trying to make sure I have the right license applied.
[22:27] <bac> MTecknology:it looks ok right now.  the restriction you have seems reasonable.  as long as you don't muck it up with a bunch of CC-NC stuff.  :)
[22:28] <MTecknology> I was kinda hoping to find a link to an ubuntu webpage to explain that paragraph
[22:28] <bac> MTecknology: sorry, i can't help there.  but when you have it finalized just ping me here or send me email (bac at canonical) and i'll take a look.
[22:29] <MTecknology> ok
[22:29] <bac> MTecknology: are you behind 'loco-drupal-dev'?  does it really need to hang around?
[22:33] <mtaylor> launchpad didn't like my code review :(
[22:35] <mwhudson> did it say why?
[22:36] <mtaylor> mwhudson: OOPS-1138CEMAIL12
[22:36] <mwhudson> oh
[22:37] <mtaylor> mwhudson: I was trying out the "approve code review via email" thing
[22:37] <mwhudson> mtaylor: the proposal was already marked "merged"
[22:37] <mtaylor> mwhudson: ah. ok
[22:37] <mwhudson> mtaylor: there is a bug about this, i think it may be fix committed already
[22:37] <mtaylor> mwhudson: about giving a better feedback message?
[22:39] <mwhudson> mtaylor: i can't remember the resolution, that sounds like the absolute minimum fix
[22:39] <mtaylor> awesome. well... good to know
[22:39] <mtaylor> mwhudson: next time I'll try the email review interface _before_ I merge the code
[22:40] <mwhudson> mtaylor: here's the bug https://bugs.edge.launchpad.net/launchpad-bazaar/+bug/326056
[22:40] <mwhudson> it's marked Low, which sounds a bit rubbish
[22:40] <mwhudson> feel free to comment
[22:40] <mwhudson> :)
[22:45] <mtaylor> mwhudson: just did. thanks
[22:49] <mwhudson> mtaylor: thanks
[22:49] <mwhudson> it seems to be one of those "a bug! but to fix it properly, we need to change our data model, argh"
[22:50] <mwhudson> whereas there is a quick fix that will actually help user experience
[22:50] <mtaylor> indeed
[22:51] <mtaylor> those happen to me all them time :)
[22:56] <thumper> mtaylor: that's on my to fix list
[22:58] <MTecknology> What license should I use for my reproduction of the launchpad-openid plugins? We converted it to use drupal 6.x
[23:04] <MTecknology> bac: ping
[23:04] <bac> hi
[23:05] <MTecknology> jonobaconcanonical AT googlemail DOTcom
[23:05] <MTecknology> bac: What license should I use for my reproduction of the launchpad-openid plugins? We converted it to use drupal 6.x
[23:06] <bac> MTecknology: what is the original project name on LP?
[23:06] <MTecknology> I'm not sure...
[23:07]  * bac looks
[23:07] <bac> https://edge.launchpad.net/drupal-openid
[23:08] <MTecknology> oh, I just found https://help.launchpad.net/DrupalPlugins
[23:08] <MTecknology> bac: Metcalfe is in our team too
[23:09] <bac> MTecknology: so you extended one of those modules?
[23:09] <MTecknology> pretty much
[23:09] <MTecknology> his is for drupal 5.x, ours is for 6.x and will be for 7.x
[23:10] <MTecknology> actually, I might talk to him about merging the projects into loco-drupal
[23:10] <bac> MTecknology: why does it need to be a separate project from 'drupal-openid'?
[23:11] <bac> MTecknology: i think stu would be better to advise you on how to manage your work than me.
[23:11] <MTecknology> bac: it's because we just started building on it and wound up keeing it
[23:11] <MTecknology> I'll talk to him for it
[23:11] <bac> can you chat with him when he shows up tomorrow?
[23:11] <bac> thanks
[23:12] <bac> MTecknology: i asked earlier, but did you create 'loco-drupal-dev'?  if so, does it need to be kept?
[23:12] <MTecknology> ya, you can drop it
[23:13] <MTecknology> bac: would I want to keep GPLv2 for the openid stuff, or should I just use GPLv3?
[23:14] <bac> MTecknology: could you file a request in the Answer section of launchpad to delete that project, please?
[23:14] <MTecknology> ok
[23:14] <bac> MTecknology: if the original is "v2" then i think you should keep v2.
[23:14] <MTecknology> ok
[23:17] <MTecknology> bac: done
[23:17] <bac> thanks so much.  clearing out the dross is good.
[23:17] <MTecknology> bac: could you review my license? https://launchpad.net/loco-drupal
[23:18] <bac> MTecknology: gladly.  done.
[23:18] <MTecknology> thanks :)
[23:19] <bac> MTecknology: ttyl.  i'm done for the day.  ping me later if you have need.
[23:19] <MTecknology> bac: aight, thanks much
[23:20] <MTecknology> bac: still here?
[23:20] <bac> yep
[23:21] <MTecknology> how long will it be before a ducky man goes through the answers? I have two requests out there atm
[23:21] <MTecknology> just curious
[23:21] <bac> MTecknology: each day a member of the launchpad team reviews outstanding requests in the answers forum
[23:21] <bac> it's the person listed in the topic for this channel as "help contact"
[23:22] <MTecknology> ok, thanks
[23:22] <MTecknology> I'll bug ya later then :)
[23:22] <bac> they take the shift during their normal working hours, wherever that may be
[23:23] <bac> so henning will take a look tomorrow, german time:  https://help.launchpad.net/HelpRotation
[23:24] <MTecknology> thanks
[23:30] <mathiaz> Hi - does vcs-import support non-trunk/ svn import?
[23:37] <mwhudson> mathiaz: yes, but with caveats
[23:40] <mathiaz> mwhudson: would the following vcs-import be accepted: https://code.launchpad.net/~vcs-imports/dovecot/pkg-debian-1.1?
[23:42] <mwhudson> mathiaz: so the caveat is that if you also import svn://svn.debian.org/collab-maint/deb-maint/dovecot/trunk, the two branches will not be mergeable
[23:42] <mwhudson> mathiaz: if you're ok with that, then yes
[23:43] <mathiaz> mwhudson: because they won't have a common ancestor?
[23:43] <mwhudson> right
[23:46] <mathiaz> mwhudson: so if we track dovecot/branches/1.1-work for now in ubuntu (ie the ubuntu package is based on this branch and the ubuntu pkg branch is based on it) when debian switches to dovecot/trunk/ we'll have to give up all of the ubuntu bzr branch history
[23:47] <mwhudson> yep
[23:47] <mwhudson> bzr-svn handles svn branches much better
[23:48] <mathiaz> mwhudson: so the other solution is that I use bzr-svn and push the resulting branch to lp myself
[23:48] <mathiaz> mwhudson: and not rely on vcs-import
[23:48] <mwhudson> yes
[23:49] <mathiaz> mwhudson: ok - I'll do the latter then.
[23:49] <mathiaz> mwhudson: could you reject/delete https://code.launchpad.net/~vcs-imports/dovecot/pkg-debian-1.1 ?
[23:52] <mwhudson> mathiaz: iz gone