[00:10] bman2: do a search for bugs you are subscribed to [00:10] bman2: and then, as appropriate, unsubscribe from the bug; unsubscribe the team(s) you're in from it, or leave the team(s) subscribed to it. [00:11] e.g. if you're in a product qa team you might reasonably expect that team to be subscribed to its products bugs :) [00:11] nah [00:11] its lists for laundpad itself [00:11] i use myown sso [00:11] how do i search? [00:16] bman2: https://bugs.edge.launchpad.net/bugs/+bugs?advanced=1 === Ursinha is now known as Ursinha-afk === Lcawte is now known as Lcawte|Away === Ursinha-afk is now known as Ursinha [02:03] did bug expiry ever end up being reenabled? [02:04] there is a spec [02:04] / wiki page thingy [02:04] I saw an edit go by the other day [02:04] is that a "no"? [02:05] not complaining, just confused [02:05] https://help.launchpad.net/BugExpiry and the ui imply it's active [02:05] Current schedule is for right after Maverick. [02:05] oh [02:05] so 'no' [02:05] It was going to be around now. [02:05] coming, but it needed more work [02:05] But Ubuntu wanted it delayed. [02:05] something like: [02:05] - ubuntu needed some tweaks [02:06] - ubuntu gets turned on [02:06] - other people can opt in after that [02:06] that's fine, i just want the docs to reflect reality [02:07] https://dev.launchpad.net/Bugs/CommuncationForBugExpiry [02:09] thanks [02:27] * poolie contemplates writing an api client to copy tracebacks from the attachment into the description and bug title [02:27] poolie: Sounds like you need apport. [02:28] i have one; can it be told to do that? [02:28] I thought it did by default. [02:29] then i will try to work that out before duplicating it, thanks [02:30] For Ubuntu it certainly does. [02:30] hm [02:30] so i think we have a few problems [02:30] one is that i don't think it ever copies the stack trace into the bug description? [02:30] (or does it?) [02:31] and i really find that helpful for bzr [02:31] the other is that users tend to upload crash files manually rather than using apport-bug [02:31] maybe we can steer them towards it [02:31] oh another is they may be on windows and just paste a log file, not using apport at all === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [03:51] lifeless: convert to question is still broke on edge [03:52] micahg: yes, for that bug [03:52] micahg: I have a branch that takes us a good way towards knowing why [03:52] lifeless: ok :), I got worried when I saw your post about lowering the timeout [03:52] micahg: hopefully that will land today; and in a follow up I'll instrument mail, memcache etc [03:53] micahg: well, convert to question isn't *systematically* broken [03:53] micahg: its db times were very reasonable IIRC [03:53] lifeless: yeah, it just timeouts [03:53] micahg: so its got a bad scaling factor in it which means it breaks sometimes [03:53] we will definitely fix it [03:53] * micahg must just have bad luck with it :) [03:53] lifeless: so, with the lower timeout, I should file bugs again for oopses? [03:54] micahg: you always should if they are not in https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=timeout [03:54] micahg: or if its not a timeout oops [03:54] k [03:55] micahg: we've fixed lots this last month [03:55] * micahg adds that to LP links [03:56] micahg: note that aiming for -0- timeouts is not a sane goal, we'll aim to minimise, but things will always happen [03:56] lifeless: of course, the convert to question one is just one I hit every time on edge :) [03:56] micahg: sorry! you hit it on prod too though right ? [03:57] lifeless: yes, about half the time [03:57] it may get a little worse [03:57] this will get it fixed sooner [03:57] lifeless: now I know where to check for timeout bugs though, so I'll file new ones if I hit something [03:57] please do. [03:58] if I don't have time to code for LP at least I can report bugs :) === Ursinha is now known as Ursinha-zzz === jamesh_ is now known as jamesh === henninge_ is now known as henninge === bpeel_away is now known as bpeel === danilo_ is now known as danilos === leoquant is now known as diebleierneZeit [10:36] Hi, anyone about? [10:37] Ryuzaki`: Sure. [10:38] Ideally a Canonical LOSA? Problem is, I can't recall which e-mail address I've currently got my Launchpad account on, as I've swapped about domains when they've been used for different things [10:39] Ryuzaki`: Do you know your Launchpad username? [10:39] So I can't log in, as I can't recall exactly which address is current for my LP account [10:39] I do know it, yeah [10:39] What is it? [10:40] * Ryuzaki` points wgrant to PM [10:40] Ah, so your email address is private. [10:40] So you do indeed need a LOSA. [10:41] LOSA ping: ^^ [10:41] so what's the account? === Lcawte|Away is now known as Lcawte [11:06] Incidentally, *why* do we log into LP using an email address, not an account id? [11:07] A good reason now is that accounts don't have non-numeric identifiers besides an email address. [11:07] As for the original reason? No idea. [11:30] it is possible to log-in with ones @ubuntu.com email address? never tried this [11:34] geser: If you've added it to your Ubuntu Single Sign On account. [11:38] Ubuntu SSO account? is that different from my LP account? [11:40] wgrant: we didn't want to expose numeric ids. we started with basic auth, with the username. [11:40] geser: Um, sort of. [11:41] geser: Your Launchpad account is knows the identity of your SSO account. login.launchpad.net and login.ubuntu.com use the SSO account. [11:44] is there a seperate page for my SSO account? e.g. to configure the attached e-mail addresses or change the password or comes this from the LP account? [11:44] geser: Email addresses are configured separately (on login.ubuntu.com or login.launchpad.net). [11:44] And passwords aren't on LP any more [11:47] * geser didn't notice this change === Ursinha-zzz is now known as Ursinha === kiko` is now known as kiko === dendrobates is now known as dendro-afk === robbiew is now known as robbew === robbew is now known as robbiew === bilalakhtar_ is now known as bilalakhtar === Ursinha changed the topic of #launchpad to: http://launchpad.net/ | Read https://help.launchpad.net/ for help | Help contact: Ursinha | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/ [16:15] hi [16:15] is it normal that PPA's APT archive has packages which are not visible on LP PPA page? [16:16] yes, click on the "View Packages" link [16:16] https://edge.launchpad.net/~hrw/+archive/arm-cross-compiler/+packages does not list libc6-armel-cross [16:17] result of armel-cross-toolchain-base build === matsubara is now known as matsubara-lunch [16:18] * bigjools pokes around [16:20] and (as expected) my next package failed to build cause did not found those in PPA's APT === Ursinha is now known as Ursinha-lunch [16:21] that won't be the reason it failed [16:22] The following packages have unmet dependencies: libc6-dev-armel-cross : Depends: libc6-armel-cross (= 2.12.1-0ubuntu1) but it is not going to be installed [16:22] hrw: it looks like you're creating arch-all packages of the same version [16:23] see http://launchpadlibrarian.net/54778928/upload_1945934_log.txt [16:23] "The following files are already published in ..." [16:23] and the old binaries got superseded too early [16:23] bigjools: it is first time when this package built on both archs [16:24] I suspect you're generating the same package on both arches [16:24] yes, will have to change that [16:24] and one is trying to supersede the other [16:24] same arch-all package I mean [16:24] but why amd64 build (first finished) published only amd64 packages but arch:all ones got to APT? [16:25] we only build arch-all on i386 [16:25] I'm not sure of that [16:25] ok, I am now preparing new version of package. will delete current one [16:25] hrw: don't delete [16:25] just increment the version [16:25] the old version will be automatically superseded [16:26] I know, but I prefer to not ship broken versions in meantime [16:26] ok [16:26] I'm guessing that your package is generating files that are not in the control file? [16:26] I'm not a packaging expert, so that's a guess [16:27] man, it is far more complicated [16:27] yes, it usually is :) [16:27] my package runs dpkg-buildpackage internally, then select set of packages, run some of them though dpkg-cross, then mangle them. then generate debian/control and debian/files [16:29] yeah it will struggle to show much in the UI since the source package doesn't tell the whole story [16:29] so on i386 "binary-arch" + "binary-indep" are run and on amd64 only "binary-arch" - right? [16:31] well if we see an arch-indep package we build it on i386 [16:31] but since you're taking that decision away from the build system then you need to manage it yourself [16:31] either arch will be fine [16:32] I am asking cause I need to split few build steps === salgado is now known as salgado-lunch [16:39] How can I turn off Answers in a project? I don't want users to be able to ask questions here on LP? [16:43] tgm4883: I think it's in the very left column on your project's page in the "Configure progress" section [16:43] click on configure support tracker [16:43] https://launchpad.net/PROJECT/+configure-answers [16:44] and choose unknown [16:44] right, or listen to deryck ;) [16:44] no, thekorn knows all as well :-) [16:45] see, I would love to have that work then [16:45] but i've had it configured that way for weeks now [16:45] and someone asked a question 17 hours ago [16:45] I have no idea how they did that [16:45] tgm4883, what project? [16:45] mythbuntu [16:45] https://edge.launchpad.net/mythbuntu [16:46] https://answers.edge.launchpad.net/mythbuntu/+question/123711 [16:46] weird [16:46] thats the question, IDK how they asked it, I can't find anywhere to ask it on our project [16:46] yeah, it looks like it's turned off. [16:47] odd [16:47] tgm4883, maybe someone asked it against something else and someone re-targeted it to mythbuntu? Just a guess. [16:47] could be, i'm going to ping aaron about it [16:47] if thats the case, would seem like a bug [16:48] tgm4883, I would open a bug against launchpad-answers. I think there is a bug somewhere. Unless it was asked before you turned off the app. [16:48] definitly not. We've actually had answers turned off for about a year, then when the new (configure..) thing came out we turned it off there as well [16:49] so it's definitly been off for a month or so [16:49] yeah, I would file a bug then [16:49] will do === hrw is now known as hrw|gone === dendro-afk is now known as dendrobates === yofel_ is now known as yofel === Ursinha-lunch is now known as Ursinha === matsubara-lunch is now known as matsubara === beuno is now known as beuno-lunch === salgado-lunch is now known as salgado [18:02] ok, stupid user question: i have a tarball. i want to put that tarball up for others as a released version tarfile. how would i do that: https://launchpad.net/cloud-init === deryck is now known as deryck[lunch] [18:40] smoser: add it as a release [18:41] smoser: click on 'trunk' series, then in there click "Create release" [18:42] smoser: already looks like there is a tarball up w/ a mielstone and everything. [18:42] yeah. i ended up figuring that out, although i'm not sure its right. [18:42] i didn't really want a milestone. [18:42] i wanted a release [18:42] pita [18:43] (that wasn't nice, sorry) [18:43] i'm probably just not a good user, but i was just confused, and wanting an easy way to just add a download. [18:44] they're the same thing [18:44] releases are the culmination of a particular milestone [18:45] I was a little confused by the milestone thing at first too. [18:45] but yes, you're a bad user, horrendous really === gary_poster changed the topic of #launchpad to: Code hosting offline 8.00-9.30 UTC on Friday 3rd September for unexpected hardware maintenance. http://is.gd/eRMxF | http://launchpad.net/ | Read https://help.launchpad.net/ for help | Help contact: Ursinha | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/ === dendrobates is now known as dendro-afk === beuno-lunch is now known as beuno === dendro-afk is now known as dendrobates === deryck[lunch] is now known as deryck === Jordan_U_ is now known as Jordan_U === Ursinha changed the topic of #launchpad to: Code hosting offline 8.00-9.30 UTC on Friday 3rd September for unexpected hardware maintenance. http://is.gd/eRMxF | http://launchpad.net/ | Read https://help.launchpad.net/ for help | Help contact: - | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/ === abentley_ is now known as abentley === dendrobates is now known as dendro-afk [21:51] evening guys [21:51] what's up with LP anwers? [21:51] I've got two emails from LP project sent to one of my projects contact === nhaines_ is now known as nhaines === matsubara is now known as matsubara-afk [22:51] BUGabundo: is it possible that one of them was for a team? [22:51] BUGabundo: if you look at the source of the email there should be some headers that explain a bit about who and why it was sent [22:51] some how one of my teams was set as a contact for LP anweser [22:51] BUGabundo: starting with X-Launchpad [22:52] no idea how it ended up there [22:52] all of the sudden today I started getting mail [22:53] thumper: http://paste.ubuntu.com/487489/ [22:56] BUGabundo: X-Launchpad-Message-Rationale is the interesting oen [22:56] one [22:57] thumper: I've "fixed" it [22:57] :) [22:57] but I just want to know HOW to got there in the 1st place [22:57] if it was a fluke, maybe some one else is also affected [22:58] if it was someone on my time, I need to talk to them [22:58] It was someone on your team :( [22:58] if it was someone unauthorized, then LP needs to be fixed [22:58] wgrant: based on your logs? [22:58] No. [22:59] But I know that code, and it's very careful about who it allows to make subscriptions. [22:59] your experience? === salgado is now known as salgado-afk [22:59] there are 3 ppl in that team [22:59] ill talk to them === bpeel is now known as bpeel_away