[00:29] <wgrant> Something is broken.
[00:30] <wgrant> I appear deactivated.
[00:30] <wgrant> Maybe the email addresses have gone AWOL again.
[00:33] <elmo> wgrant: err?
[00:34] <wgrant> elmo: All LP people appear to be deactivated at the moment.
[00:34] <elmo> you mean we're in read-only mode?
[00:35] <wgrant> Yes, but it doesn't normally go like this.
[00:36] <elmo> oh, I see what you mean
[00:36] <elmo> wow that's special
[00:36] <elmo> and not in a good way
[00:37] <wgrant> It's not terribly surprising.
[00:38] <elmo> it's not?
[00:38] <flacoste> wgrant: how do you see you are deactivated?
[00:39] <elmo> flacoste: you're in grey
[00:39] <elmo> and go to launchpad.net/~flacoste
[00:39] <wgrant> I'm grey, and my user page is blank.
[00:39] <elmo> for exampel
[00:39] <wgrant> As is everyone else.
[00:39] <flacoste> i see
[00:41]  * thumper needs food badly
[00:41] <flacoste> this would point at the ValidPersonCache being screwed :-/
[00:42] <mwhudson> i guess noone cares all that much right now, but 'make schema' seems screwed on devel :(
[00:42] <wgrant> mwhudson: What breaks? It worked for me yesterday.
[00:42] <wgrant> Hm, although that might have been db-devel. I forget which ec2 demo -t uses.
[00:43] <mwhudson> wgrant: comments.sql seems to contain comments for columns that have now been deleted
[00:43] <mwhudson> like build.estimated_build_duration
[00:43] <mwhudson> (it's possibly some local fuckup)
[00:43]  * ajmitch tries on a clean devel branch
[00:43] <wgrant> mwhudson: I don't find it likely that columns have been deleted from devel lately.
[00:44] <mwhudson> wgrant: you have a point there
[00:44] <flacoste> mwhudson: that sounds like a build refactoring patch you and others have been working on
[00:44] <ajmitch> of course, getting "not a branch" from bzr when I try rocketfuel-get isn't helping
[00:45] <mwhudson> flacoste: yes, but i don't get it
[00:45] <mwhudson> i'll worry about it after the current chaos is over i guess
[00:45] <flacoste> ajmitch: codehosting is down
[00:45] <flacoste> for the upgrade
[00:45] <wgrant> Is the upgrade working a little better this time?
[00:45] <ajmitch> flacoste: ok, I figured it was update-related, I was hoping it was 'normal' :)
[00:46] <mwhudson> wgrant: a little
[00:46]  * elmo snorts indescriminately in the background
[01:23] <wgrant> The link in the read only notice points to blog.launchpad.net/maintenance, which only points to dev.launchpad.net/Maintenance, which points to identi.ca.
[01:23] <wgrant> I wonder if that could be done better.
[01:29] <mwhudson> ah well at least when launchpad is down i don't get so much mail
[02:26] <thumper> mwhudson: haha
[09:16] <wgrant> gmb: While the staging import wasn't a terribly good test (we've reorganised milestones and such since staging last restored), please perform the import on production when you can.
[09:29] <gmb> wgrant: Will do, thanks.
[09:40] <mrevell> hey
[10:28] <bigjools> gmb: did you land this for jelmer? https://code.edge.launchpad.net/~jelmer/launchpad/bug390845/+merge/14924
[10:35] <gmb> bigjools: No; I lost track of that one and jelmer mentioned landing it himself the other day.
[10:35] <bigjools> ok
[10:53] <henninge> bigjools: are you already onto the branch to fix the translations uploads?
[10:53] <bigjools> henninge: I've not started it yet, but you can take over if you want? :)
[10:53] <bigjools> it's a one-liner
[10:54] <henninge> bigjools: you were just going to add the permission for the translationgroup table, right?
[10:54] <bigjools> yep
[10:54] <bigjools> for the queued user
[10:54] <henninge> I'll take it. It's my code that's failing ... ;)
[10:56] <henninge> bigjools: btw, are the LCA-conf attendees all booked now?
[10:56] <bigjools> henninge: not at all
[10:57] <henninge> bigjools: jeroen just replied from his vacation, thinking it's too late.
[10:57] <bigjools> ah ok
[10:57] <bigjools> henninge: for going to the daily build sprint the week before as well?
[10:58] <bigjools> ah I see his email, nm
[10:58] <henninge> bigjools: AFAIK he was planning to go there
[10:58] <henninge> bigjools: he just sent it, so he may be at a computer now ... ;)
[10:59] <deryck> Morning, all.
[10:59] <bigjools> howdy deryck
[13:22] <bigjools> wgrant: fyi dogfood has the backported dpkg, when the DF buildd gets fixed up as well (Tuesday) we'll be able to do some testing
[14:03] <bac> morning sinzui
[14:03] <sinzui> Yes it is
[14:04] <bac> sinzui: i thought about the snapshot problem some more and think we made things way too complicated
[14:04] <bac> what do you think about this instead?
[14:04] <bac> http://pastebin.ubuntu.com/334532/
[14:06] <sinzui> I would worry about this approach
[14:06] <bac> sinzui: i realize we'd have to filter out form data that doesn't correspond to attributes on the object
[14:07] <bac> what is your concern?
[14:07] <sinzui> There are many views that update extra attributes to reconcile state. eg change A, B must be reset
[14:07] <sinzui> bac: consider that when you change the status of a bug, Lots of other things change too.
[14:11] <sinzui> This wont work with automated changes either. The janitor updates answer statues and send out an email that causes a change notification to go to all answer contacts
[14:11] <bac> sinzui: yeah, ok.
[14:13] <bac> sinzui: it just feels like we're doing too much work in the snapshot and tagging things to exclude is cumbersome.
[14:13] <bac> sinzui: but i see the other approach is incorrect
[14:13] <sinzui> bac: we really do not wan to exclude anything
[14:14] <sinzui> we are only excluding items that we learn as an after-thought, that we do not think users want to know about in emails.
[14:15] <flacoste> morning launchpadders
[14:19] <bac> morning flacoste
[14:51] <BjornT_> gary_poster, salgado: do we have any documentation on how to update launchpad-developer-dependencies?
[14:52] <gary_poster> BjornT_: no we do not.  I have wanted that too, and I think I have been bitten by it enough to be able to write a start on the document.  We could then have salgado review (and maybe maxb too).  Do you need this now, or if I write this today would that be OK?
[14:52] <salgado> BjornT_, I don't think so, but maybe maxb has written something
[14:52] <maxb> yes
[14:52] <maxb> dev.lp.net/LaunchpadPpa
[14:52] <maxb> BjornT_: ^
[14:52] <gary_poster> wow, thanks maxb!
[14:54] <BjornT_> maxb: thanks!
[14:57] <BjornT_> maxb: so, any documentation on how to add a new dependency, for someone who knows next to nothing about packaging? :)
[14:58] <maxb> Edit the debian/control file in a hopefully fairly obvious way
[14:59] <maxb> And definitely definitely take time to learn the "dch" tool for updating debian/changelog files
[14:59] <BjornT_> maxb: right. i figured out i had to change control, but i didn't know how to update the changelog
[15:01] <BjornT_> gary_poster, losas: btw, do you know which packages were installed in in the jscheck buildbot builder to make windmill tests runnable?
[15:01] <gary_poster> BjornT_: I do not.
[15:06] <EdwinGrubbs> thumper: ping
[15:11] <EdwinGrubbs>  /nick Edwin-afk
[15:36] <henninge> bigjools: I am not getting anywhere with the test, though.
[15:36] <henninge> bigjools: as in, I cannot reproduce it.
[15:36] <henninge> it = the error
[15:37] <bigjools> hum
[15:37] <bigjools> henninge: you're calling spr.attachTranslationsFiles ?
[15:37] <henninge> bigjools: now, one further down
[15:38] <henninge> TranslationImportqueue.addOrUpdateEntriesFromTarball
[15:38] <bigjools> did you remove your "fix" from before and did a make schema?
[15:38] <henninge> bigjools: yes
[15:39] <bigjools> henninge: as user queued?
[15:39] <henninge> yes
[15:39] <bigjools> henninge: is it reaching the code that accesses translationgroup?
[15:40] <bigjools> as per the stack trace
[15:40] <henninge> bigjools: hm, need to check that ...
[15:42] <henninge> bigjools: ah, prerequisite is an existing entry that is being updated
[15:42]  * henninge updates test
[15:42] <bigjools> ah
[15:42] <bigjools> excellent, we found a buggy test :)
[15:49] <sinzui> beuno: ping
[15:51] <beuno> sinzui, pong
[15:51] <sinzui> beuno: take a look at http://people.canonical.com/~curtis/linked-packages.png
[15:53] <sinzui> beuno: I am struggling with a bug where users can create a packaging link between their project and a source package. The problem we have is that the package may only be a PPA, so it is not offically in ubuntu. We do not want to link to the ubuntu series in this case
[15:53] <sinzui> beuno: I removed the link, and added a poor explanation that there is not official version
[15:54] <beuno> sinzui, drop the series requirement and become a hero
[15:54] <sinzui> beuno: that does not help
[15:54] <bigjools> sinzui: sounds like the package vocab might be wrong when picking one?
[15:54] <sinzui> beuno: We will let users link to the project, and we will select the default series.
[15:54] <sinzui> no
[15:55] <bigjools> it's done the other way around?
[15:55] <sinzui> bigjools: This is about the project, and it may link to fedora.
[15:56] <sinzui> bigjools: This picture is an extension of a branch I have that filters out the unversioned sps from lucid/+packaging
[15:56] <bigjools> so you need to check that the package is published in that distro before allowing the link
[15:56] <sinzui> bigjools: this picture does that
[15:57] <sinzui> bigjools: the issue is communication. Why is it not linked? Th answer is that there is no version in the official archive
[15:57] <sinzui> bigjools: since you are here, let's discuss a real example: https://edge.launchpad.net/gdp/+packages
[15:59] <sinzui> bigjools: Soyuz built those packages. I offer them in a PPA. It would be nice to tell the users it is in a PPA, not official ubuntu
[16:02] <bigjools> sinzui: so you don't want to exclude packages only in PPAs?
[16:03] <sinzui> Big there two pages for two perspectives
[16:03] <sinzui> bigjools: ^
[16:04] <sinzui> bigjools: https://edge.launchpad.net/ubuntu/lucid/+packaging
[16:04] <sinzui> ^ This MUST only show what has a version. I do that in my branch by filtering out the packagings that have no version
[16:05] <bigjools> timeout ... :(
[16:05] <bigjools> ouch
[16:05] <sinzui> bigjools: yep, it it loading all those bogus PPA packagings
[16:06] <bigjools> sinzui: you need to join to a SPPH and Archive with the right purpose
[16:07] <bigjools> sinzui: see Distribution.getCurrentSourceReleases for example
[16:07] <sinzui> bigjools: https://edge.launchpad.net/gdp/+packages
[16:07] <sinzui> ^ shows where my project is package for all distributions. It just so happens that I only make ubuntu packages. Someone can make a fedora RPM and link it on launchpad.
[16:08] <bigjools> and that page can see PPA packages too?
[16:08] <sinzui> bigjools: I think the error is in distroseries. Distroseries.packagings returns all packagings is disregard to SPPH
[16:09] <bigjools> yeah that looks horribly fuct
[16:10] <bigjools> it begs the question though
[16:10] <sinzui> bigjools: I would like to know how to see PPAs, or at least point the user how to find the PPA.
[16:10] <bigjools> how did a Packaging row get made for a package inly in a PPA?
[16:10] <bigjools> only*
[16:10] <sinzui> That is very easy
[16:11] <sinzui> I keep saying it too. anyone can create a link beween an project and an SP in ANY distribution because Launchpad wants to model everything
[16:11] <bigjools> ok well you can fix that property easily
[16:11] <sinzui> bigjools: I do not think it is broken
[16:11] <bigjools> assuming you only want to return packages published in the same series in the main archive?
[16:11] <bigjools> what do you want it to do?
[16:12] <sinzui> bigjools: yes, that is what my disrtoseries + packaging changes do...and our sample data is so bad it actually behaves like the bad data in production...easy to test \o/
[16:13] <bigjools> you said " I think the error is in distroseries. Distroseries.packagings..."
[16:13] <bigjools> heh
[16:13] <sinzui> bigjools: yes, that is where I am fixing the issue
[16:13] <sinzui> but thera are  *two* perspectives. the lucid perspective is easy to fix
[16:13] <bigjools> how did you fix it?
[16:14] <bigjools> right, you want to see distro and PPA packages separately, or at least identify the difference?
[16:14] <sinzui> do not show unpublished source packages. I know that because the packagings has not currentrelease
[16:15] <bigjools> so you join to SPPH with status in (1,2)
[16:15] <henninge> bigjools: interesting, I get more "perission denied" errors now ... translationgroup has not yet been among them.
[16:15] <bigjools> (pending, published)
[16:15] <sinzui> for the project someone might has an archive with fedora, suse, and ubuntu pacckages, so users add a link. I believe you can see that same action on my gdp/+packages page.
[16:16] <bigjools> henninge: that is worrying, it sounds like the publisher can go bang any any minute
[16:16] <sinzui> bigjools: I will update the query
[16:17] <bigjools> sinzui: if you're filtering on published packages it will never show links to non-ubuntu distros
[16:18] <sinzui> bigjools: you are singlelu thinking of lucid, that is not an issue. it is easy to solve.
[16:18] <sinzui> bigjools: the issue is the project. you have its own list,
[16:18] <sinzui> bigjools: it has it's own list
[16:19]  * bigjools is getting more confused
[16:19] <bigjools> all I am saying is that if you add the fix you just suggested, you won't see anything for Fedora etc
[16:19] <bigjools> but I am not sure I really understand your problem now!
[16:20] <sinzui> bigjools: That is not so, because the fix for the distroseries -> packagings will not affect a project. You are, you need to remember that project -> series -> packagings is a legitmate relationship, We do not know what is in fedora, so we believe the user when he tells us that
[16:22] <sinzui> In the example we are talking about, I know the package is in a PPA, and i wonder if it is possible for me it identify that and link to the ppa's info instead of the distroseries's official SP.
[16:22] <bigjools> the gdp example?
[16:22] <sinzui> It happens to be one that I know has package built in the last week
[16:23] <bigjools> see Archive.getPublishedSources()
[16:24] <bigjools> you can't re-use it as it is, but you can adapt its query to check all PPAs to see where something is published
[16:24] <sinzui> that may help
[16:24] <bigjools> actually
[16:25] <bigjools> noodles775: which query is the PPA search using at the bottom of the DSP page?
[16:28] <bigjools> sinzui: DSP.findRelatedArchives()
[16:29] <noodles775> Sorry, yes.
[16:29] <henninge> bigjools: ok, now I did reproduce the error. Had the wrong line commented out in security.cfg ... :(
[16:29] <sinzui> that look very helpful
[16:29] <bigjools> noodles775: np I was being lazy :)
[16:29] <bigjools> henninge: !
[17:18] <adiroiban> danilo__: can you please take a look at bug 491454. If its valid, I would like to look at it durring this weekend
[17:18] <mup> Bug #491454: Search English string on entire Project / DistroSeries <search> <Launchpad Translations:New> <https://launchpad.net/bugs/491454>
[17:36] <danilos> adiroiban, it's a valid use case, but it's harder than you might think: just a single series is probably much easier, but the main problem is dealing with performance
[17:38] <adiroiban> danilos: i think,a single series would solve 90% of ubuntu translation needs regarding searching for english strings
[17:38] <adiroiban> danilos: in most cases they know in what Ubuntu version they should look for a string
[17:39] <adiroiban> no need to have a search in all active series
[17:39] <danilos> adiroiban, I agree, it's still not trivial for performance reasons
[17:40] <adiroiban> danilos: ok. thanks!
[17:41] <danilos> adiroiban, in general, the only complication is figuring out right SQL; I do have a few ideas on how that would work, but basically, you'd have to test it with our data set (i.e. millions of rows in postgres)
[17:42] <adiroiban> danilos: or with my 5 years old computer
[17:42] <danilos> adiroiban, well, the other complication is how to come up with a good UI that will clearly explain that you are searching only through English and that it's impossible to search for non-English
[17:42] <danilos> adiroiban, believe me, it's not the same :)
[17:43] <adiroiban> danilos: you are saying it is very hard to reproduce the production installation on my computer?
[17:43] <adiroiban> or that it is not possible :)
[17:44] <danilos> adiroiban, yeah, it is... basically, the tests I did were on staging, which relatively closely resembles production databases, and I was able to get decent performance out of it
[17:44] <adiroiban> danilos: ok. np. I will look into other bugs
[17:45] <danilos> adiroiban, however, with postgres, it depends on a lot of other things as well, and ultimately, one can probably solve it with right partial indexes and full text search, but it's still requires a lot of testing to make sure it works
[17:47] <danilos> adiroiban, sure, thanks... I can probably be convinced to look into it myself, but as I said, it's mostly about coming up with queries and decent performance in actual circumstances :)
[17:48] <adiroiban> danilos: ok. I only took a brief picture of rosetta db ... i don't know if msgstr table is partitioned based on langauage
[17:49] <danilos> adiroiban, it's not, and even if it was, you'd soon run into a postgres issue where it doesn't really choose optimal query plans even with partial indexes :)
[17:49] <danilos> adiroiban, i.e. it does a sequential scan of the entire table first anyway if you are using (I)LIKE for matching
[17:54] <adiroiban> danilos: i was hopping you can limit somehow the scan on only one table
[17:55] <danilos> adiroiban, yeah, but it's not partitioned, and that's what partial indexes should be for, but it doesn't really work like that with postgres and large tables
[17:57] <adiroiban> danilos: and partitioning  now would break any functionality  ?
[18:00] <danilos> adiroiban, no, if done properly, it's just a lot of work
[18:01] <danilos> adiroiban, one of the things is that there are many messages which are used in different languages (i.e. potranslation table contains only unique strings)
[18:02] <adiroiban> ok. thanks.
[18:02] <adiroiban> I will leave it for the future...
[18:03] <danilos> adiroiban, if you want to take on that, I'd be happy to talk about it anytime and direct you exactly where to look
[18:04] <adiroiban> danilos: yep. I still need to read about postresq... but if partial index are not working
[18:04] <adiroiban> i think that in the long term, partitioning is a must.. and I will try to look into it
[18:05] <danilos> adiroiban, oh, they are working, but not sufficiently well with like searches; it works better with FTS, but that increases the amount of data we store
[18:06] <danilos> adiroiban, oh, indeed, that was part of the initial plans for implementing search as well, and the bug you filed was supposed to be the very next step, but we just never got to it :)
[18:07] <adiroiban> danilos: thanks for all the details. I have to go now. cheers
[18:07] <danilos> adiroiban, cheers
[18:08] <danilos> adiroiban, btw, we should exchange our photos from UDS :)
[19:05] <sinzui> bac: is pqm open?
[19:06] <bac> sinzui: not yet.  mbarnett is going to do it soon.
[19:08] <sinzui> bac: how did you manage this: https://edge.launchpad.net/launchpad-foundations/+milestone/3.1.12
[19:08]  * sinzui has a lot of branches to land
[19:10] <bac> sinzui: lazr.lifecycle does not go through PQM
[19:10] <bac> sinzui: i merely pushed the fix up to the team branch
[19:10] <sinzui> bac: https://edge.launchpad.net/lazr.lifecycle is launchpad-foundations
[19:11] <bac> sinzui: i don't understand your point
[19:11] <sinzui> bac: change the project from launchpad-foundations to lazr.lifecycle
[19:11] <bac> https://code.edge.launchpad.net/~lazr-developers/lazr.lifecycle/trunk
[19:11] <bac> ah, i see
[19:12] <sinzui> I was ever so hopeful I could land my branches
[19:13] <sinzui> bac: do we need that egg to to appear if rocketfuel before you can land the registry fix?
[19:13] <bac> sinzui: i will push download-cache (thanks for the reminder!) before landing the branch
[19:14] <sinzui> oh good, now i know the secret
[19:16] <bac> sinzui: doc/buildout.txt is helpful
[19:16] <bac> sinzui: even more so are the notes i took when gary_poster walked me through a change to lplib
[19:17] <gary_poster> improvements to the shared instructions would be greatly appreciated.  What I wrote in doc/buildout.txt has made some happy; others, not so much.
[19:17] <gary_poster> Myabe there should be different instructions for different...uh, kinds of thinkers?  Something.
[19:18] <bac> sinzui, gary_poster: http://pastebin.ubuntu.com/334689/
[19:18] <bac> sweet and simple
[19:18] <bac> chopped from my history file, i think
[19:22] <gary_poster> bac: Cool, thanks.  Maybe I should muck with it and put it somewhere, like on the dev wiki.  That's good for local changes.  It doesn't Do The Right Thing for actually releasing a dist for others...but I honestly am not sure how to do that myself (I know how to use pypi, which is easy, but we have a launchpadlib script to release across pypi and launchpad, which didn't work last time I checked).
[19:22] <gary_poster> Leonard has some instructions for that on the wiki that I haven't tried lately (and things should be fixed now).
[19:22] <gary_poster> bac: I'll put it on the dev wiki today
[19:22] <bac> gary_poster: great, thanks
[19:23] <bac> gary_poster: who actually "releases" lazr packages?
[19:23] <gary_poster> anybody who has pypi privs to do so for the given package
[19:23] <bac> gary_poster: for instance, i made those changes to lazr.lifecycle sufficient enough to support LP
[19:23] <bac> but i didn't create a release, do the pypi bits, etc
[19:24] <bac> should i request a release be packaged up or just wait for someone to notice?
[19:24] <bac> or not worry since it is not a huge change
[19:26] <gary_poster> bac: in a perfect world, you would do it.  In that perfect world, you would have a PyPI account, and the tools would exist to make releasing that a single line command.  That perfect world *almost* exists except (1) I don't know if you have a PyPI command and (2) to my knowledge Leonard is the only one who has used the wonderful on-line command that does all the PyPI and Launchpad stuff, and I don't want to make you do it if
[19:26] <gary_poster> it works. So...
[19:26] <gary_poster> bac: send me an email :-/ <shrug> :-)
[19:26] <bac> ok
[21:12] <EdwinGrubbs> sinzui: I know we talked about bug 67909 a while back, but I can't remember the details. The dates on the series definitely look wrong.
[21:12] <mup> Bug #67909: product release finder set all release dates to 23/10/2006 <prf> <Launchpad Registry:Triaged by edwin-grubbs> <https://launchpad.net/bugs/67909>
[21:15] <sinzui> EdwinGrubbs: The finder is creating a milestone and a release and setting the value to something. The question really is "How do we know the true date that something was releases?" There is nothing in a file name that says that. We know "now'" is definitely wrong
[21:16] <sinzui> EdwinGrubbs: I is may be possible to use the mod/create date fromt he remove file system. We need to change the finder rules to get a date with the listing. That is hard. doable, but always unreliable
[21:17] <sinzui> EdwinGrubbs: We ultimately expect upstream adopters to fix this. They do not. They are happy to let the finder download 500 released for a single series.
[21:18] <sinzui> EdwinGrubbs: Maybe the answer is to explore not having dates at all.
[21:19] <EdwinGrubbs> sinzui: should I unassign myself from it? It doesn't sound like you really want me to work on it.
[21:20] <sinzui> kiko:  reopened it, you were still assigned
[21:20] <sinzui> EdwinGrubbs: unassign your self. It is not important because it is not targeted to a milestone
[21:21] <sinzui> EdwinGrubbs: since we cannot commit to fixing the issue, the bug is thus low
[21:21] <EdwinGrubbs> ok, cool
[21:42] <bac> salgado: will you update the topic here when PQM opens?
[21:42] <salgado> yep
[21:43] <bac> thanks
[21:44] <kiko> sinzui, so we can't use the file mod date from the listing? why? parsing unreliability?
[21:44] <sinzui> salgado: I assume we are not doing a reroll.
[21:44] <sinzui> kiko: the listing is a HTML page that may be formatted in many ways. We can guess
[21:45] <salgado> sinzui, correct
[21:45] <sinzui> fab. time to release some projects
[21:47] <kiko> sinzui, pity
[22:34] <adiroiban> is there a config option in LP to enable listing in terminal of strom SQL queries?
[22:37] <sinzui> no, but I know you can enable postgress and or storm to log.
[22:37] <sinzui> I do not know how to do that though
[22:39] <adiroiban> thanks. there are some tips here https://storm.canonical.com/Tutorial#Debugging ... I think I can use them and enable debugging