[00:36] <ubotu> New bug: #153762 in launchpad "python-medusa missing from developer dependencies" [Undecided,New] https://launchpad.net/bugs/153762
[00:41] <ubotu> New bug: #153763 in launchpad "we should never do bug redirects to disabled products" [Undecided,New] https://launchpad.net/bugs/153763
[00:43] <rob> hello, I was wondering if it is possible to take over the username of an inactive user?
[01:02] <rob> guess it's a bit of a bad time :(
[01:05] <mpt> rob, you can make a request for it
[01:05] <mpt> https://answers.launchpad.net/launchpad
[01:57] <kiko-zzz> rob, which user.
[02:45] <rob> kiko-zzz, either rob or robert
[02:48] <kiko-zzz> rob, what's your user?
[02:49] <kiko-zzz> rob, both of them have validated email addresses, though
[02:49] <kiko-zzz> rob, you should contact them to see if they are willing to give up their names for you. if so, let me know.
[02:49] <kiko-zzz> zzz now for real
[04:15] <Rotund> Could I get some basic info about the tech behind launchpad?
[04:17] <Rotund> Anyone here with knowledge of what is behind the scenes?
[04:27] <poolie_> Rotund, what kind of thing in particular
[04:28] <Rotund> it's twisted under the hood, right?
[04:28] <Rotund> Including the web interface?
[04:28] <Rotund> What templating engine is used?
[04:29] <poolie_> well, it's zope
[04:29] <Rotund> The web interface or the whole thing/
[04:30] <spiv> https://help.launchpad.net/FAQ#head-34295746b9c12bbe42eee4a9bd5e2656306fd796 mentions some of the libraries its built on.
[04:31] <Rotund> Interesting.  So, what parts of Twisted?
[04:34] <spiv> Bits and pieces.  The SFTP/bzr+ssh server at bazaar.launchpad.net, the "librarian" web server, an internal XML-RPC server, and some other internal systems.
[04:36] <Rotund> Okay, what about the web interface?  is that Zope or Nevow or something else?
[04:38] <spiv> It's Zope 3.  (You can see that it's Zope by looking at the Server and X-Powered-By headers in the HTTP responses)
[04:40] <Rotund> ahhh.  I just looked at the HTML
[04:40]  * spiv -> lunch
[04:40] <Rotund> excellent.  just wanted a bird's eye view.  thanks
[05:04] <imbrandon> someone mind confirming and looking at bug #153798
[05:04] <ubotu> Launchpad bug 153798 in launchpad "canonical partner repo packages showing as "in ubuntu"" [Undecided,Confirmed] https://launchpad.net/bugs/153798
[05:05] <ubotu> New bug: #153798 in launchpad "canonical partner repo packages showing as "in ubuntu"" [Undecided,Confirmed] https://launchpad.net/bugs/153798
[07:58] <carlos> morning
[12:20] <bostik> hi all
[12:21] <bostik> on launchpad there is no trace of our mirror
[12:22] <bostik> it's uptodate since yesterday
[12:22] <bostik> i'm talking of ubuntu mirror
[12:23] <salgado> hi bostik
[12:23] <salgado> bostik, what is your mirror's name?
[12:24] <bostik> ubuntu.fastbull.org from italy
[12:26] <salgado> bostik, https://launchpad.net/ubuntu/+mirror/ubuntu.fastbull.org-release
[12:27] <salgado> bostik, looks like some files were missing when it was last checked (2h ago)
[12:32] <bostik> salgado, last update 13.01 CET
[13:50] <ubotu> New bug: #153884 in rosetta "Translation import queue needs better validation" [Undecided,New] https://launchpad.net/bugs/153884
[13:50] <ubotu> New bug: #153885 in soyuz "Refactor source and binary publishing presentation templates in a single macro" [Undecided,New] https://launchpad.net/bugs/153885
[14:05] <ubotu> New bug: #153891 in launchpad-bazaar "branch listings can be sorted by invisible quantities" [Undecided,New] https://launchpad.net/bugs/153891
[14:17] <ubotu> New bug: #153894 in launchpad-bazaar "two styles of sorting on one page branch listings probably confusing" [Undecided,New] https://launchpad.net/bugs/153894
[14:22] <warsocket> Hey, if i register a project as blueprint, must i program it all by myself is it possible that someone jumps in and helps
[14:23] <warsocket> cause I think i have a good idea but im not sure i can complete it all by myself
[14:25] <ubotu> New bug: #153901 in launchpad "OOPS registering attendance in a sprint with year before 1900" [Undecided,New] https://launchpad.net/bugs/153901
[14:30] <mrevell> hi warsocket
[14:31] <mrevell> warsocket: If you register a blueprint in Launchpad, any other Launchpad user can become involved. You can even assign people to work on the blueprint.
[14:52] <lamont> cprov: is there any way from the LP UI (looking at build records, especially failed records) to say "please eliminate the records for any superseded source"?
[14:54] <cprov> lamont: no, they are eliminated only when they reach dispatcher (i.e, on-the-fly, not by batches) and since gutsy was released they won't be considered by dispatched and will remain in pending state (hint: it's a problem)
[14:55] <lamont> cprov: and manually deleting them will just be undone when the queue-builder fix hits production, eh?
[14:55] <lamont> my question wasn't really hppa/gutsy related...
[14:56] <lamont> when I pull up the list of failed-to-build packages, I don't really care about earlier versions: I only want to see things where the current version is FTBFS
[14:57] <cprov> lamont: no, failed build from old versions will remain as 'history', we do not provide a proper FTBFS list yet
[14:57] <lamont> cprov: right.  they need to remain as history.  I just want the option to filter records for superseded source.
[14:57] <lamont> so I'll file a wishlist bug
[14:59] <cprov> lamont: yup.
[15:00] <lamont> new question.  if the dispatcher strips any needs-build records and doesn't dispatch them for gutsy now, then I think I have another wishlist bug that says "please mark such records as failed, reason="stable release, no way (or some such)", rather than leaving the queue polluted with records that'll never go anywhere
[15:01] <SteveA> Welcome to this week's Lauchpad development meeting!
[15:01] <SteveA> For the next 45 minutes or so, we'll be coordinating and reporting on Launchpad development. 
[15:01] <lamont> which gets back to the base question of "will all those gutsy/hppa build records go away, or hang out" (if so, please make 'em all priority -1 in sql. kthxbye.)
[15:01] <SteveA> Who is here today?
[15:01] <gmb> me
[15:01] <mrevell> me
[15:01] <danilos> me
[15:01] <carlos> me
[15:01] <lamont> oops. meeting.
[15:01] <mpt> me
[15:01] <intellectronica> me
[15:01] <bac_afk> me
[15:01] <sinzui> me
[15:01] <allenap> me
[15:01] <EdwinGrubbs> me
[15:01] <Schnitz> hi
[15:01] <jtv> me
[15:01] <barry> me
[15:01] <mwhudson> me
[15:01] <BjornT> me
[15:01] <bigjools> me, but I am ill so may not stay
[15:02] <mthaddon> me
[15:02] <salgado> me
[15:02] <matsubara> meme
[15:02] <Rinchen> me
[15:02] <matsubara> me
[15:02] <ddaa> me
[15:02] <flacoste> me
[15:02] <jamesh> me
[15:02] <schwuk> me
[15:02] <leonardr> me
[15:02] <statik> me
[15:02] <jsk> me
[15:03] <jsk> me (but may experience intermittent disconnection)
[15:03] <evarlast> me?
[15:03] <kiko> me
[15:04] <SteveA> apologies (according to the meeting page)
[15:04] <SteveA> == Apologies ==
[15:04] <SteveA>  * adeuring
[15:04] <SteveA>  * bac
[15:04] <SteveA>  * jamesh
[15:04] <SteveA>  * kiko
[15:04] <SteveA>  * ddaa
[15:04] <SteveA>  * stub
[15:04] <SteveA>  
[15:04] <SteveA> obviously some of these are incorrect
[15:04] <ddaa> that was lastweek
[15:04] <kiko> I'm not apologizing
[15:04] <kiko> that was last week
[15:04] <mpt> ergh
[15:04] <SteveA> == Agenda ==
[15:04] <SteveA>  * Roll call
[15:04] <SteveA>  * Agenda
[15:04] <SteveA>  * Next meeting
[15:04] <SteveA>  * Actions from last meeting
[15:04] <mpt> Did I forget to update it?
[15:04] <Schnitz> is it just a question of time when i can upload packages to my ppa using hardy as distro?
[15:04] <SteveA>  * Oops report (Matsubara)
[15:04] <SteveA>  * Critical Bugs (Rinchen)
[15:04] <SteveA>  * Bug tags
[15:04] <SteveA>  * Operations report (mthaddon)
[15:04] <SteveA>  * DBA report (stub)
[15:05] <SteveA>  * Sysadmin requests (Rinchen)
[15:05] <SteveA>  * A top user-affecting issue (mrevell)
[15:05] <SteveA> ----
[15:05] <SteveA>  * starred reviews - barry
[15:05] <SteveA>  * postgres shared memory - flacoste
[15:05] <SteveA>  (other items)
[15:05] <SteveA> ----
[15:05] <SteveA>  * Blockers
[15:05] <SteveA>  
[15:05] <SteveA>  * Next meeting
[15:05] <SteveA> same time next week
[15:05] <SteveA> Anyone know that they will be away?
[15:06] <gmb> I won't be here next week.
[15:06] <kiko> Schnitz, yes, a question of time. probably 1-2 weeks
[15:06] <SteveA>  * OOPS report : matsubara 
[15:06] <stub> me
[15:06] <matsubara> Today's oops report is about bugs 153884, 153901
[15:06] <ubotu> Launchpad bug 153884 in rosetta "Translation import queue needs better validation" [Undecided,New] https://launchpad.net/bugs/153884
[15:06] <ubotu> Launchpad bug 153901 in launchpad "OOPS registering attendance in a sprint with year before 1900" [Undecided,New] https://launchpad.net/bugs/153901
[15:07] <matsubara> carlos, bug 153884 is the one we discussed yesterday. I couldn't trigger it in
[15:07] <matsubara> the exact same way you did in production, but it's a start. Can you take that one?
[15:07] <carlos> SteveA: jtv, danilos and I will be in a sprint, although I guess we will be able to attend the meeting as usual
[15:07] <matsubara> jsk, are you the right person to take 153901?
[15:07] <carlos> matsubara: sure
[15:08] <matsubara> carlos: thanks. I have some other test cases that trigger a bug in that page. I'll add it to the bug report.
[15:08] <intellectronica> jsk, matsubara: isn't that already covered by work the jsk started on date formatting?
[15:08] <carlos> matsubara: ok, thank you. That form needs a lot of love so that's really helpful
[15:08] <matsubara> intellectronica: I think it might be covered by bug 139413
[15:08] <ubotu> Bug 139413 on http://launchpad.net/bugs/139413 is private
[15:09] <kiko> carlos, it's very easy to cause that page to OOPS, btw.
[15:09] <matsubara> intellectronica: there's also bug 134063 but that's not in progress...
[15:09] <ubotu> Launchpad bug 134063 in launchpad "OOPS registering sprint or meeting using date format DD-M-YYYY" [High,Confirmed] https://launchpad.net/bugs/134063
[15:09] <jsk____> intellectronica: possibly - I was offline for a moment there.
[15:10] <mpt> ... I won't be here next week. (Sorry, just realized.)
[15:10] <matsubara> jsk____: do you think you'll fix 139413 soon?
[15:10] <kiko> cool.
[15:10] <kiko> SteveA, move on.
[15:11] <SteveA> kiko: why?
[15:11] <jsk____> intellectronica, matsubara: this is primarily related to bug 139360
[15:11] <ubotu> Launchpad bug 139360 in launchpad "DateTimeParser fails silently for certain inputs" [High,Confirmed] https://launchpad.net/bugs/139360
[15:11] <SteveA> matsubara: are you done?
[15:11] <matsubara> jsk____: ah so you need a upstream fixed
[15:11] <matsubara> SteveA: not yet
[15:11] <matsubara> s/fixed/fix/
[15:11] <jsk____> matsubara: yes this is related to an upstream bug.
[15:11] <kiko> SteveA, because this can be resolved privately.
[15:11] <kiko> the oops has been raised already
[15:12] <kiko> (and it's not a very common oops)
[15:12] <matsubara> jsk____: ok then. thanks
[15:12] <matsubara> SteveA: ok, back to you.
[15:12] <jsk____> matsubara: welcome.
[15:12] <SteveA> thanks matsubara 
[15:12] <SteveA> * Actions from last meeting
[15:12] <SteveA> mrevell to report a bug about "ubuntero", etc.
[15:12] <mrevell> Yes, that's done it is bug number
[15:13] <SteveA> * #
[15:13] <SteveA> * Critical Bugs (Rinchen)
[15:13] <SteveA> #
[15:13] <mrevell> Sorry
[15:13] <mrevell> mislaid number
[15:13] <mrevell> will report to list
[15:13] <Rinchen> Hi, Two bugs have been resolved and cherrypicked: Bug #147633 and Bug #148147.   One bug remains on the list and that's Bug #150988.  cprov, what's the current status on this? Please update the bug report too.  SteveA, I've replied to you moments ago via email about bug #86185
[15:13] <ubotu> Bug 147633 on http://launchpad.net/bugs/147633 is private
[15:13] <ubotu> Bug 148147 on http://launchpad.net/bugs/148147 is private
[15:13] <ubotu> Launchpad bug 150988 in soyuz "queue-builder failing due duplicated entries in the DB" [Critical,In progress] https://launchpad.net/bugs/150988 - Assigned to Celso Providelo (cprov)
[15:13] <ubotu> Launchpad bug 86185 in launchpad "Librarian should log OOPS reports" [Medium,Confirmed] https://launchpad.net/bugs/86185
[15:15] <cprov> me (sorry, was distracted with a code review)
[15:15] <cprov> Rinchen: 1.1.10 code will cope with the problem pointed in 150988
[15:16] <Rinchen> so we're targeting next week's roll-out for resolution then.
[15:17] <cprov> Rinchen: I didn't have time to work on the DB cleanup patch yet, but since we *can* live with the broken data, I think the bug should be demoted to 'high'
[15:17] <kiko> cprov, won't the broken data cause the constraint to not apply?
[15:17] <kiko> cprov, and isn't the broken data causing OOPSes too?
[15:18] <cprov> kiko: right, the broken data in gutsy-* will block the constraint
[15:18] <kiko> cprov, it needs fixing asap.
[15:18] <cprov> kiko: but I don't think they are causing any OOPSes
[15:18] <kiko> cprov, the "lastscore" oopses?
[15:19] <cprov> kiko: yes, if people hit 'retry' on the duplicated build :(
[15:19] <kiko> right.
[15:20] <kiko> so let's fix the damned builds. don't we have a script that does this already?
[15:20] <Rinchen> kiko, do you have some time later today to work this a bit further with cprov (in the interest of meeting time)?
[15:20] <cprov> kiko: partially, because we can't remove stuff published in gutsy 
[15:21] <cprov> kiko: we have to tweak the SQL generated by the script manually
[15:22] <cprov> kiko: right, let's sort this together, but we need a DBA (postgres access to jubany).
[15:22] <Rinchen> Thanks cprov 
[15:23] <Rinchen> SteveA, over to you.
[15:23] <SteveA> thanks Rinchen 
[15:23] <SteveA>  * Bug tags
[15:23] <SteveA> there is one bug tag proposed today
[15:23] <SteveA> lp-deps
[15:23] <SteveA> bugs related to the launchpad*-dependencies packages in Ubuntu
[15:24] <SteveA> however, the bug examples aren't linked
[15:24] <SteveA> so I can't easily look them up
[15:24] <flacoste> why not something about lp-deps
[15:24] <flacoste> sorry, lp-debs
[15:24] <SteveA> I'm defering this until later in the meeting
[15:24] <flacoste> or lp-packaging
[15:24] <SteveA> kiko: please make the links
[15:24] <SteveA>  * Operations report (mthaddon)
[15:24] <flacoste> since we might have other LP related packages in the future (for API stuff)
[15:24] <mthaddon> Issues with PostgreSQL and escalation which SteveA has discussed on the list
[15:24] <mthaddon> Working on codehosting staging setup and feeds staging setup
[15:24] <mthaddon> Lots of cricket work over the last week - also in the process of migrating cricket to a new server to take load off asuka
[15:24] <mthaddon> That's it from me unless there are any question
[15:25] <SteveA> thanks mthaddon 
[15:25] <SteveA>  * DBA report (stub)
[15:25] <stub> At about 13:50 UTC either something chewed up way too much shared memory
[15:25] <stub> resources on the Production DB or we ran out of locks. Restarting the
[15:25] <stub> appservers and authserver appears to have fixed the issue, which indicates
[15:25] <stub> it was either an appserver or the authserver chewing up the shared resources.
[15:25] <stub> I'll increase the suggested tuning parameter next rollout, but we have no
[15:25] <stub> way of knowing the actual cause or if we will ever see it again. Given the
[15:25] <stub> codebase has been reasonably static as has the database there is a good
[15:25] <stub> chance we will never see it again - just a one off glitch causing an
[15:25] <stub> outage.
[15:26] <stub> I don't know how long the outage was for or if it 'ramped up' to a
[15:26] <stub> full on outage or switched from working to not working quickly. As far as
[15:26] <stub> I am aware it was a single outage rather than an ongoing problem.
[15:26] <stub> If you have approved branches with db patches land em.
[15:26] <stub> I'm on leave tomorrow, back on Wednesday. I'll probably be around tomorrow
[15:26] <stub> during the day.
[15:26] <SteveA> stub: was the database restarted?
[15:27] <SteveA> stub: was the shared memory max increased?
[15:27] <stub> Not that I am aware of. And no mem changes have been made (they require a restart)
[15:27] <SteveA> stub: please send a message to the launchpad list in future when we have any kind of database issue that causes failing pages
[15:27] <stub> Or if you mean the linux max, I don't know.
[15:27] <mthaddon> DB wasn't restarted as far as I know either
[15:28] <SteveA>  * Sysadmin requests (Rinchen)
[15:28] <Rinchen> Hi! Is anyone blocked on an RT or have any that are becoming urgent? flacoste, did someone respond with the email information?
[15:28] <Rinchen> and yes, barry, I'll remind elmo today :-)
[15:28] <flacoste> Rinchen: no
[15:28] <barry> Rinchen: thanks!
[15:28] <Rinchen> Thanks flacoste.  
[15:29] <jtv> Rinchen: #29134
[15:29] <kiko> SteveA, you are pretty good at skipping /my/ topics, hmmm.
[15:29] <Rinchen> Who is the correct person to advise flacoste about how to access the incoming staging email pop?
[15:29] <SteveA> kiko: what topic is that?
[15:29] <kiko> SteveA, the proposed bug tag. it was just a matter of outputting the bug numbers here and getting them linkified!
[15:29] <SteveA> kiko: yep, so we'll come back to it later in the meeting.  defered to later in this meeting, not skipped.
[15:29] <kiko> Rinchen, matsubara would know -- didn't he email people about this a while back?
[15:30] <Rinchen> flacoste, worst case I can have IS reset the pw on it and have them provide you that info.  I would assume it was a config value.  mthaddon ?
[15:30] <mthaddon> Rinchen, incoming mail is configured on staging - what access does flacoste need?
[15:30] <matsubara> Rinchen, kiko, flacoste: I have access only to the outgoing mailbox
[15:30] <flacoste> mthaddon: the credentials so that process-mail.py can access the POP mailbox where these email ends up
[15:30] <mthaddon> flacoste, it's already working and in place
[15:30] <flacoste> incoming email that is
[15:31] <flacoste> mthaddon: do they end up at the same place that the /outgoing/ ones go?
[15:31] <Rinchen> jtv, got it, thanks.
[15:31] <mthaddon> flacoste, there's a config file in the directory above where RF sits on staging that defines how to connect to the incoming mail box
[15:31] <flacoste> mthaddon: ok, thanks!
[15:32] <flacoste> Rinchen: case close
[15:32] <Rinchen> flacoste, mthaddon - thanks
[15:32] <Rinchen> jtv,  elmo the good man he is, raised your ticket and assigned it earlier today so you can expect it soonish
[15:32] <Rinchen> SteveA, back to you
[15:32] <SteveA> kiko: please make the examples links.  that way, they're available and convenient for people to look at ahead of time, not at the last minute in this meeting.
[15:32] <SteveA> thanks Rinchen 
[15:32] <jtv> Rinchen, elmo: thanks
[15:32] <SteveA>  * A top user-affecting issue (mrevell)
[15:32] <mrevell> In the "User deletion" thread on the launchpad-users list, Cesare Falco
[15:32] <mrevell> raises bug 87326.
[15:32] <ubotu> Launchpad bug 87326 in soyuz "Support PPA Renaming and Reassignment" [Wishlist,Confirmed] https://launchpad.net/bugs/87326
[15:32] <kiko> SteveA, jesus christ, it's just 4 bugs requesting packaging stuff into lp-dependencies
[15:33] <mrevell> When changing his Launchpad username,
[15:33] <mrevell> Cesare's PPA remained under his
[15:33] <mrevell> previous Launchpad username.
[15:33] <mrevell> I'll send a mail to the launchpad-users list to kick of a discussion.
[15:33] <mrevell> Thank you and back to you SteveA.
[15:33] <mrevell> Apologies for odd formatting.
[15:33] <mpt> I thought we didn't allow people to change their Launchpad ID for precisely that reason.
[15:33] <kiko> mpt, we do allow them to change it.
[15:33] <SteveA> we do allow people to change their id
[15:34] <mpt> Maybe I'm confusing that with project IDs
[15:34] <SteveA> however, we have discussed the idea that there are certain things you do
[15:34] <SteveA> that mean you can no longer change your id after doing those things
[15:34] <kiko> bug #141046
[15:34] <ubotu> Launchpad bug 141046 in launchpad "lp-dependencies missing ssh" [Undecided,Confirmed] https://launchpad.net/bugs/141046 - Assigned to Guilherme Salgado (salgado)
[15:34] <SteveA> we need to think about how to warn people about this, and how all that would work
[15:34] <mpt> ok
[15:35] <SteveA> I think some forum software or whatever allows people one name change shortly after joining
[15:35] <Rinchen> SteveA, or perhaps would should let them but with a warning. 
[15:35] <SteveA> I've seen that kind of thing before
[15:35] <SteveA>  * starred reviews - barry
[15:35] <barry> I sent an email to launchpad@ about starred review status, please read and let
[15:35] <barry> me know if you have any questions.  In summary: if your branch is being
[15:35] <barry> reviewed by a mentored reviwer (a.k.a. recruit) your review status will have a
[15:35] <barry> star until it is approved by that reviewer's mentor.  You are not allowed to
[15:35] <barry> commit any branch that is still starred.
[15:36] <barry> Once the mentor approves the review, your reviewer will remove the star and
[15:36] <barry> then you can act on the status (e.g. commit if it's approved).  Any status can
[15:36] <barry> be starred, and when you respond to a needs-reply* branch, please keep the
[15:36] <barry> star when you move it to needs-review*.
[15:36] <cprov> Rinchen: if we allow them to change a PPA directory will remain lost 
[15:36] <barry> done
[15:37] <SteveA> thanks barry
[15:37] <SteveA>  * postgres shared memory - flacoste
[15:37] <cprov> Rinchen: I meant, a warning won't solve the issue, we should either deny changes or support them properly.
[15:37] <SteveA> actually, that's my item
[15:37] <flacoste> (If you aren't aware of it, go reat the 'Critical issue...' threads on
[15:37] <flacoste> the LP mailing list.)
[15:37] <carlos> barry: btw, pendingreviews page needs to be updated to handle needs-mentoring status, or does it disappear with the * flag?
[15:37] <flacoste> The DB is running out of shared memory causing transactions in many different
[15:37] <SteveA> I just put flacoste's name on it because he's taking it forward :-)
[15:37] <flacoste> parts of LP to fail.
[15:37] <flacoste> We have two suspects:
[15:37] <flacoste> - recent use introduction of usage of TEMP table in Translations code.
[15:37] <flacoste> - increase usage of authserver and/or Librarian.
[15:37] <flacoste> The more of think of it, the more I'm pretty sure it's the changes to use
[15:38] <flacoste> SQLObject in the authserver that is the problem.
[15:38] <flacoste> These changes were merged on 2007-07-3, so well after the last Ubuntu release.
[15:38] <flacoste> Each Ubuntu release brings a spike in usage on the wiki, so it makes sense
[15:38] <flacoste> that we are only seeing this now.
[15:38] <flacoste> Temporary solution: revert the authserver to the old version not using
[15:38] <flacoste> SQLObject. But since there were later changes to the authserver for Code
[15:38] <flacoste> stuff, that may not be practical.
[15:38] <flacoste> Permanent solution would be to fix bug #140817.
[15:38] <flacoste> sorry, well, i prepared something :-)
[15:38] <ubotu> Launchpad bug 140817 in launchpad "The librarian reconnects too often (and takes too long to do so)" [Medium,Confirmed] https://launchpad.net/bugs/140817 - Assigned to Francis J. Lacoste (flacoste)
[15:38] <barry> carlos: bjornt is looking at issues related to pending-reviews and the new star flag
[15:38] <carlos> ok
[15:39] <SteveA> flacoste: thanks
[15:39] <SteveA>  * Blockers
[15:39] <flacoste> Foundations team: not blocked
[15:39] <SteveA> SC: not blocked
[15:39] <jtv> Translations team: Not blocked.  We wish.
[15:40] <Rinchen> Releases Team: Not Blocked.
[15:40] <BjornT> Bugs team: not blocked
[15:40] <bigjools> soyuz: not blocked
[15:40] <ddaa> Code: not blocked
[15:40] <Rinchen> flacoste is my hero.
[15:40] <Rinchen> For today at least :-)
[15:41] <SteveA> ok
[15:41] <SteveA> and coming back to the bug tags...
[15:42] <SteveA> for the proposed tag 'lpdeps', the heading and bugs are not linked, making it inconvenient for readers to see what bugs are refered to
[15:42] <SteveA> even so, I think this is better done with a Product
[15:42] <SteveA> as it's not launchpad code we're talking about, but packages for use by developers and installation on servers
[15:42] <SteveA> so, I think we should use a launchpad-dependencies Project for this instead
[15:43] <SteveA> kiko: you proposed the tag.  comments?
[15:43] <salgado> +1 for the Project
[15:44] <kiko> SteveA, I'm fine with a separate project; it sounds more correct to me tbh.
[15:44] <SteveA> cool
[15:44] <kiko> the only reason I proposed a tag was to be less controversial
[15:44] <kiko> but having it be a project will allow us to use Packaging links correctly too
[15:44] <SteveA> great
[15:44] <kiko> since these are included in Ubuntu
[15:44] <kiko> my /only/ question is
[15:45] <kiko> why don't we just use the Ubuntu packages to manage these bugs? it appears that that is frowned upon
[15:45] <SteveA> which ubuntu packages?
[15:45] <kiko> as Salgado commented in one of the bugs I looked at yesterday
[15:45] <kiko> launchpad*-dependencies?
[15:45] <SteveA> those were in dapper iirc
[15:45] <SteveA> by mistake
[15:45] <statik> Collaborative Commerce: not blocked (sorry for the delay there)
[15:45] <flacoste> isn't because they are published from another APT archive?
[15:45] <salgado> kiko, they don't really exist in Ubuntu
[15:46] <SteveA> so, basically, they are not in ubuntu in any meaningful sense
[15:46] <SteveA> we could put them in a PPA
[15:46] <kiko> they aren't?
[15:46] <kiko> okay let me shut up then.
[15:46] <SteveA> right
[15:46] <SteveA> they were in once, but it was a mistake
[15:46] <mpt> That may be related to the recently-reported bug about "partner" appearing as an Ubuntu pocket
[15:46] <kiko> a separate project is fine, I'll move the bugs across.
[15:46] <SteveA> so they were removed again
[15:46] <SteveA> cool
[15:46] <kiko> thanks!
[15:46] <SteveA> so, 'lpdeps' as a bug tag is rejected in favour of using a Project
[15:47] <SteveA> I'd like us to use PPA for these, if possible, in the future
[15:47] <SteveA> dogfooding and all that
[15:47] <SteveA> ok, that's all folks
[15:47] <SteveA> thanks for being here and keeping the meeting productive
[15:47] <flacoste> we can't report bugs against packages in PPAs yet?
[15:47] <SteveA> MEETING ENDS
[15:47] <flacoste> that would be a cool feature!
[15:47] <kiko> flacoste, we can't no. and that's a scary question. :)
[15:47] <kiko> flacoste, talk to sabdfl. kthxbye :)
[15:47] <flacoste> each PPAs becoming a mini-distribution :-)
[15:47] <ScottK> flacoste: Please, $DEITY, no.
[15:48] <ScottK> kiko: I'm around if you want to discuss the pyspf upstream info you mentioned yesterday (or the day before).
[15:48] <flacoste> i'm sure Mark would like the idea...
[15:48]  * mpt tries to imagine the navigation that would involve
[15:48] <mpt> Translations for PPAs? Questions for PPAs?
[15:48] <gmb> c!
[15:48] <flacoste> so maybe I shouldn't talk about it then
[15:48]  * ScottK tries to imagine the nightmare for but triagers.
[15:48] <gmb> Ignore me.
[15:48] <kiko> ScottK! Let me get off the phone :)
[15:48] <ScottK> kiko: No rush.
[15:49] <Rinchen> flacoste, you mean micro-distribution right? ;-)
[15:50] <flacoste> Rinchen: you get to pick the name
[15:51] <Rinchen> Launchpad Outstanding User-created Distribution
[15:51]  * Rinchen toddles off to do real work.
[15:54] <sabdfl> flacoste: we are SO going to have to solve that
[15:54] <sabdfl> because sooner, rather than later, bugs will start to show up against Ubuntu for PPA packages :-)
[15:54] <flacoste> sabdlf: i knew you would like the idea!
[15:55] <sabdfl> in my ideal world, apport / bugbuddy / whatevertool would know that a package was installed from a PPA and file it in the right place
[15:55] <sabdfl> it's just that we don't currently know what "the right place" is :-)
[15:56]  * ScottK would like "right" to be somewhere where Ubuntu bug triagers never have to deal with it.
[15:56] <lamont> ScottK: until it's flagged as also affecting ubuntu
[15:57] <ScottK> lamont: If it's in a PPA, by definition it doesn't.
[15:57] <lamont> cprov: so - about my question from right at the meeting start... got a couple minutes to chat?
[15:57] <lamont> ScottK: it's possible that I'm encountering a bug in the part of the package that wasn't changed in stuffing it into the ppa
[15:58] <ScottK> lamont: Then go test against a real package and file against that.
[15:58] <lamont> just because I find a bug in an ubuntu package with a -ubuntuN suffix in the version doesn't mean that it doesn't affect debian
[15:58] <lamont> ah, I'd rather they just marked the bug as also-affects.
[15:59] <ScottK> True, but it takes some figuring by someone who (usually) knows more than the bug reporter to know.
[15:59] <cprov> lamont: can't it wait 30 min ? I need some food ;)
[15:59] <lamont> then again, I'd like to be able to say that a bug also-affects debian, and have LP deal with the mechanics of filing said bug for me if it's not already there.
[15:59] <lamont> cprov: sure
[15:59] <lamont> poke me
[15:59] <cprov> ok
[15:59] <lamont> ScottK: then again, having LP file bugs against debian or other upstream begins to enter the political space
[15:59] <ScottK> lamont: Exactly.
[16:00] <lamont> ScottK: and since ubuntu is apolitical (esp wrt our derivatives?), we shouldn't mind the 'also-affects' activity
[16:01] <ScottK> lamont: You may not.  I certainly do.  All the also affects baltix bugs in backports drive me nuts.  How can a request to backport to Ubuntu Feisty affect baltix?
[16:02] <lamont> because baltix is planning to do a feisty.7 release? :-)
[16:02] <lamont> or is derived from feisty-backports? (*phear*)
[16:04] <ScottK> I have no idea, but feisty-backports is a project about backporting to a specific Ubuntu release.  Baltix should deal with their own problems and not spam me with their bugmail.
[16:05] <ubotu> New bug: #153934 in launchpad "Ubuntero status shouldn't appear on everyone's profile page" [Undecided,New] https://launchpad.net/bugs/153934
[16:10] <lamont> ScottK: ah... that's a different issue.  LP shouldn't be sending you also-affects email, I expect
[16:10] <lamont> or you should be able to tell it not to
[16:10] <ScottK> lamont: You're either subscribed to the bug or not AFAIK
[16:11] <lamont> grumble.  I see your point
[16:11] <lamont> also-affects (in my mind anyway) wants to be a very light weight clone of the bug
[16:13] <ScottK> lamont: That'd be different, but that's not the LP we have today.
[16:14] <lamont> right.  iz bug. :-)
[16:14] <ScottK> OK.  Get them to fix that, then we'll talk.
[16:14] <lamont> OTOH, procmail is love
[16:15] <ScottK> Sure, I could filter out irrelevanceies, but I shouldn't have to be bothered.
[16:15] <lamont> you should file a bug that says 'also affects' should not generate mail, maybe
[16:16] <seb128> hey
[16:17] <seb128> does anybody if it's possible to have a bot displaying all the commits to a launchpad team archive on IRC?
[16:17] <pochu> can't ubotu do that?
[16:18] <pochu> lamont, ScottK: I think Also Affects should generate mail. If I have a bug in a package, and it also affects upstream, for example, I'd really like to know what upstream thinks about it.
[16:18] <ScottK> pochu: Then subscribe to that too.
[16:19] <pochu> lamont, ScottK: Also, how would you know a comment is reported against feisty-backports, or against baltix?
[16:19] <pochu> ScottK: hmm, that might have sense...
[16:19] <ScottK> Well currently you don't
[16:19] <ScottK> That's another part of the problem.
[16:19] <lamont> pochu: which is why 'also affects' should really be cloning the bug
[16:23] <kiko> pochu, also affects does generate email -- do you mean to the people subscribed to the bug, though?
[16:24] <ScottK> kiko: lamont and I were just wishing it didn't and he was presenting a counter argument.
[16:25] <lamont> kiko: when a downstream disto says "me too", I really don't want to hear it: that's their bug.
[16:25] <lamont> OTOH, when they have a patch for me, I'd love to know
[16:25] <kiko> lamont, I'm not sure you really don't want to hear it in all cases.
[16:25] <lamont> and if someone marks the bug as "also affects upstream", then I do want to hear about it, generally.
[16:25] <kiko> and it's easier to ignore or delete email than to make it appear when it doesn't. :)
[16:25] <lamont> kiko: heh
[16:25] <ScottK> kiko: I'm certain when baltix me too's feisty-backports bugs that I don't want to hear it in all cases.
[16:26] <lamont> kiko: and understood...
[16:26] <lamont> kiko: ostrich-releases like backports (head in the sand, don't care about the world)  _would_ be a case where I don't want to hear about it _ever_.
[16:27] <kiko> ScottK, you can ignore mail by component you know :-)
[16:27] <lamont> but backports could be special in that regard.
[16:27] <kiko> but not by pocket, hmm
[16:27] <lamont> kiko: sounds like you know what to put in _that_ bug report, eh? :-)
[16:30] <kiko> heh
[16:32] <keescook> ddaa: heya
[16:33] <ddaa> keescook: I looked a your xpath stuff
[16:33] <ddaa> the biggest problem I have is not translating it
[16:33] <ddaa> is figuring what the hell it's intended to do
[16:34] <keescook> hehe, yeah.
[16:34] <ddaa> I have a feeling it should be reasonably easy to translate to some functional programming construct that's more readable
[16:34]  * lamont wonders if there is a mailing list that all build logs get mailed to...
[16:34] <pochu> seb128: #ubuntu-installer has the CIA bot, which does that for them. You might want to talk to cjwatson or evand.
[16:34] <ddaa> or even not even functional programming at all...
[16:34] <keescook> ddaa: sure, I totally believe it's possible to do that; I'm interested in figuring out why it doesn't work with the "workaround" document obj.
[16:35] <ddaa> keescook: what I am interested in
[16:35] <ddaa> is enabling folks like to make nice greasemonkey love for launchpad
[16:35] <seb128> pochu: as they documented on their wiki that's something they set up on the commiter side, not on the server
[16:35] <ddaa> keescook: figuring why esoteric undocumented features of firefox do not work as intended in edge cases is, like, totally not on my radar :)
[16:36] <keescook> ddaa: um, esoteric?  xpath is very very common.
[16:36] <pochu> seb128: ok, but that's what you asked for, isn't it? :-)
[16:36] <ddaa> I know xpath, I just never heard of a portable way to evaluate xpath expression in js
[16:37] <ddaa> keescook: I'd be glad to be educated, though
[16:37]  * keescook has no clue
[16:37] <keescook> I just use things from examples I see.  :)
[16:37] <seb128> pochu: not really, I would like a server side solution, not something which display commit only of people who configured the hook locally
[16:37] <keescook> but I know xpath is all fancy-cool and what all the web2.0 kidz are using.  :)
[16:38]  * ddaa used xpath beyound reason when he was a xslt crack-peddler
[16:38] <ddaa> keescook: here's my hunch
[16:38] <ddaa> try stuffing the data into a hidden element on the page
[16:39] <ddaa> it might it's not working because the DOM is not up in the air, and not in a page
[16:39] <ddaa> in any case, it does not look it a problem with launchpad at all
[16:39] <ddaa> prove me wrong and give me something to fix
[16:39] <keescook> ddaa: that's true.  I do get an XML response now.
[16:40] <keescook> I'll try the hidden element hack.  :)  do you have a small snippet as an example of that?
[16:40] <ddaa> nope, I just imagined it might work :)
[16:41] <ddaa> but I cannot help the feeling that it would be more sensible to stick to simple things that get the job done
[16:42] <pochu> seb128: this might be interesting: https://blueprints.edge.launchpad.net/launchpad/+spec/irc-notifications
[16:42] <ddaa> keescook: I'm thinking of closing bug 153654 as invalid
[16:42] <ubotu> Launchpad bug 153654 in launchpad "null XHR.responseXML" [Medium,Confirmed] https://launchpad.net/bugs/153654 - Assigned to David Allouche (ddaa)
[16:42] <seb128> pochu: right, the idea is not new ;-)
[16:43] <keescook> ddaa: okay, that's fine by me.
[16:43] <ddaa> I talked a bit with mpt, and he seems to be extremely meh about serving pages as text/xml...
[16:43] <kiko> hey Seveas 
[16:43] <kiko> ScottK, so, about pyspf.
[16:43] <keescook> yeah, that's fine.  Adding the mime override for XML use is okay by me.
[16:43] <Seveas> hey kiko
[16:44] <kiko> ScottK, it's actually the case that because pyspf releases separate tarballs, it's meant to be a separate project indeed.
[16:44] <kiko> ScottK, now I've set up a code import for it on trunk and am waiting for it to sync
[16:44] <ddaa> keescook: btw, I have just come up with some userContent.css you might want to use
[16:45] <keescook> ddaa: oh?
[16:45] <ScottK> kiko: I don't see anything on LP about it?
[16:45] <kiko> Seveas, how could I convince you to rig your bot to also accept commit messages?
[16:45] <kiko> ScottK, in https://edge.launchpad.net/pyspf?
[16:45] <ScottK> Oh.
[16:46] <kiko> ScottK, because that's what represents the upstream side of the project
[16:46] <Seveas> kiko, a suitable bribe and/or a more clear explanation of what you mean
[16:46] <ScottK> kiko: I was looking at https://edge.launchpad.net/ubuntu/+source/pyspf
[16:46] <Seveas> :)
[16:46] <kiko> Seveas, so seb128 was talking to be about how it would be neat to get commit messages posted to IRC
[16:46] <kiko> Seveas, and I was thinking that if we got your bot to subscribe to a branch, it'd get notified
[16:47] <ScottK> kiko: I don't see any indication of code, but maybe that waits for the sync
[16:47] <kiko> Seveas, it'd then be a matter of parsing that email and posting it
[16:48] <Seveas> kiko, hmm, I'm going to have to redesign the mail-to-irc bits then. They currently require a separate address for each function
[16:48] <ScottK> kiko: Homepage and description are still obsolete.
[16:48] <kiko> Seveas, we could use a separate address, no problem.
[16:48] <Seveas> kiko, file it as a bug please
[16:48] <kiko> ScottK, yeah, the sync isn't going yet. but it will, and I'm working on a portlet to display the latest revisions that we could use in useful contexts
[16:48] <kiko> ScottK, do you have a good description for it?
[16:48] <kiko> I don't
[16:49] <ScottK> kiko: Where did you get the wrong one you have?
[16:49] <Seveas> kiko, it is a problem since it's not trivial to create N launchpad accounts for N branches. Ideally, adding a branch (or bug) monitor should be fairly trivial 
[16:49] <kiko> ScottK, from http://www.wayforward.net/spf/
[16:49] <kiko> ScottK, incidentally. :)
[16:50] <ScottK> So where did you get that?
[16:50] <kiko> ScottK, http://www.google.com.br/search?q=pyspf&ie=utf-8&oe=utf-8&aq=t&rls=com.ubuntu:en-US:official&client=firefox-a
[16:51] <ScottK> kiko: It would seem to me to make sense to look at the perfectly reasonable package description provided in the Debian packaging.
[16:51] <ScottK> The problem in this case is that that hasn't been the project's home for ~3 years.
[16:52] <lamont> ScottK: if the package isn't 3 years old, then that's a bug.
[16:53] <lamont> if it is, then it's just annoying
[16:53] <kiko> ScottK, arguably, the project needs its own homepage :)
[16:54] <ScottK> kiko: It's got all the home page it needs on Sourceforge or Python Cheeseshop.
[16:55] <kiko> ScottK, fair enough. maybe get the original author to redirect to it? :)
[16:56] <ubotu> New bug: #153948 in rosetta "translation does not update" [Undecided,New] https://launchpad.net/bugs/153948
[16:56] <ScottK> kiko: Sure, but I'm sensing this is a wrong way to go about this.
[16:57] <kiko> ScottK, updated the upstream page, now
[16:57] <ddaa> keescook: http://paste.ubuntu-nl.org/41077/
[16:57] <ScottK> kiko: I'm one of the upstream developers.  I just took over as Debian maintainer for the package (although I havne't uploaded yet), and here I am (only because I also happen to use Ubuntu) having to tell you that it's wrong.
[16:57] <ScottK> This just doesn't seem like a process that is going to scale well at all.
[16:59] <kiko> ScottK, now that this is done more useful things can happen.
[17:00] <ScottK> kiko: How is this going to work for the thousands of packages in Universe?
[17:00] <kiko> ScottK, one step at a time? we already have about a thousand covered
[17:00] <keescook> ddaa: neat; how do I apply that?
[17:00] <ddaa> stick that into chrome/userContent.css
[17:01] <ubotu> New bug: #153955 in soyuz "Creating a new distribution series with a space in its name causes an IntegrityError but no OOPS" [Undecided,New] https://launchpad.net/bugs/153955
[17:01] <ScottK> kiko: How many of those are as wrong as this one?  So far you are 0 for 1 I've looked at.
[17:02] <kiko> behold the statistics ;)
[17:04] <ScottK> Well so far, I've wasted a fair amount of time getting something that is of no value to me right.  I don't understand why it exists at all.
[17:04] <kiko> ScottK, it would help if you helped maintain the upstream project, given you are an upstream developer, in this specific case. we've done that for most upstreams that we have a good relationship with
[17:04] <ScottK> Why should I spend time on it? 
[17:04] <kiko> ScottK, i.e. I maintain the kiwi and stoq packages
[17:04] <ScottK> What value is it to me as an upstream or an Ubuntu dev?
[17:04] <kiko> which I am upstream for
[17:04] <kiko> ScottK, I guess I need to write a blog entry about that
[17:05] <ScottK> As an Ubuntu dev, all I want is to be able to link to upstream bugs.  
[17:05] <kiko> ScottK, but to be honest, I'm not sure how much time you've wasted since it's me doing all the real work!
[17:05] <ScottK> All this other stuff is just extraneous cruft.
[17:05] <kiko> you are just the one being a curmudgeon. :)
[17:05] <ScottK> Well it's me sitting here pointing you at it.
[17:06] <ScottK> kiko: I do resent time I spend as a volunteer helping you improve your proprietary prodcut.  In most cases I have consulting rates for that.
[17:07] <kiko> ScottK, one day you will realize that I am just a great a person as your best friend and then you will regret being so nasty to me. but for now I will just ignore that.
[17:08]  * kiko goes back to work
[17:08] <ScottK> It's not personal
[17:08]  * ScottK really doesn't understand why noticing that launchpad is not FOSS, is being nasty.
[17:11] <LaserJock> ScottK: noticing is one thing, but "resenting" is a bit more than that
[17:12] <ScottK> LaserJock: Perhaps.  Getting forced to work on proprietary products to keep Ubuntu working nicely is something I resent, but OK.
[17:15] <ubotu> New bug: #153960 in soyuz "AMD64 sbuild didn't apt-get the 'Build-Depends-Indep' but i386 did" [Undecided,New] https://launchpad.net/bugs/153960
[17:17] <LaserJock> ScottK: right, but giving the people who *can't* change that a hard time doesn't help make it any free-er, IMO
[17:17] <ScottK> Agreed.  Equally I really don't appreciate having the time I invest in it (resentful or not) minimized.
[17:20] <ubotu> New bug: #153962 in rosetta "Sorry for being rude but this is the only way of contacting you,l " [Undecided,New] https://launchpad.net/bugs/153962
[17:22] <LaserJock> ScottK: agreed
[17:24] <kiko> well, it can be changed, and I do care a lot about it not being free software, but it's not something that happens in a blink. and creating the upstream product and maintaining the packaging link isn't making "a proprietary product" better, it's actually making the Launchpad service for Ubuntu better. but that's ill-documented and I'd better invest time in fixing that than in arguing nonsense over IRC.
[17:25] <ScottK> kiko: No trouble.  It is how it makes Ubuntu better that I really don't understand.
[17:26] <ScottK> kiko: So I'll be glad to read about it in the blog.
[18:25] <MilesTeg> hi everyone
[18:26] <jtv> hi
[18:28] <MilesTeg> I want to translate some programs. Is it possible to list all entries that are not translated yet AND have no suggestions?
[18:29] <kiko-fud> hmmm. good question.
[18:29] <kiko-fud> carlos?
[18:32] <jtv> carlos is done for the day.  I'm looking at it.  I'm already half asleep though, so don't expect much
[18:34] <jtv> MilesTeg: in the various translation overviews you'll see a column "need review."  That's the number of messages that have pending suggestions.
[18:34] <jtv> So at least you'll be able to find the templates that need your attention.  Individual messages are harder.
[18:35] <MilesTeg> ok, thx
[18:48] <MilesTeg> hm... anyway, a filter "untranslated+no suggestions" would be useful...
[18:51] <jtv> MilesTeg: you might see if there's a bug ticket for that.
[18:52] <MilesTeg> k
[18:52] <jtv> Oops, 1 AM, I'm being kicked out.  Gotta go!
[18:58] <MilesTeg> hm... yes there is a bug ticket... and at least two duplicates ;)
[19:08] <kiko-fud> MilesTeg, what's the number?
[19:08] <MilesTeg> it's #102943
[19:13] <kiko-fud> bug #102943
[19:13] <ubotu> Launchpad bug 102943 in rosetta "Allow displaying only strings that have no suggestions" [Undecided,Confirmed] https://launchpad.net/bugs/102943
[19:33] <javamaniac> hi everyone, does launchpad have some "clean" way to allow an external application to get data from it? I mean, a web service or something
[19:33] <javamaniac> I don't want to use web scrapping for that
[19:33] <mwhudson> javamaniac: it depends a bit
[19:34] <mwhudson> javamaniac: it is _absolutely_ a goal, but not one that's quite attained yet
[19:34] <mwhudson> javamaniac: what sort of info are you after?
[19:34] <javamaniac> bug reports
[19:34] <pochu> javamaniac: Actually you can use python-launchpad-bugs for that.
[19:34] <pochu> (And bughelper)
[19:35] <javamaniac> pochu, Oh, good, I'll search about it
[19:35] <ScottK> pochu: bughelper screen scrapes, IIRC.
[19:35] <javamaniac> does it?
[19:36] <ScottK> Last I looked, yes, but it's been a while.
[19:38] <kiko> javamaniac, how much do you need from the bug?
[19:38] <javamaniac> kiko, I want to be able to search on the Bug Database (aka Malone)
[19:39] <javamaniac> soren, the most of the information, the better
[19:39] <kiko> javamaniac, search and do what with the results?
[19:39] <javamaniac> so*
[19:41] <javamaniac> kiko, I'm doing web app to search on some Bug tracking systems , I have debbugs and bugzila, I'd like to search on Malone from my app
[19:41] <javamaniac> (yeah, I know launchpad does it a long time ago)
[19:42] <javamaniac> but i'd like to make it on my own way, I'm playing with some ideas about it right now
[19:47] <kiko> javamaniac, okay, that's cool, but what sort of information do you want from the results? just the bug ids?
[19:48] <javamaniac> kiko, the summary would be cool too
[19:50] <kiko> javamaniac, mmmm. we used to have a working way to do queries for bug that returned text only. I'll look into fixing it :-/
[19:51] <javamaniac> kiko, great!, let me know about it :)
[19:55] <ubotu> New bug: #154018 in launchpad "supermirror@vostok keep locking my branch" [Undecided,New] https://launchpad.net/bugs/154018
[21:40] <ubotu> New bug: #154053 in launchpad "launchpad account does not work in news" [Undecided,New] https://launchpad.net/bugs/154053
[21:55] <ubotu> New bug: #154057 in soyuz "DistroSeries architecture list sorts randomly" [Undecided,New] https://launchpad.net/bugs/154057