[12:56] <ubotu> New bug: #145853 in soyuz "Visibly reject FTP uploads done with unrecognized keys" [Low,Triaged]  https://launchpad.net/bugs/145853
[12:57] <cprov> kiko, elmo: do you really think that the users will be able to track their own failures ? i doubt it.
[12:58] <cprov> we can add the source IP  and the changesfile name (maybe content) if it helps.
[12:59] <kiko> cprov, key-id, source IP and changesfile name would be okay
[01:01] <cprov> kiko: or we can forward the log output to a mailing list (!) instead of keep it in the local mbox only
[01:01] <kiko> cprov, hmmm, filtered, that would not be a bad idea. 
[01:02] <kiko> cprov, do you know how the partner archive work is going?
[01:02] <cprov> kiko: yes, this morning opera got uploaded and built
[01:03] <cprov> https://edge.launchpad.net/ubuntu/gutsy/+source/opera
[01:03] <kiko> cprov, wow! that's very awesome.
[01:03] <kiko> cprov, I hear that we will need to make changes to the buildds?
[01:03] <cprov> kiko: julian has a branch for you with last-minute fixes ...
[01:03] <cprov> kiko: to the chroots, to be precise
[01:04] <kiko> cprov, I haven't seen it -- does it need cherry-picking?
[01:04] <cprov> kiko: but we haven't decided what exactly we will do.
[01:04] <cprov> kiko: yes, let me check the wip queue
[01:05] <ubotu> New bug: #145861 in malone ""Latest Bugs touched" should not list just created bugs" [Undecided,New]  https://launchpad.net/bugs/145861
[01:05] <cprov> kiko: it's not there, but it contains fixes in the ogre-model code and the NoMoreAF indexes perms, IIRC
[01:05] <kiko> yeah, I had assumed that
[01:06] <cprov> kiko: apart from the chroot problem, we have to run gina from a.c.c to production
[01:06] <cprov> kiko: shall I call you ?
[01:07] <kiko> cprov, gina? not before gutsy, right?
[01:07] <kiko> cprov, well, my phone is dead and I have no charger!
[01:07] <cprov> kiko: where are you ?
[01:07] <kiko> in bsb
[01:08] <cprov> kiko: uhm ... well, not I believe fabio's plan is to get gutsy stuff from a.c.c into production via gina
[01:08] <Daviey> Hey, are any LP dev's about who have access to the DB?
[01:09] <cprov> kiko: but I might be mistaken :(
[01:09] <kiko> cprov, AFAIK fabbione is going to upload straight to launchpad -- any reason why he wouldn't?
[01:09] <kiko> cprov, anyway, you can do a dogfood gina run, I guess?
[01:09] <cprov> kiko: no, a.c.c has no gutsy yet
[01:09] <kiko> cprov, ah, then it's cool.
[01:10] <kiko> Daviey, Tom's on leave, so I'm waiting for him to be back in office
[01:10] <cprov> kiko: yes, gina on dogfood worked correctly, AFAIK
[01:10] <Daviey> kiko: well won't matter after Sunday.. just a nuisance :(
[01:11] <kiko> cprov, oh, beautiful to hear
[01:12] <Daviey> Canonical employee's should not be allowed leave.. *fact*
[01:12] <cprov> kiko: so, the only problem we have is the chroot 
[01:12] <kiko> Daviey, I tried to tell him that
[01:12] <Daviey> :)
[01:13] <cprov> kiko: the feisty-release chroot is not able to install the new version of pkgbinarymangler (that supports partner componenent correctly) uploaded to feisty-updates 
[01:14] <kiko> cprov, hmm, that's terrible
[01:14] <kiko> but why?
[01:14] <cprov> kiko: that's the inconsistency cause by the assumption that 'release' pockets will be opened in partner.
[01:14] <cprov> archive 
[01:15] <cprov> kiko: we keep partner consistent with the rest of soyuz and upload/import packages into post-release pocket of old distroseries.
[01:15] <cprov> kiko: but I don
[01:15] <cprov> 't think I have any chance in this battle :(
[01:15] <kiko> I think we already lost that one
[01:16] <cprov> ok, let's deal with the side-effect
[01:17] <cprov> release chroots have to be modified to allow installation of packages coming from post-release pockets (the extra deb lines are passed by the buildmaster when the job is dispatched)
[01:19] <kiko> cprov, for /all/ archives, not just for partner? 
[01:19] <kiko> that's evil
[01:19] <cprov> kiko: a horrible hack that work is to simply override -release chroots with the respective -updates ... nobody will notice since after release the -release chroot is not used anymore
[01:19] <ajmitch> cprov: did you mean for realplay to end up on feisty-changes? :)
[01:19] <kiko> ajmitch, can I see that email?
[01:19] <ajmitch> sure, where shall I bounce it to?
[01:20] <cprov> ajmitch: no, it was a test from dogfood ... 
[01:20] <cprov> ajmitch: it was a *mistake* on our side.
[01:20] <ajmitch> cprov: that's what I hoped, rather than a bug
[01:21] <cprov> kiko: chroot as shared between archives, they are categorized only by (arch, series, pocket) atm.
[01:22] <cprov> ajmitch: I'm really sorry for that, it might have caused a huge confusion for the readers.
[01:23] <cprov> kiko: errm, sorry,  s\as\are in my previous comment.
[01:23] <ajmitch> I don't think too many people will worry a lot
[01:23] <kiko> cprov, well, the pocket is different, right?
[01:24] <cprov> kiko: no, component
[01:24] <kiko> doh.
[01:24] <kiko> right.
[01:24] <kiko> do we need per-archive chroots, now?
[01:24] <cprov> kiko: it sounds like the best solution
[01:25] <cprov> it should fallback to the primary archive chroot on lookup failures ...
[01:25] <cprov> would it be too nasty ?
[01:25] <kiko> that sounds kinda evil
[01:25] <ubotu> New bug: #145867 in malone "Oops for apt source package page" [Undecided,New]  https://launchpad.net/bugs/145867
[01:25] <ubotu> New bug: #145868 in malone "bug indexing/searching unable to deal with 'cron.daily'" [Undecided,New]  https://launchpad.net/bugs/145868
[01:26] <cprov> yeah, I noticed :(
[01:26] <kiko> both dupes, gar.
[01:36] <kiko> cprov, mpt: where are our approved bug tags listed?
[01:40] <cprov> kiko: https://help.launchpad.net/TaggingLaunchpadBugs
[01:41] <cprov> help  ?!? it took ages to find :(
[01:41] <kiko> thanks
[01:43] <cprov> kiko: before I forget, 10s socket timeouts on buildmaster gives us 1 failure per day
[01:44] <cprov> kiko: each time a different builder ... there is no other explanation than network hiccups.
[01:44] <kiko> cprov, okay, that's cool, though -- can we try 20s now?
[01:44] <cprov> kiko: I will keep watching.
[01:44] <kiko> I think we're close to seeing zero failures per day
[01:44] <cprov> kiko: really ?
[01:44] <cprov> kiko: okay, aiming for zero failures
[01:45] <cprov> kiko: done, 20s
[01:47] <cprov> kiko: I have to go, I will connect on IRC tomorrow morning as soon as get in the hotel. Call if you need.
[01:47] <cprov> g'night all.
[02:02] <jkakar> How do I create a team for my project in Launchpad?  There doesn't seem to be an obvious 'Create Team' action anywhere.
[02:03] <stdin> jkakar: https://launchpad.net/people/+newteam   got that link from https://launchpad.net/people
[02:04] <kiko> yeah.
[02:04] <kiko> jkakar, where could we put that link, though?
[02:05] <jkakar> kiko: I expected to find it on the launchpad.net/<project> page actions, visible only if I'm the owner of the Team I guess.
[02:05] <jkakar> stdin: Thanks!
[02:06] <kiko> jkakar, but teams are orthogonal to projects!
[02:08] <jkakar> kiko: Well.  Yeah, I can see how that's true, but it also seems that often teams represent the people working on a project.
[02:09] <jkakar> kiko: At least, the few teams I'm a part of work like that.  In fact, 'Create project team' would be nice on the project page.  It would create a team and set it as the maintainer for the project in one go.
[02:10] <jkakar> I guess you can already do that from the 'Change maintainer' page, though.
[03:01] <ubotu> New bug: #145894 in launchpad-bazaar ""Fault 8002" when pushing a branch to an unregistered project" [Undecided,New]  https://launchpad.net/bugs/145894
[03:07] <kiko> jkakar, tricky, isn't it?
[05:02] <mpt> Gooooooooooooooooooooood afternoon Launchpadders!
[05:02] <lifeless> where!
[05:14] <mpt> "Anyone Has a Fisherman" would be a great name for a band
[05:25] <fabbione> kiko: ping?
[06:49] <poolie> hi
[06:49] <poolie> i'm again getting a page loading for many minutes, without an oops timeout
[06:49] <poolie> this time it is https://bugs.edge.launchpad.net/bzr/+bug/128456/nominations/1474/+editstatus
[06:49] <ubotu> Launchpad bug 128456 in bzr "bzr+https is not a supported protocol" [Low,Triaged]  
[09:35] <ubotu> New bug: #146193 in launchpad "wish: wikitext for homepage" [Undecided,New]  https://launchpad.net/bugs/146193
[12:20] <ubotu> New bug: #146237 in launchpad "Not accepting additional spaces in string" [Undecided,New]  https://launchpad.net/bugs/146237
[12:27] <iwj> BjornT: Thanks for your investigations about those lost mails.
[12:35] <stub> kiko: It is not totally doom and gloom - if we had a catastrophic failure of the db on jubany right now we could recover - it would involve surgery on the database dumps and some consulting fees but the information is still there. But I still think the backups are a top priority.
[12:41] <boggle> how can I see the diff between a revision in a branch and it's parent branch in LP?
[12:42] <mwh> boggle: give me an example?
[12:43] <boggle> mwh: for merge proposal, see https://code.edge.launchpad.net/~canonical-training/ubuntu-desktop-course/ubuntu-desktop-course-beta
[12:44] <mwh> ah well
[12:44] <mwh> i think the answer here is "wait a couple of releases"
[12:46] <kiko> mwh, no, it's more like "pull the parent branch, merge your code into it and diff." :-/
[12:46] <boggle> he he
[12:46] <mwh> kiko: that hardly satisfies the "in LP" part
[12:46] <mwh> but yes, for now that's what you need to do
[12:46] <kiko> its parent branch is in LP! :)
[12:47] <mwh> well
[12:47] <mwh> when the code review thing is all done and dusted, this will be very slick and all lp based
[12:48] <mwh> (though somehow i doubt we'll be able to duplicate meld in a web browser...)
[01:17] <slytherin> Is it possible to request removal of a package form ppa?
[01:22] <kiko> slytherin, not at the moment, but it will be for the next release. you can upload a new version and the old one gets automatically superseded and removed, though.
[01:23] <slytherin> kiko: that is my problem, I choose wrong version for the old package I created. And now after I have created package by merging with debian package, old one supersedes new one. :-(
[01:24] <slytherin> kiko: Anyway, I have hosted the package somewhere else for the moment.
[01:24] <kiko> slytherin, maybe you could use an epoch. warning: I don't know what I am talkiing about.
[01:24] <kiko> could he use an epoch?
[01:25] <Hobbsee> kiko: yes, he could use an epoch
[01:25] <kiko> thanks Hobbsee 
[01:25] <Hobbsee> kiko: it's still somewhat evil, though
[01:25] <Hobbsee> kiko: as in, makes it harder to merge each time, as debian's will always appear lower
[01:26] <kiko> right, it will require some manual effort.
[01:26] <Hobbsee> slytherin: what you could do is your-version+really-debian-version-etc
[01:26] <Hobbsee> slytherin: which only makes you do it until upstream releases a new version, so that debian then supercedes your botched version.
[01:27] <slytherin> Hobbsee: Ok. Thanks for the info. Anyway, I just wanted the latets package to be available somewhere for discussion among developers and google page creator came to rescue. :-D
[01:32] <Hobbsee> slytherin: ah, cool
[03:10] <ubotu> New bug: #146289 in kde-i18n "Translations for non main packages are discarded" [Undecided,New]  https://launchpad.net/bugs/146289
[04:00] <ubotu> New bug: #146302 in launchpad "Clean up ProductSeries naming properties" [Undecided,New]  https://launchpad.net/bugs/146302
[04:46] <ubotu> New bug: #146334 in launchpad "Firefox decompresses tarballs from launchpad (dup-of: 102652)" [Undecided,New]  https://launchpad.net/bugs/146334
[05:27] <AlexLatchford> Howdy guys, I am currently leaving for a few months. I wish to not be notified through email about bugs and code I am involved in, is there a way to do this without changing my default email address or not?
[05:29] <intellectronica> AlexLatchford: i think your best bet is to filter the email
[06:43] <bdmurray> Is there a +text for blueprints?
[06:50] <kiko> bdmurray, nope, but you can ask for one
[06:51] <bdmurray> kiko: okay, I recall using the "api" tag but what product should that bug be filed about?
[06:52] <kiko> bdmurray, blueprint :)
[06:53] <bdmurray> kiko: I was hoping for a cool code name like malone or . . .
[07:01] <gnomefreak> does LP handle the shipit site?
[07:06] <ubotu> New bug: #146384 in soyuz "germinate for hppa" [Undecided,New]  https://launchpad.net/bugs/146384
[07:11] <kiko> gnomefreak, yes, it does.
[07:12] <gnomefreak> kiko: ShipIt is currently closed while we prepare for the Ubuntu 7.04 (Feisty Fawn) release. We'll be back in a few days.  should read 7.10 gutsy gibbon maybe?
[07:12] <kiko> gnomefreak, yeah, it's a bug, but I think salgado has it nailed :)
[07:13] <gnomefreak> kiko: ok ty :)
[07:14] <salgado> gnomefreak, kiko, yeah, it's fixed already. we only need a cherry pick
[07:15] <gnomefreak> salgado: ty just figured it was a typo not so much a bug
[07:15] <kiko> salgado, I approved, right?
[07:16] <salgado> kiko, you did, but we'll have to wait for tom
[07:16] <ubotu> New bug: #146382 in postgresql-8.2 "A tsvector can make database dumps unrestorable" [Undecided,New]  https://launchpad.net/bugs/146382
[07:16] <ubotu> New bug: #146389 in blueprint "api for blueprint tracker" [Undecided,New]  https://launchpad.net/bugs/146389
[07:17] <kiko> bright
[10:00] <ubotu> New bug: #146441 in malone "Cancel a build queue in ppa" [Undecided,New]  https://launchpad.net/bugs/146441
[10:05] <ubotu> New bug: #146444 in malone "remove file from PPA" [Undecided,New]  https://launchpad.net/bugs/146444
[11:24] <stdin> is there something up with the PPA build system?: http://launchpadlibrarian.net/9553072/buildlog_ubuntu-gutsy-i386.kde-style-qtcurve_0.54.0-0%7Eppa1_CHROOTWAIT.txt.gz
[12:07] <Daviey> Any LP admins around?
[12:07] <Daviey> *urgent*
[12:07] <Daviey> -- well semi
[12:11] <MadMan2k> Hi, Ive got some questions regading PPA
[12:11] <MadMan2k> are there some kind of stats available, so I can see which of my packages are popular?
[12:12] <MadMan2k> and is there a way to create my own sections?
[12:12] <MadMan2k> I want to backport xserver1.4 and seperate it from the less dangerous stuff
[12:13] <Daviey> jamesh_: are you about?
[12:14] <Daviey> or BjornT 
[12:14] <bastian> hello
[12:15] <jkakar_> Is there a way to specify the e-mail address that receives PPA-related notifications?  It's currently set to our team address which has our mailing list address as it's e-mail address.
[12:15] <bastian> I have found a problem with eog but I'm not sure wether to call it a bug
[12:15] <Daviey> bastian: raise it anyway and let others decide :)
[12:16] <bastian> If I open an image with eog, which is in a folder together with a very big image, eog will fill up my ram, that ubuntu will freeze if I don't react quickly enough
[12:16] <Daviey> how can that not be a bug?
[12:17] <bastian> hmm, might be a feature that other images are loaded
[12:17] <Daviey> "ubuntu will freeze" ... sounds like a bug
[12:17] <soren> Anything that might cause your machine to freeze is a bug.
[12:18] <soren> Badly implemented or not well thought out features can very easily constitute a bug.
[12:18] <bastian> It "freezes", because my ram gets filled up
[12:18] <soren> Just because it's easy to figure out why  it
[12:18] <soren> 's breaking doesn't make it any less of a bug :)
[12:19] <bastian> Is there a tutorial, how to report bugs correctly in launchpad?
[12:19] <soren> No. Launchpad helps you a bit, though.
[12:19] <Daviey> https://help.ubuntu.com/community/ReportingBugs
[12:19] <bastian> thx
[12:20] <soren> https://bugs.edge.launchpad.net/ubuntu/+source/eog/+filebug
[12:20] <soren> Daviey: wow, I had no idea there was such a document. Go figure :)
[12:20] <Daviey> soren: ftw -> http://www.google.co.uk/search?hl=en&safe=off&q=launchpad+report+a+bug+wiki&btnG=Search&meta=
[12:28] <Daviey> thumper: ping
[12:43] <Daviey> jamesh_: ping