[04:31] <radix> does SteveA generally disappear for the weekends?
[04:32] <LarstiQ> radix: I haven't really paid attention to that
[04:32] <Burgundavia> radix, likely, as he is paid to work on lp
[04:34] <radix> right :)
[08:20] <LarstiQ> oeh!
[08:20] <LarstiQ> someone implemented subscribed bugs in the web interface!
[09:05] <lifeless> stub: ping
[09:05] <stub> lifeless: pong
[09:05] <lifeless> i just nuked 3 corrupt jobs
[09:06] <lifeless> you have sftp://chinstraphome/warthogs
[09:06] <lifeless> and variations thereupon
[09:06] <stub> 2 corrupt jobs, and I just fixed bzr-submit-merge on the wiki so others don't have the same problem
[09:06] <lifeless> thanks
[09:06] <lifeless> whats your x-push-data file contents ?
[09:07] <stub> chinstrap:/home/warthogs/archives/stub/dists/devel/
[09:07] <stub> There seemed to be a missing '/' in bzr-submit-merge. 
[09:07] <lifeless> hmm
[09:07] <lifeless> copied and pasted from my working one
[09:07] <lifeless> ah-oops
[09:41] <sivang> moins all
[01:14] <shawarma> Hi! Is there  any way to view the complete list of specifications?
[01:39] <Hieronymus> hello
[01:40] <Hieronymus> How come the French translation page in Rosetta lists more packages than the Dutch one?
[01:40] <Hieronymus> https://launchpad.net/distros/ubuntu/dapper/+lang/fr and https://launchpad.net/distros/ubuntu/dapper/+lang/nl
[06:21] <LarstiQ> hmm, I don't see a distinction between Serbian in Cyrillic and Latin anywhere
[07:50] <\sh> guys, is it possible to have the support tracker tool on launchpad to work as well for teams, like an "RFP" tracker for MOTU?
[07:51] <\sh> let's say, I select the "MOTU" team, and file a support ticket for having "shiny-software-5.0" packaged for universe?
[07:51] <sivang> \sh: does the moto have something like that currently?
[07:51] <\sh> sivang: well...a wiki page
[07:52] <\sh> UniverseCandidates..which is for this purpose a but degenerated...we thought about using RT but if there is something like a support tracker in LP...why not using this
[07:52] <\sh> s/but/bit/
[07:52] <sivang> \sh: if it supports the notion of group assignments of requests and has sufficient enough emailing interface , ofcourse
[07:53] <\sh> sivang: yes..but https://launchpad.net/people/motu/+tickets doesn't show up anything to create a ticket :)
[07:54] <shawarma> Hi! Is there  any way to view the complete list of specifications?
[07:55] <sivang> \sh: hmm, maybe we need it to be a "motu" product? :)
[07:55] <\sh> shawarma: all approved, or actually all?
[07:55] <shawarma> \sh: either.
[07:55] <sivang> \sh: seems issues are only registered against a product, not a team
[07:55] <\sh> shawarma: https://launchpad.net/distros/ubuntu/+specs
[07:55] <shawarma> \sh: I'd really like to take a look at all the Ubuntu Server specs to see if there's anything I can work on, but I can only view the 10 newest.
[07:55] <\sh> sivang: jepp...product or distro
[07:56] <\sh> shawarma: see the url
[07:56] <sivang> \sh: We need to ask Bjorn about that then
[07:56] <shawarma> \sh: How on earth did you find that?
[07:56] <\sh> shawarma: well..I used it when I was in the reviewing team during UBZ :)
[07:56] <shawarma> \sh:I've been clicking everywhere, but never been able to find anything but the 10 most recently added.
[07:57] <shawarma> \sh: Well, thank you!
[07:57] <\sh> shawarma: to see even the assignees https://launchpad.net/distros/ubuntu/+specstable
[07:58] <\sh> shawarma: you're welcome..even when i'm totally clueless...as I had to read a couple of minutes ago ;)
[08:01] <bercik> hey 
[08:01] <bercik> when I get e-mail with activation?:p
[08:01] <BjornT_> \sh: so, basically you'd want it to be possible to open a ticket on a team, that's not necessarily associated with a product or distribution?
[08:02] <sivang> BjornT_: you're here? :-)
[08:02] <\sh> BjornT_: that's what I thought about...well..thinking of MOTU it belongs to distro ubuntu ... but is in need of this feature :)
[08:02] <bercik> when I get e-mail with activation?:p sorry for my englisch ;p
[08:02] <BjornT_> sivang: of course :)
[08:02] <bercik> english ;p
[08:05] <BjornT_> \sh: yeah, although i would guess that if someone request support to MOTU, it's always about ubuntu. the same is probably true for most teams.
[08:06] <\sh> BjornT_: yes, right, but this is special..it's a type of debians "RFP" or "ITP" 
[08:06] <\sh> process
[08:06] <sivang> BjornT_: why does it make a difference? I would think that being able to open a ticket against a team would be possible without having to associate it with a distro product
[08:06] <\sh> so to have a package to hit ubuntu, it needs to go to universe first...
[08:09] <LarstiQ> bercik: it was immediate for me
[08:11] <BjornT_> \sh: i'll have to think about it will fit into the changes to the support tracker that will happen. could you file a bug about it (or better, create a spec ;), so i won't forget it?
[08:12] <\sh> BjornT_: sure...but not today..let me do it tomorrow :) 
[08:12] <BjornT_> \sh: sure, thanks :)
[08:12] <\sh> BjornT_: spec to launchpad product? or ubuntu?
[08:12] <BjornT_> \sh: launchpad
[08:13] <\sh> BjornT_: k...you'll get your spec :)
[08:18] <sivang> BjornT_: are you also working on the spe tracker?
[08:18] <BjornT_> sivang: well, it does make a difference some difference, as how to implement it. my point was that you probably don't need to have the possibility to associate with both a product/distribution and a team, which makes it somewhat easier.
[08:19] <sivang> BjornT_: I had the same though :) we could be following ticket against ---->team---[assoc. with $DISTRO] .
[08:19] <BjornT_> sivang: i hope not :) actually, i'm probably going to be the one implementing email notifications for it.
[08:20] <sivang> BjornT_: email interface for the spec tracker you mean?
[08:20] <BjornT_> yeah
[08:21] <BjornT_> https://wiki.launchpad.canonical.com/SpecTrackerEmailInterface
[08:21] <BjornT_> (it's only a rough braindump so far, though)
[08:22] <sivang> anyway, re: tickets against team, those tickets could be indirectly assoc. with a distro through the team assoc itself. Does that sound sane?
[08:24] <sivang> BjornT_: hmm, I need to make some time and help you out with that rough braindump. maybe add some ideas etc..
[08:24] <BjornT_> sivang: yeah, that sounds sane.
[08:24] <BjornT_> sivang: that would be really great
[08:28] <sivang> BjornT_: I had some ideas back then, maybe I can refine and use my spare moments tomorrow at work to add them. Also, do you know if you could inherit email interface of support/malone trackers and just change syntax and semantics?
[08:29] <\sh> sivang: why?
[08:29] <sivang> \sh: what why? :)
[08:29] <\sh> Also, do you know if you could inherit email interface of support/malone trackers and just change syntax and semantics?
[08:30] <\sh> the syntax can stay like it is...the status fields has to be changed :)
[08:31] <sivang> \sh: ah, that's actually waht I meant. but to allow greater flexiabilty (ouch, here is that word again) you might want to have better extended semantics for support tickets that a bug tracker might not support or expose
[08:32] <sivang> not support/expose by design, that is
[08:32] <\sh> sivang: well...actually a support ticket is a subview of a bug ticket..everything what a support ticket can have, could be filed even in a bug ticket...
[08:33] <\sh> sivang: IMHO !! :)
[08:34] <sivang> :-)
[08:34] <\sh> .oO(I have no clue!)
[08:34] <\sh> I should trademark this statement 
[08:34] <BjornT_> sivang: yeah, the support email interface will probably be similar to malone's.
[08:34] <sivang> \sh: LOLO
[08:35] <\sh> BjornT_: but get rid of the gpg signed email for filing bugs/support tickets...
[08:35] <ajmitch> \sh: you sound like bddebian
[08:36] <sivang> but, thinking in general terms, what about things like price quotes per ticket, departments invovled, status (which is basically different from a bug status) etc..
[08:36] <LarstiQ> ajmitch: what, about trademarking? :)
[08:36] <sivang> as I see it, a support ticket might sometime have more data over a bug -
[08:36] <ajmitch> LarstiQ: no, the 'I have no clue' thing
[08:36] <\sh> BjornT_: or think a bit more complicated: if it's a gpg signed mail, which identifies user X which is in team A and is able to change the status and some other stuff for the bug/support ticket, then allow him to do it...if there is no gpg signed mail, drop all action keywords 
[08:36] <LarstiQ> ajmitch: yeah, that is what I mean
[08:37] <BjornT_> \sh: i'll see what i can do. it requires some discussion, but i think it should be possible to file a bug without having a gpg key.
[08:38] <\sh> BjornT_: well..the possibilty must be given, to send always a gpg signed mail to create a special report with action keywords in it, to file it directly to a special assignee or set a status != new
[08:38] <\sh> anyways back to my merges :)
[08:38] <\sh> which i'm doing without a clue ,)
[08:40] <sivang> a bug should ideally be a technical description of a technical system specific problem. While a support ticket need not always result in a bug. 
[08:41] <sivang> \sh: why do you keep saying you have no clue? you seem to have more clue then everybody else. The fact I don't say I have no clue doesn't make me less clueless
[08:41] <BjornT_> \sh: yeah, something like that. when i have time i will bring it up with the others for discussion.
[08:41] <\sh> sivang: read ubuntu-devel ml...then u know why :)
[08:42] <sivang> \sh: I wish I could :-( pitti's server has been hacked and we need to wait for monday so the server farm compnay will restore a backup :...-(
[08:43] <\sh> sivang: say this again? hacked? pittis server?
[08:43] <sivang> err ops /me runs
[08:43] <sivang> actually that was a lie
[08:43] <\sh> didn't he install the latest security patches?
[08:43] <sivang> :)
[08:43] <\sh> hehe...I'll tease him with this :)
[08:43] <sivang> well, it was mostly a DoS
[08:43] <sivang> \sh: please don't, I don';t know if I was supposed to tell about it :)
[08:43] <\sh> sivang: I know how it feels to be hacked
[08:43] <\sh> sivang: well..it's logged now :)
[08:44] <\sh> but do not worry
[08:44] <sivang> \sh: I really don't understand what people have to be hacking with piware.de, such a wonderful server with a wonderful name
[08:44] <\sh> sivang: hackers don't do this..these are scriptkiddies
[08:44] <sivang> yes
[08:44] <sivang> that is why I said crackers :-) 
[08:44] <ajmitch> sivang: you just announced it on a publically logged channel :P
[08:45] <sivang> erm
[08:45] <\sh> not even crackers...crackers are cracking copy protection
[08:45] <\sh> or phreaking..
[08:47] <sivang> (and logs)