=== RAOF_298 is now known as RAOF_831
=== RAOF_831 is now known as RAOF_61
=== RAOF_61 is now known as RAOF
[00:10] <lifeless> I wonder if 'https://edge.launchpad.net/+search?field.text=launchpad' is worth a bug report :P
[00:12] <swegner> Whenever I install package version from my own PPA, I am prompted with a "this package cannot be authenticated" warning. Is there a signature file I can add to Software Sources to avoid this warning?
[00:13] <lifeless> no
[00:14] <lifeless> there is a bug open on this
[00:14] <swegner> gotcha-- thanks
[00:16] <lifeless> bug 125103
[00:16] <ubottu> Launchpad bug 125103 in soyuz "ppa archives are not signed" [High,Confirmed] https://launchpad.net/bugs/125103
[00:16] <swegner> ahh, thanks, was just searching for it.
[00:27] <lifeless> cute
[00:27] <lifeless> http://www.powerset.com/
[00:31] <lifeless> are there docs on using launchpad apis?
[00:32] <jml> yes. lots.
[00:32] <jml> I've even emailed the URL to you :)
[00:33] <jml> lifeless: https://help.launchpad.net/API is a good starting place.
[00:33] <lifeless> jml: I was google searching etc, utter fail
[00:42] <Hobbsee> who are the bug launchpad guys now?
[00:42] <Hobbsee> or do nominations fall into someone else's territory?
=== hakr is now known as h[a]kr
[00:45] <jml> Hobbsee: not sure.
[00:45]  * Hobbsee discovered an interesting bug there yesterday.
[00:46] <Hobbsee> You can have a simultaneously approved & declined nomination, and once you get to that point, can't either de-approve it, or de-decline it.
[00:47] <jml> two cheers for state machines
[00:47] <Hobbsee> actually, maybe you can de-approve it, but i've forgotten how one tries to do that.
[00:47] <Hobbsee> yup
[00:47] <Hobbsee> and LP oopses if you try to de-decline it.
[00:47] <jml> Hobbsee: well, file a bug *somewhere*, and if it's in the wrong place, it's not that hard for someone who knows better to change it.
[00:48] <Hobbsee> that's true
[00:48]  * jml quite likes that trait of Launchpad's
[00:48] <spiv> Yes, making mistakes cheap to correct is a good thing.
[00:48] <Hobbsee> i look forward to when it works for project/distro-type-mistakes :)
[00:49] <Hobbsee> although it does for questions now
[00:50] <spm> spiv: remind me to show you how "cheap" some of those mistakes are to correct from our perspective... ;-)
[00:50] <spiv> spm: buying you a beer is still pretty cheap ;)
[00:51] <spm> spiv: LOl. especially when I don't drink beer and would just give it straight back. :-P
[00:51] <lifeless> spm: spirits?
[00:51] <spm> lifeless: coke, fanta, OJ et al
[00:51] <spm> *coffee*!!!
[00:51] <lifeless> harder to downcast
[00:51] <lifeless> but it is doable
[00:52] <spm> "buy you a slab of coffee" just doesn't have the same... ring to it
[00:52] <spiv> spm: that's great, because I get a favour done *and* I get a beer :)
[00:52]  * spm goes to install anti-spiv filter....
[00:52] <spiv> A "case of coffee" doesn't sound much better.
[00:52] <jml> cake
[00:53] <spm> indeed - totally OT - spiv - how goes the mo?
[00:53] <jml> First there will be logs, then there will be cake.
[00:53] <spiv> Well!  I'll post another update pic to the mospace thingy tonight.
[00:53] <spiv> I'm looking more like a spiv each day.
[00:54]  * spm has horrified visions of spiv doing a full Boonie mo....
[00:54] <spiv> I'm can't look at a mirror without thinking I look ridiculous, but happily I don't generally look at myself in mirrors all that much.
[00:55] <spm> :-)
[00:55] <spiv> I think you need special Tasmanian genes to achieve a full, luxurious Boonie mo.
[00:55] <spm> hmm. jml?
[00:56] <jml> spm: buying you a beer isn't all that useful, so perhaps cake can be the substitute.
[00:56] <spm> jml: no, the line spiv gave: "<spiv> I think you need special Tasmanian genes to achieve a full, luxurious Boonie mo."
[00:56] <jml> oh, I have no Tasmanian genes.
[00:57] <spm> A poor assumption on my part then. Apologies.
[00:57] <RAOF> You don't pick them up just by passing through :)
[00:57] <jml> a mere decade isn't quite enough to become Tasmanian.
[00:57] <RAOF> Certainly not genetically so :P
[00:58] <spm> heh.I can relate. 18 years in canberra and still consider myself a Qlder. :-)
[00:58] <jml> Queenslanders are funny like that.
[00:59] <jml> actually, I think a disproportionate number of Canonical .au folk are originally from QLD.
[00:59] <spm> "parochial" is the word....
[00:59] <jml> :)
[00:59] <Hobbsee> they must need to hire some more southerners to balance that trend.
[01:00] <jml> well, most of us live in NSW :)
[01:00] <jml> or geometrically inside, in spm's case.
[01:00] <spm> Hobbsee! You missed the perfect line! "You only need a sole southerner to balance X qlder's. Simply better doncha know."
[01:01] <spm> jml: No. Comment. :-P
[01:02] <Hobbsee> spm: haha
[01:02] <spiv> jml: You could say he only ACTs like a NSW resident.  *ba dum tish*
[01:02] <spm> damn. MUST put that anti-spiv filter on.....
[01:02] <spiv> :)
=== h[a]kr is now known as hakr
[01:25] <maco> i can't submit bugs.  i'm using https://bugs.launchpad.net/gwibber/+filebug  I've had on edge where a +filebug won't do anything when I hit the Continue button, but I tried +filebug-advanced (which has always worked for me on edge) and tried disabling redirection and not using edge, and whatever I try, the Sumit and Continue buttons just don't do anything
[01:26] <Hobbsee> noscript?
[01:26] <maco> actually, it looks like the launchpad greasemonkey scripts...
[01:26] <maco> false alarm
=== jamesh__ is now known as jamesh
=== hakr is now known as h[a]kr
=== h[a]kr is now known as hakr
=== hakr is now known as h[a]kr
=== h[a]kr is now known as hakr
=== hakr is now known as h[a]kr
=== h[a]kr is now known as hakr
=== abentley1 is now known as abentley
=== hakr is now known as Guest10635
=== Guest10635 is now known as hakr
=== abentley1 is now known as abentley
=== persia_ is now known as persia
=== miken is now known as absoludity
[07:45] <enurien> hy everybody
[07:46] <enurien> do anyone know, where can I find MrKanister?
[07:47] <enurien> :O:O:O
[07:49] <enurien> ...
[07:58] <mtaylor> kiko: morning... you around?
[07:59] <mtaylor> or any other PPA people - I've got a very odd build error on x86 that doesn't happen on 64bit - except it's not anything that makes sense as to why it's only happening on x86
[07:59] <mtaylor> so I thought it _might_ possibly be a PPA bug?
[07:59] <mtaylor> http://launchpadlibrarian.net/19713425/buildlog_ubuntu-intrepid-i386.protobuf_2.0.2-4intrepid1_FAILEDTOBUILD.txt.gz
[08:00] <wgrant> It could be a race.
[08:00] <Hobbsee> mtaylor: what arch:all packages are you building there?
[08:01] <wgrant> Note how it removes debian/tmp a few lines before it fails to copy something into it...
[08:01] <persia> That, or as it's in Java bindings, perhaps related to arch:all vs. arch:any
[08:01] <mtaylor> hrm.
[08:01] <wgrant> That too.
[08:02] <wgrant> Does it happen on lpia?
[08:02] <mtaylor> Hobbsee: arch: all is just libprotobuf-java and python-protobuf
[08:02] <Hobbsee> sorry, i meant to ask about arch:any, iirc.
[08:03] <mtaylor> nope. lpia builds fine
[08:03] <wgrant> Hmm.
[08:03] <mtaylor> Hobbsee: any: libprotobuf0 libprotobuf-dev  and protobuf-compiler (which has the problem file)
[08:04] <mtaylor> oh, and I re-did the build and got the same error :(
[08:05] <mtaylor> seriously though - what's up with the interleaved dh_clean during the install?
[08:08] <Hobbsee> errr...
[08:08] <Hobbsee> +install: install-indep install-arch
[08:08] <Hobbsee> +install-indep:
[08:08] <Hobbsee> +	dh_testdir
[08:08] <Hobbsee> +	dh_testroot
[08:08] <Hobbsee> +	dh_clean -k -i
[08:08] <Hobbsee> +	dh_installdirs -i
[08:08] <Hobbsee> probably because you didn't put dh_clean last, no?
[08:08] <wgrant> Ehem.
[08:08] <wgrant> Hmm.
[08:09] <Hobbsee> (which would explain why it only happens on i386)
[08:09] <wgrant> dh_clean -k isn't dh_clean at all.
[08:09] <Hobbsee> mtaylor: my guess would be that you'd find switching them worked.
[08:09] <Hobbsee> oh, isn't it?
[08:10] <wgrant> No, confusingly enough,
[08:10] <wgrant>        -k, --keep
[08:10] <wgrant>            This causes dh_prep(1) to be run instead of dh_clean, for backwards compatibility.
[08:10] <mtaylor> sigh
[08:10] <mtaylor> that sounds like a wonderful flag
[08:10] <Hobbsee> but it removes debian/tmp.
[08:10] <Hobbsee> dh_prep is a debhelper program that performs some file cleanups in
[08:10] <Hobbsee>        preparation for building a package. (This is what dh_clean -k used to
[08:10] <Hobbsee>        do.)  It removes the package build directories, debian/tmp, and some
[08:10] <Hobbsee>        temp files that are generated during the build. Putting this at the
[08:10] <Hobbsee>        start of the build process makes the build process idempotent.
[08:10] <wgrant> Oh.
[08:10] <Hobbsee> which will cause the build to blow up
[08:10] <wgrant> Hmmm.
[08:11] <mtaylor> awesome
[08:11]  * Hobbsee looks up what the hell idempotent is
[08:11] <wgrant> So binary-indep depends on stuff installed in binary-arch, or something?
[08:11] <mtaylor> that'll teach me to try to adapt someone else's packaging
[08:11] <jamesh> Hobbsee: it means doing it twice is the same as doing it once
[08:11] <Hobbsee> ah, right.
[08:12] <mtaylor> how about I take dh_clean -k -i out of the install rules
[08:12] <jamesh> not quite the same as "side effect free", since it can have side effects as long as they don't affect output for subsequent calls
[08:12] <mtaylor> and instead stick it up in configure or something
[08:13] <Hobbsee> err, doesn't clean get run after all the installs?
[08:14] <mtaylor> does it?
[08:14] <persia> Why would it be run?
[08:14] <Hobbsee> well, as in, rather than before the installs actually get run.
[08:14] <persia> (unless it's in debian/rules, it probably doesn't happen (ignoring include directives)
[08:15] <Hobbsee> persia: as in, at all?
[08:15] <persia> Hobbsee, Right.  There's a call to debian/rules clean at the beginning of the build, but that doesn't guarantee anything specific.
[08:18]  * Hobbsee tries to remember how this all works
[08:19] <Hobbsee> oh, i thought that got automatically called at hte end, or something.
[08:35] <mtaylor> Hobbsee: wgrant: took out the dh_clean -k  - all worked fine
[08:35] <mtaylor> thanks!
[08:36] <Hobbsee> mtaylor: you're welcome :)
[08:42] <wgrant> Hmmm.
[08:51] <SpunkMeYeR> hi all
[08:51] <SpunkMeYeR> anybody here ever try install nav?
[08:53]  * Hobbsee thinks you want #ubuntu
[08:56] <pygi> SpunkMeYeR, what does this channel has with NAV?
[08:56] <pygi> hi Hobbsee
[08:58] <SpunkMeYeR> because i see this website https://launchpad.net/nav
[08:58] <SpunkMeYeR> so i'm in wrong channel?
[08:59] <pygi> yup yup :)
[08:59] <pygi> it's just being developed on Launchpad
[08:59] <pygi> SpunkMeYeR, #nav
[08:59] <pygi> ;)
[09:00] <SpunkMeYeR> thanks pygi, but i already try that <-- no body can help :(
[09:01] <Hobbsee> hey pygi
[09:01] <Hobbsee> oh, right
[09:01]  * Hobbsee assumed nav was an ubuntu package or something
[09:01] <pygi> Hobbsee, long time no see :)
[09:01] <Hobbsee> pygi: indeed!
[09:01] <pygi> Hobbsee, I assumed it was that Microsoft thingy :)
[09:02] <Hobbsee> heh
[09:02] <pygi> well, it's more known then this thingy xD
[09:02] <pygi> SpunkMeYeR, heh
[09:04] <pygi> SpunkMeYeR, well, I guess wait there, devs might come sooner or later :)
[09:04] <SpunkMeYeR> yup.. maybe they are busy or something :)
[10:12] <StFS> hello, I'm wondering whether launchpad is a "service" type of thing only or whether it's possible (easy) for me to set up my own instance of launchpad? I know there is a project for the launchpad code (on launchpad) but I haven't found much documentation about how to deploy it in my own infrastructure.
[10:13] <mwhudson> it's a service type thing
[10:14] <StFS> ok, thanks
=== sabdfl1 is now known as sabdfl
[12:33] <wB3> Sorry, there was a problem connecting to the Launchpad server.  -- http://bazaar.launchpad.net/~bzr/bzr/trunk/files
[12:35] <spiv> wB3: try again, sometimes loggerhead (the software for browsing inside bzr branches) is a bit slow.
[12:35] <wB3> ok, up
[12:35] <wB3> thank you
=== verterok_ is now known as verterok
[12:45] <voland> Good day to you all. Could anyone help me to setup my ppa?
[12:47] <bigjools> voland: how can I help?
[12:47] <cprov> voland: sure, did you follow https://help.launchpad.net/Packaging/PPA ?
[13:02] <voland> i cannot upload my packages using dput
[13:03] <voland> i've recived e-mail titled "rejected"
[13:03] <voland> and yes, i followed url above
[13:04] <Hobbsee> did it say why?
[13:05] <voland> yes, it says: Rejected:
[13:05] <voland> Unable to find distroseries: interpid
[13:05] <voland> Further error processing not possible because of a critical previous error.
[13:05] <Hobbsee> voland: well, that should be fairly obvious.   you've mispelt 'intrepid'
[13:05] <Hobbsee> in debian/changelog
[13:07] <Hobbsee> fortunately, it's simple to fix!
[13:07] <voland> oh Lord! Thank you very much. By the way, in my profile in Launchpad it said that my ppa is for jaunty
[13:07] <voland> can i change it to 'intrepid'
[13:07] <Hobbsee> :)
[13:07] <Hobbsee> it will automatically change to intrepid when you upload something for intrepid
[13:07] <Hobbsee> iirc
[13:08] <bigjools> yes
[13:08] <voland> thank you again
[13:08] <Hobbsee> you're welcome!
[13:17] <voland> now it says: Section 'office' is not valid
[13:18] <voland> which section shoul i use for office application?
[13:20] <persia> voland, From what do you get that message?
[13:20] <persia> The reject mail from the PPA?
[13:21] <voland> it was e-mailed to me after dput upload
[13:21] <voland> section 'offie' is in debian/control
[13:22] <cprov> voland: 'office' is not a valid intrepid section. The fact that we don't publish the valid sections for a distroseries in LP is a bug
[13:22] <persia> Interesting.  That might be a bug.  It might mean you have to use something listed in debian-policy.  I'm not sure if PPAs follow the same policy, but it's likely they do: http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections
[13:23] <voland> so what shoul i do? leave it blank?
[13:23] <cprov> persia: do you know if there is a easy way to list them all using dpkg/apt ?
[13:23] <persia> cprov, I don't.  How do you determine if they are valid?
[13:23]  * persia checks how lintian does it
[13:24] <cprov> voland: if you omit Section:  it will default to 'misc'
[13:25] <voland> i'll take a try
[13:25] <cprov> persia: it's a manually defined collection in LP. I was thinking more like 'Mr dpkg, return all unique sections in my archive index cache, please.'
[13:25] <voland> thank you
[13:27] <persia> cprov, It's hardcoded in lintian, so I'm guessing there's no easy way to extract it from dpkg.
[13:27] <cprov> persia: okay, a stronger reason to list them in LP, I guess.
[13:27] <persia> cprov, Hrm.  I don't think dpkg can do that, but it shouldn't be hard to extract from a set of Packages files.
[13:28] <persia> On the other hand, you probably don't want a section becoming valid just because a stray package got in somehow.
[13:28] <persia> Debian hardcodes to enforce policy control by ftp-masters.  For Ubuntu, the equivalent is roughly archive-admins.  If you made it settable, they'd probably be the group that would want to be able to adjust it.
[13:29] <voland> so there is no page in LP where theese sections listed?
[13:29] <cprov> persia: yes, good point.
[13:29] <persia> voland, No, which is the bug.
[13:29] <voland> sad :(
[13:30] <persia> cprov, Especially if LP ever grows even more distribution-neutral (I think all the imported distros have the same Section policy currently), this could be important.
[13:30] <cprov> file a bug, I don't remember of seen it before.
[13:30] <persia> voland, Do you want to file the bug, or shall I?
[13:30] <persia> cprov, Which component?  Soyuz?
[13:31] <voland> persia, I'm afraid I have no such expirience to decribe it :) so please do it
[13:31] <cprov> persia: yes, please.
=== lamont` is now known as lamont
[13:33] <voland> persia, sorry for mispell
[13:35] <voland> another one question from ppa newbie :) how can i add my deb into ppa?
[13:35] <cprov> voland: golden question
[13:36] <cprov> voland: you don't .. PPA is a build service, you upload sources and it will build the binaries for you.
[13:37] <voland> :) it's a miracle! :) i'm dumbest person in the world :)
[13:37] <cprov> voland: does it make sense ?
[13:38] <cprov> voland: no worries, it's a very common doubt, people don't believe in such a coolest service when they first see it ;)
=== mrevell is now known as mrevell-luncheon
[13:53] <Ng> http://www.artima.com/weblogs/viewpost.jsp?thread=242653
[13:54] <cprov> persia: great bug report, thank you.
[13:55] <persia> cprov, Thanks for the feedback :)
[14:09] <voland> i've uploaded files to LP, but build fails: checking for pkg-config... no
[14:09] <voland> checking for PACKAGE... configure: error: The pkg-config script could not be found or is too old.  Make sure it
[14:09] <voland> is in your PATH or set the PKG_CONFIG environment variable to the full
[14:09] <voland> path to pkg-config.
[14:10] <voland> but it works on my machine
[14:13] <persia> voland, Check your Build-Depends.  Your local environment is probably dirty.
[14:16] <voland> ok
=== cprov is now known as cprov-lunch
[14:18] <voland> persia, and where i can check them
[14:19] <voland> sorry for dusturbing you
[14:19] <persia> voland, It's in debian/control.
[14:20] <persia> Also, while this is a great channel to discuss issues with a PPA, it's not really a great channel to learn packaging.
=== fjlacoste is now known as flacoste
[14:28] <voland> persia, sorry :)
[14:30] <persia> voland, It's not a big issue, it's just that it distracts the LP developers.  I'd recommend setting up a local sbuild if you want to investigate things in depth: saves uploading and trying to decode the output.
=== mrevell-luncheon is now known as mrevell
=== abentley changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Need help? Community help contact: - abentley
=== sale_ is now known as sale
=== thekorn_ is now known as thekorn
[15:48] <Odd_Bloke> Is there a publically-accessible roadmap for Launchpad becoming free software?
[15:54] <kiko> Odd_Bloke, not yet, but I think it will be publicized in december.
[15:54] <kiko> that's my plan
[16:01] <Odd_Bloke> kiko: OK, that's pretty cool.  Thanks. :)
=== kiko is now known as kiko-fud
=== kiko-fud is now known as kiko
[17:18] <beuno> Hobbsee, kirkland, https://bugs.staging.launchpad.net/bzr/+bug/139202
[17:18] <ubottu> Launchpad bug 139202 in bzr ""Could not acquire lock" error doesn't tell you how to fix it" [Medium,Fix released]
[17:19] <kirkland> beuno: awesome ;-)
[17:19] <kirkland> beuno: works for me ;-)
[17:19] <beuno> fantastic, that's just waiting there to roll out to production
[17:20] <beuno> so it's out of my hands now
=== bac is now known as bac_lunch
[18:25] <tgm4883_laptop> I received a rejected email when uploading a package to my PPA.  The email stated the reason was "Unable to find distroseries: hardy intrepid".  According to debian-policy http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog  I should be able to have a space separated list of distributions in my changelog.  My changelog line looks like "mythnettv-gui (1.0~bzr32-0ubuntu1) hardy intrepid; urgency=low"  Is th
[18:25] <tgm4883_laptop> ere a reason Soyuz doesn't allow this?
[18:26] <beuno> tgm4883_laptop, I don't think you can do that with PPAs
[18:26] <beuno> you probably have to upload twice to different series
[18:26] <tgm4883_laptop> yes I can see that, but my question is why?
[18:27] <tgm4883_laptop> was there a conscious reason for Soyuz to not allow that or was it an overlook of debian-policy?
[18:27]  * beuno pokes cprov-lunch or bigjools 
[18:27] <beuno> kiko, ^  do you know?
[18:55] <vvinet> tgm4883_laptop: from what I've seen, you must upload it to a single distro
[18:55] <vvinet> then from launchpad you can copy it to other distros
=== thumper_laptop is now known as thumper
[20:00] <cprov-lunch> tgm4883_laptop: simple answer is: because it's not implemented.
[20:01] <cprov-lunch> tgm4883_laptop: see https://bugs.edge.launchpad.net/soyuz/+bug/235064
[20:01] <ubottu> Launchpad bug 235064 in soyuz "Implement multi-release support for packages" [Undecided,New]
=== bac_lunch is now known as bac
[20:59] <hunk4ths> sorry ,  in launchpad i public my projects ??
[20:59] <hunk4ths> projects in PHP
[21:51] <jml> abentley: should I take over the topic now?
[21:51] <abentley> jml: Please do.
=== jml changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Need help? Community help contact: - jml
[22:19] <fta> i'm still suffering from several "FATAL: kernel too old" with my ppa :( any progress on that?
[22:19] <CarlFK> lp.net is an Open ID provider, right ?
[22:19] <cprov-lunch> fta: no, sorry.
[22:20] <thumper> CarlFK: AFAIK
[22:20] <CarlFK> https://launchpad.net/~carl-personnelware  thats 'me' - so what do I put in http://www.ustream.tv/login-signup  "Open ID Login"  ?
[22:22] <CarlFK> hmm.. maybe I have to create an account there first.  i am still confused by OID things
[22:26] <jml> CarlFK: your user page on edge should have an openid url. not sure about launchpad.net -- lemme check
[22:26] <CarlFK> jml: what is  "on edge" ?
[22:27] <jml> CarlFK: https://edge.launchpad.net/~carl-personnelware
[22:27] <jml> CarlFK: it's a version of Launchpad for beta testers.
[22:27] <jml> CarlFK: but, I can see my openid login on https://launchpad.net/~jml
[22:28] <jml> CarlFK: on other websites that support openid, I've just pasted it in on the registration form
[22:29] <CarlFK> you pasted  https://launchpad.net/~jml ?
[22:29] <jml> CarlFK: no, there's a URL that's displayed on that page, next to a label saying "OpenID login"
[22:30] <jml> CarlFK: if you can't see it, it might be an "only for beta testers" thing -- in which case, would you like to be a beta tester?
[22:30] <CarlFK> sure
[22:30] <CarlFK> that's about all I do :)
[22:30] <jml> CarlFK: :)
[22:30] <jml> CarlFK: ok, I haven't done this before so give me a minute.
[22:31] <CarlFK> beta beta...
[22:31] <jml> CarlFK: ok. try reloading your LP home page.
[22:32] <CarlFK> "               Launchpad Beta Testers                 Joined       29 seconds ago     "
[22:32] <CarlFK> but still no open id
[22:32] <jml> hmm.
[22:33] <jml> nothing that says "id.launchpad.net"?
[22:33] <CarlFK> wait... im not logged into lp..
[22:33] <CarlFK> er,, not loged into edge...
[22:33] <kiko> CarlFK, jml: note that we're going with launchpad.net/~foo as the sekrit plan
[22:34] <jml> kiko: cool.
[22:34] <kiko> the numbers thing just.. was too much for too little
[22:34] <CarlFK> OpenID login ... yay.
[22:35] <CarlFK> kiko: mum's the word
[22:42] <Hobbsee> i wish launchpad would provide some information about not assigning bugs to big teams.
=== hakr is now known as h[a]kr
[22:42] <Hobbsee> or at least, forbid certain teams being assigned to bugs, controllable by the drivers of each project.
[22:43] <jml> Hobbsee: the actual problem being unwanted bug mail?
[22:43] <Hobbsee> jml: yes
[22:43] <Hobbsee> jml: and the fact that it's useless to assign certain teams to bugs
[22:43] <Hobbsee> (unless they have a specific workflow that way)
[22:44] <Hobbsee> beuno: er, i think you meant that link for persia?
[22:45] <jml> Hobbsee: actually, I didn't even know you could assign bugs to teams :)
[22:45] <Hobbsee> jml: oh, you can.  Including ones with 80 people :P
[22:45] <Hobbsee> i think it's 80, anyway
[22:46] <jml> Hobbsee: who's assigning these bugs anyway?
[22:47] <Hobbsee> jml: clueless users, i think.  The main case seems to be "look up the maintainer, file the bug, assign the bug to the maintainer"
[22:47] <Hobbsee> unfortunately, the maintainer is a team of ~80 people.
[22:47] <Hobbsee> as we do group maintainership
[22:47] <jml> *nod*
[22:48] <jml> Hobbsee: these are users who are forbidden from setting the priority, right?
[22:48] <Hobbsee> jml: i expect so.  No one would manage to make it thru to -quality if they consistently made errors like that.
[22:48] <jml> (do you see where I'm going with this?)
[22:48] <Hobbsee> ah.  Yes.
[22:48] <Hobbsee> for teams, or for assigning anyone?
[22:49] <jml> Well, I'd start with assigning anyone, because it's a simpler idea.
[22:49] <Hobbsee> well, being able to assign an individual to a bug, as anyone, is useful.
[22:49] <Hobbsee> a lot of -quality hopefuls do that, as they're taking responsibility to track down a bug
[22:50] <Hobbsee> so, i don't think it's overly helpful to drop that use case, even though it's simpler
[22:50] <jml> assigning a bug to yourself is different from assigning it to someone else though
[22:50] <Hobbsee> that's true, but there are certainly use cases of "oh, file a bug on launchpad, and assign or subscribe me, please"
[22:51] <Hobbsee> i don't think the annoyance factor for sending mail to one person is that high, either.  Usually they'll have had something to do with it, for the user to think of assigning them at all.
=== h[a]kr is now known as hakr
[22:51] <Hobbsee> either because they've modified it recently, or asked them to file it, or whatever
[22:51] <Hobbsee> in which case, the assignment is likely to be valid - or they'll already receive the bug mail anyway
[22:51] <Hobbsee> (if they're subscribed to the project, for eg)
[22:52] <Hobbsee> 55 active (ubuntu-core-dev) and 112 active (ubuntu-dev).  it's gone up!
[22:54] <beuno> Hobbsee, I don't think so
[22:54] <beuno> it's the onw where you can copy n paste bug #
[22:54] <Hobbsee> beuno: right.  Then Ithink you got the wrong number, as ubottu agrees with me - it's a bug about bzr lock.
[22:54] <Hobbsee> beuno: but, cool :)
[22:55] <beuno> Hobbsee, right, it's the first bug I had in my history  :)
[22:55] <Hobbsee> ah :)
[22:56] <Hobbsee> no wonder i couldn't guess the context, then :P
[22:56] <jml> Hobbsee: I've filed https://bugs.launchpad.net/malone/+bug/299257
[22:56] <ubottu> Launchpad bug 299257 in malone "Too easy to spam a team by assigning a bug to them" [Undecided,New]
[22:57] <Hobbsee> jml: ah, cool
[22:58] <jml> Hobbsee: it's *almost* a dupe.
[22:58] <Hobbsee> jml: yes, almost.  It's two ways to go about solving the same problem.
[22:58] <jml> Hobbsee: well, "subscribe" and "assign" are different features and could arguably have different workflows.
[22:59] <Hobbsee> jml: that's true
[22:59] <Hobbsee> and some teams are legitimately supposed to be subscribed.
[23:00]  * Hobbsee isn't quite sure why ubuntu-dev, ubuntu-core-dev, etc, have no /dev/null mailing list, either.
[23:03] <Hobbsee> jml: do you know what happened to fix it friday?
[23:04] <jml> Hobbsee: yes. it died.
[23:04] <Hobbsee> jml: why?
[23:05] <jml> Hobbsee: quite a few reasons.
[23:05] <jml> Hobbsee: many of which require extensive narration to fully explain.
[23:06] <jml> Hobbsee: we need a thing *like* the old fix-it-friday though.
[23:06] <Hobbsee> ahhh
[23:06] <Hobbsee> yes
=== jml changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Need help? Community help contact: - jml (afk)
=== jml changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Need help? Community help contact: - jml