[12:40] <ubotu> New bug: #117460 in launchpad "Linking to upstream bugs is counter-intuitive" [Undecided,Unconfirmed]  https://launchpad.net/bugs/117460
[12:41] <elmo> mwh: are you looking after loggerhead yet?
[12:49] <mwh> elmo: to some extent, i'm not sure how much i'm supposed to be looking after the running of it
[12:49] <mwh> elmo: is it wedged again?
[12:49] <elmo> mwh: well, it was using 1.5Gb of RSS memory which was causing the box to thrash
[12:49] <elmo> but since I asked it seems to have calmed down
[12:50] <mwh> someone was probably looking at the inventory view
[12:51] <mwh> https://bugs.launchpad.net/loggerhead/+bug/116869
[12:51] <ubotu> Launchpad bug 116869 in loggerhead "viewing the file listing consumes a lot memory" [Undecided,Unconfirmed]  
[12:52] <mwh> it's on the list of things to look at this week
[12:53] <elmo> k
[05:35] <ASCIIGirl> hello world! I found this --> "Fixed in RF 4082" closing a bug, can anybody tell me what RF refers to? , appears on bug #70074
[05:35] <ubotu> Launchpad bug 70074 in rosetta "Add direct link downloads" [Low,Fix released]  https://launchpad.net/bugs/70074 - Assigned to Carlos Perell Marn (carlos)
[05:40] <LaserJock> I *think* the RF is something like a revision #
[05:42] <ASCIIGirl> LaserJock, any idea if ubuntu has something like a dictionary of those words? cause I been googling and checking the wiki without finding anything useful :(
[05:43] <LaserJock> well, it isn't Ubuntu-specific
[05:43] <LaserJock> and it's an internal thing
[05:43] <ASCIIGirl> aw that makes my search a bit more difficult :-) 
[05:44] <ASCIIGirl> anyway, thanks LaserJock 
[05:45] <LaserJock> you could email launchpad-users mailing list
[05:45] <LaserJock> that might be a good way to draw attention to the issue ;-)
[05:45] <LaserJock> ah, or ask Fujitsu ;-)
[05:47] <ASCIIGirl> heheheh..so means rocket fuel.... :)
[05:51] <thumper> ASCIIGirl: yes it means rocketfuel
[05:51] <thumper> and the number is the bzr revision number for our main development branch
[05:55] <ASCIIGirl> thumper, on this bug just says a "fix released" and speaks about few problems on the same bug...
[05:55] <ASCIIGirl> I would like to know which of the problems of that bugs were fixed on that revision and which was the solution given...any idea where I can find that? 
[05:56] <LaserJock> if it's marked Fix Released then the bug should be fixed with that revision
[05:57] <Fujitsu> Fix Released is when that revision hits production.
[05:57] <Fujitsu> Fix Committed is when it's committed to rocketfuel.
[05:58] <ASCIIGirl> the point is that on the bug tells about 2 steps....that means both steps were implemented?
[06:07] <stub> ASCIIGirl: A fix released bug should mean all issues with this bug have been dealt with and all relevant changes are running on the production systems.
[06:07] <ASCIIGirl> stub, thanks ...
[06:08] <stub> ASCIIGirl: If that is not the case, then someone made a mistake or was not clear enough (eg. I'm opening up a new bug on this seperate issue)
[06:09] <ASCIIGirl> stub Im checking in rosetta if the 2nd step of the bug its also fixed...
[06:13] <ASCIIGirl> if there is any rosetta expert around: is it possible to do daily exports so upstream can fetch translations automatically?
[08:02] <thumper> lifeless: ping
[08:02] <thumper> lifeless: AU reviewers meeting?
[08:03] <jml> review my branch, reviewers
[08:43] <lifeless> thumper: Mondays...
[08:46] <`23meg> has anyone run into upstream project being incorrectly filled in as "rebuntu" when marking a bug as affecting upstream? looks like a bug.
[08:49] <`23meg> looks like specific to gnome-terminal
[08:50] <LaserJock> I've seen some things with rebuntu
[08:50] <thumper> lifeless: last week we moved it to Tuesday and updated the wiki
[08:50] <crimsun> no, it has struck every instance that I tried yesterday, but I wasn't able to follow through
[08:50] <crimsun> (the whole mantis isn't supported yet)
[08:51] <`23meg> LaserJock, I think the upstream product for gnome-terminal incorrectly points to rebuntu when marking as affects upstream
[08:56] <lifeless> thumper: oh!. what time tuesdays ?
[09:03] <Fujitsu> `23meg: Right, the creator the rebuntu project assigned it as upstream for a number of Ubuntu packages. There's no UI to reverse that at the moment.
[09:04] <`23meg> thanks Fujitsu
[09:11] <carlos> morning
[09:11] <Fujitsu> Hi carlos.
[09:12] <beuno> mornin' carlos
[09:12] <beuno> how are you today?
[09:13] <carlos> beuno: fine thanks, and you?
[09:13] <beuno> pretty good, getting ready to go to sleep
[09:14] <beuno> I've been working on some new rosetta specs, so expect to have a bigger queue pretty soon   :D
[09:21] <`23meg> bug #117494 filed :)
[09:21] <ubotu> Launchpad bug 117494 in launchpad "Rebuntu incorrectly marked as upstream for some Ubuntu packages" [Undecided,Unconfirmed]  https://launchpad.net/bugs/117494
[09:23] <thumper> lifeless: 06:00 UTC
[09:25] <ubotu> New bug: #117494 in launchpad "Rebuntu incorrectly marked as upstream for some Ubuntu packages" [Undecided,Unconfirmed]  https://launchpad.net/bugs/117494
[09:26] <beuno> I'm off, night everyone
[09:34] <lifeless> thumper: ok, I can do that. I do think its nice to have the convenor of the meeting present when its rescheduled though :)
[09:58] <thumper> lifeless: yeah, sorry
[11:05] <ubotu> New bug: #117508 in rosetta "Last translator field should handle accounts without email address" [Undecided,Unconfirmed]  https://launchpad.net/bugs/117508
[11:14] <beuno> carlos: I'm triaging some rosetta bugs, trying to clean it up a bit, should I be doing this, or does this fall upon the launchpad devs exclusively?
[11:15] <carlos> beuno: any help is welcome. We do it from time to time
[11:16] <carlos> as long as you don't do weird things... you are free to help there too :-9
[11:16] <carlos> :-)
[11:16] <beuno> ok, great, I'm drafting up a few specs, and I want to relate them to existing bugs/specs, but I keep bumping into duplicate bug reports, or some that just don't seem to apply anymore
[11:16] <beuno> (including 2 bugs I had reported a while back)
[11:17] <beuno> so I figured why not tidy that a bit while I'm at it
[11:17] <carlos> feel free to ask us if you have doubts about any of those
[11:17] <carlos> beuno: and thanks for your help
[11:18] <beuno> carlos: my pleasure, we all use rosetta, so I guess we should give back a bit anyway
[11:18] <beuno> if you can take a look at: https://bugs.launchpad.net/rosetta/+bug/39291
[11:18] <ubotu> Launchpad bug 39291 in rosetta "status bar on package listing wrong" [Medium,Confirmed]  
[11:19] <beuno> I marked 3 of them duplicates to that bug
[11:26] <carlos> beuno: I guess it would be a duplicate, yes
[11:26] <carlos> either that or a bug in statistics that is already fixed
[11:28] <beuno> one last bug, then I'm off to work on my spec, https://bugs.launchpad.net/rosetta/+bug/20   seems to be in place, right?
[11:28] <ubotu> Launchpad bug 20 in rosetta "Sort translatable applications with most-wanted translations first" [Wishlist,Confirmed]   - Assigned to Carlos Perell Marn (carlos)
[11:29] <carlos> beuno: we have priorities for templates
[11:29] <carlos> but that request goes further 
[11:29] <carlos> I don't think we could say it's fixed
[11:30] <beuno> right, I'll stay out of bugs that go that deep then
[11:30] <beuno> thanks carlos  :D
[11:30] <carlos> np
 I did get a bit frustrated that I run into so many specs located in Launchpad's wiki and can't access them </nag>
[11:42] <beuno> carlos: searching through the specs, I found one that is very similar to what I'm working on (again, can't be certain since I can't actually *see* it), does it make sense to draft it up considering I can't edit/see the current one?   what are my options?
[11:43] <carlos> tell me the spec you are writing and I would be able to tell you whether is the same or not
[11:43] <beuno> (most of this is coming after a talk I gave on launchpad, and a profesional translator approached me and we talked for about half an hour about how to improve it)
[11:43] <carlos> we cannot publish our specs right now, but you can talk about that with kiko or SteveA
[11:43] <beuno> I'm referring to: https://blueprints.launchpad.net/rosetta/+spec/rosetta-word-lists
[11:44] <beuno> the basic idea is for each language team to have a list of "prefered" words, so we can have some uniformity across packages
[11:45] <carlos> beuno: that spec is empty and we didn't write it yet
[11:45] <beuno> if that word would be on the string to translate, the pre-set translation recommendation should be suggested somewhere
[11:45] <carlos> if you want to draft it, you can do it on wiki.ubuntu.com and update the link to yours (or ask me to do it if you don't have enough rights)
[11:47] <beuno> carlos: great, I'll draft it then and add the link to the whiteboard so you can edit it in (I can't change it, I just checked), does that work?
[11:48] <carlos> yeah
[11:48] <carlos> I just removed the link to the empty one
[11:48] <beuno> thanks  :D
[11:49] <beuno> just curious, what would give me rights to edit it?   to be set as a drafter?
[11:51] <carlos> beuno: I think you need to be the owner of the project
[11:51] <carlos> like I'm
[11:51] <carlos> anyway, let me set you as the drafter
[11:52] <beuno> carlos: thanks again, I'll let you work now and start the draft on the wiki
[11:52] <carlos> beuno: you are now the drafter, check whether you have permissions now
[11:53] <beuno> carlos: yes I can  :D
[11:53] <carlos> :-)
[11:53] <beuno> ok, so that's what I'll be bothering you next
[11:53] <beuno> :p
[11:54] <carlos> enjoy! :-)
[12:31] <mpt> Gooooooooooooood evening Launchpadders!
[12:33] <Hobbsee> heya mpt 
[01:04] <mpt> crud, just got a "Fobidden" error that I shouldn't have, but I can't reproduce it
[01:29] <sacater> whats being done about the ansewrs bug :(
[01:29] <mpt> sacater, there are 47 Answers bugs. Which one are you referring to?
[01:30] <sacater> mpt: the one where you enter nothing and you get an OOPS when you click 'find answers'
[01:30] <mpt> oh
[01:30] <ubotu> New bug: #117525 in launchpad-answers "Retargeting and setting whiteboard are forbidden when done simultaneously" [Undecided,Unconfirmed]  https://launchpad.net/bugs/117525
[01:30] <mpt> ^^^ that's the 47th
[01:32] <Hobbsee> mpt: you're supposed to be able to mindread.
[01:36] <mpt> I should have read the job description more closely
[01:37] <Hobbsee> indeed.
[01:42] <mpt> sacater, according to the bug report, it's been fixed in the code, so it'll be fixed on launchpad.net in a couple of weeks
[01:42] <sacater> :o
[01:43] <sacater> how many...
[01:43] <mpt> It seems like doing an empty search is a pretty easy thing to avoid, though
[01:43] <mpt> in the meantime
[01:43] <mpt> oh
[01:43] <mpt> Does it happen when searching for (for example) all the Needs Info questions?
[01:44] <mpt> hmm, no, those controls aren't available on that page
[01:46] <mpt> So the problem doesn't occur when you specify a project
[01:46] <mpt> It doesn't occur on a project's Answers page
[01:46] <mpt> It occurs only if you search for nothing at all on https://answers.launchpad.net/
[01:46] <beuno> sacater: launchpad is normally updated on tuesdays, so unless the fix creates problems in other places, it's probable that it will land by next week (unless mpt says differently)  :p
[01:46] <mpt> I can't think of a reason for doing that
[01:47] <mpt> Not saying that it shouldn't be fixed (it will be), just that it doesn't seem urgent.
[01:49] <cprov-fud> morning, guys.
[01:59] <carlos> beuno: that's not true anymore
[02:01] <carlos> beuno: we are doing an update once per month, usually third Thursday of the week (although it would change depending on the cycle)
[02:01] <carlos> we started with that this month
[02:04] <mpt> matsubara, hi, you called me while I was asleep
[02:05] <carlos> cprov-fud: morning
[02:05] <matsubara> mpt: hello matthew
[02:05] <Hobbsee> mpt: new form of alarm.
[02:05] <matsubara> mpt: so, I was trying to get the ies4linux to work
[02:05] <matsubara> mpt: is there any special trick to make the rendering work? (I installed it fine, but it doesn't render the page)
[02:11] <siretart> cprov: is it possible that the ppa chroots have only 'main' activated? 
[02:11] <siretart> cprov: ffmpeg is still waiting for liba52-0.7.4-dev, again. and that should be available in gutsy/universe
[02:13] <cprov> siretart: yes, you were *victim* of ogre-component algorithm (sources in main can only build-depend on main and so on ...)
[02:14] <Hobbsee> siretart: are they open to all of ubuntu-dev, or just specific people?
[02:18] <siretart> Hobbsee: you need to ask this cprov
[02:18] <Hobbsee> cprov: ^
[02:18] <siretart> cprov: so I cannot do anything about it?
[02:19] <siretart> hm. okay, then I need to look for something else
[02:21] <cprov> siretart: you can re-upload the package to 'universe' 
[02:21] <beuno> carlos: good to know, I'll have to update a few slides for that
[02:23] <siretart> cprov: sorry? how to do that?
[02:24] <siretart> cprov: you mean uploading to "~siretart/ubuntu/gutsy/universe"?
[02:24] <mpt> matsubara, I didn't do anything special
[02:24] <mpt> Sorry I don't know what your problem might be there
[02:24] <cprov> siretart: nope, you have to change the package section metadata 'universe/devel'
[02:25] <mpt> matsubara, unless you have Desktop Effects turned on (just a guess, haven't tried it)
[02:26] <mpt> carlos, will this be the earliest in the release cycle that translations have opened for any Ubuntu release?
[02:26] <carlos> mpt: indeed
[02:26] <mpt> That's cool!
[02:26] <mpt> That should make life a lot easier for LOTE Ubuntu users
[02:27] <matsubara> mpt: well, I'm using the beta version. I'll read documentation and see if I can find anything. thanks anyway.
[02:27] <mpt> Well done, sir
[02:27] <carlos> s/sir/team/
[02:27] <carlos> ;-)
[02:27] <mpt> indeed
[02:28] <siretart> cprov: oh. that sounds great. thanks
[02:40] <kiko> cprov, might be interesting to allow overriding component via the directory as well
[02:40] <Hobbsee> heya kiko!
[02:40] <kiko> hey Hobbsee 
[02:40] <kiko> nice to hear you around
[02:40] <Hobbsee> kiko: hear me around?  *didnt think she'd been stomping*
[02:41] <kiko> Hobbsee, these electrons make a lot of noise
[02:41] <Hobbsee> hehe
[02:41] <cprov> kiko: it's possible
[02:42] <kiko> cprov, dunno if we actually want to. might be something to ask our users, distro guys and sabdfl 
[02:42] <cprov> kiko: since we are catching users too often with "ogre" trap
[02:43] <kiko> cprov, why are they uploading to main? ah, they don't provide a component in the Section: line, right?
[02:43] <kiko> slightly tricky
[02:43] <kiko> I think components for PPAs are bong anyway
[02:43] <cprov> kiko: well, they have to cope with it if they are intended to fit in ubuntu
[02:44] <cprov> kiko: but I understand that they are two different concerns (to work vs. to fit in ubuntu)
[02:45] <kiko> cprov, right, but then during the NSS step they'd get a component overridden in.
[02:47] <cprov> kiko: yes, and that might make the source FTBFS since we force 'ogre'
[02:47] <kiko> oh, because the section in the DSC won't match. you're right.
[02:48] <cprov> kiko: that too, the main problem is that it won't build again in ubuntu because it doesn't respect ogre (main can only build-dep on other main, and so on )
[02:49] <kiko> it might not, right
[02:55] <kiko> Fujitsu, we probably won't offer overrides. removals will be done initially via admin request, and then you'll have a UI for doing it
[02:55] <cprov> Fujitsu: via the web UI 
[02:56] <Fujitsu> What will happen if something from Debian is uploaded with component contrib or non-free?
[02:57] <kiko> Fujitsu, it will be rejected. it should be changed before uploading.
[02:57] <Fujitsu> Hmm...
[02:57] <kiko> I don't like that very much though
[02:57] <kiko> I think we should consider components more carefully for PPA
[02:57] <Fujitsu> That means introducing more changes, which is  somewhat silly.
[02:59] <Hobbsee> kiko: did you come to any conclusions on what you said you'd have to go and think about, with the bugs at UDS?
[02:59] <kiko> Hobbsee, I did list a large number of enhancements for BjornT to consider
[03:00] <Hobbsee> kiko: are they public?
[03:00] <kiko> I could make them public
[03:01] <Hobbsee> that'd be interesting to see, at least.
[03:01] <Hobbsee> even if you dont want input on them
[03:01] <kiko> I'll email you the wikitext
[03:01] <kiko> hang on
[03:02] <Hobbsee> great :)
[03:02] <seb128> hi
[03:03] <seb128> kiko: any news on the "rebuntu" tasks hijack?
[03:03] <kiko> seb128, I'm going to sort it out today.
[03:03] <seb128> cool
[03:03] <kiko> I contacted the guy and wanted to wait for him to reply
[03:03] <kiko> but now I say boo
[03:05] <seb128> right
[03:07] <seb128> Hobbsee: what do you read?
[03:09] <Hobbsee> seb128: possible enhancements for LP.  was from before you came in
[03:09] <seb128> ah, k
[03:09] <seb128> URL? ;)
[03:11] <Hobbsee> kiko: all looks sane, except = Collapsing all bug comments =
[03:11] <Hobbsee> seb128: via email
[03:11] <seb128> k
[03:12] <kiko> seb128, https://launchpad.canonical.com/SevillaBugTrackerProposals#preview
[03:12] <kiko> Hobbsee, I like collapsing all bug comments, though
[03:13] <Hobbsee> kiko: they're annoying to open all of them - particularly if there are lots
[03:13] <kiko> Hobbsee, they'd be all collapsed at once
[03:13] <kiko> I guess I need to clarify that in the spec
[03:13] <Hobbsee> one of the blogs i sometimes read did that - the screams *still* havent stopped, and it was changed a month or so ago.
[03:13] <kiko> a single twistie for the whole comment section
[03:13] <Hobbsee> ah right.  not quite so evil then.
[03:14] <seb128> if you collapse comments please make possible to change the default
[03:15] <kiko> To make bug reports more concise, we could collapse all the bug comments and the comment field. Comments would be collapsed using a single twisty, meaning that they would either all be collapsed or all be uncollapsed (this does not address the deletion/hiding of specific comments).
[03:15] <seb128> or that would mean one extra click every time triagers open a bug
[03:15] <kiko> seb128, the default would be persistent, yes.
[03:15] <seb128> good
[03:32] <mpt> kiko, I'm not sure that "concise" is quite what you mean there
[03:32] <mpt> It wouldn't be reducing the amount anyone had to read
[03:32] <mpt> s/had/needed/
[03:32] <kiko> mpt, they can choose to not read the comments if they don't want to.
[03:33] <kiko> I don't think the use of "concise" is mine but whatever
[03:33] <mpt> People can already choose not to read them. :-)
[03:33] <kiko> mpt, not really
[03:33] <kiko> I mean, try not reading the comments in bug #1
[03:33] <ubotu> Launchpad bug 1 in Ubuntu "Microsoft has a majority market share" [Critical,In progress]  https://launchpad.net/bugs/1 - Assigned to Mark Shuttleworth (sabdfl)
[03:34] <Spads> the load time for that bug is pretty impressive
[03:34] <mpt> I think the #1 beneficial way of decreasing the number of comments people have to read would be making editing the description more obvious and quicker to do.
[03:39] <mpt> But if you're the relevant developer, I think not reading a comment that's already posted is safe only if someone you trust has already marked that particular comment as not being relevant.
[03:39] <mpt> (I dare you to diagram that sentence!)
[03:41] <Hobbsee> i'd love to see a different colour for posters in ~ubuntu-dev or something
[03:41] <Hobbsee> particularly for kernel bugs, with a lot of traffic
[03:41] <Hobbsee> no idea fi that's feasible - but if you're kicking around new ideas...
[03:42] <kiko> Hobbsee, we're working on that
[03:42] <mpt> It is feasible, we're considering something similar for Answers
[03:42] <Hobbsee> it's very hard to see who's official, and who's not, seeing as they're all offering advice, saying it must be fixed immediately, etc
[03:42] <Hobbsee> ah, great.
[03:42] <mpt> also highlighting the reporter
[03:42] <mpt> (comments from them, I mean)
[03:44] <kiko> Fujitsu, you mean rejected/wontfix?
[03:45] <Fujitsu> kiko: No, as in the bug manifests itself in this package primarily, but is in fact a bug elsewhere. I don't want the task in that package open as such, as it's not a bug there. But it should be visible as people will look for it there.
[03:46] <kiko> Fujitsu, in a single word? :-)
[03:47] <Fujitsu> No idea.
[03:48] <kiko> SEP!!!
[03:48] <Fujitsu> Heheh, yes!
[03:48] <mpt> Fujitsu, so you want "Not For Us"
[03:48] <kiko> mpt, it's more SEP than NFU
[03:48] <kiko> NOP
[03:48] <mpt> SEP?
[03:48] <Hobbsee> ooh, i want a SEP!!!!
[03:48] <Fujitsu> mpt: Not quite. kiko: Right.
[03:48] <kiko> someone else's problem
[03:48] <Hobbsee> mpt: Someone Else's Problem
[03:48] <kiko> not our problem
[03:48] <kiko> etc
[03:49] <mpt> oh
[03:49] <highvoltage> what is SEP?
[03:49] <mpt> I want fewer bug statuses
[03:49] <highvoltage> ah, I get it
[03:49] <Hobbsee> highvoltage: see 5&6 lines up
[03:49] <highvoltage> someone elses problem
[03:49] <Fujitsu> mpt: But I want to be able to handle this use case.
[03:50] <mpt> I understand
[03:50] <mpt> because it'll reduce duplicates
[03:51] <mpt> We had a long long discussion about what this status should be called
[03:51] <mpt> I don't remember anyone suggesting SEP
[03:51] <mpt> though
[03:51] <mpt> bug 36059
[03:51] <ubotu> Launchpad bug 36059 in malone ""Rejected" should be split into "Not a Bug" and "Not For Us"" [Medium,Confirmed]  https://launchpad.net/bugs/36059 - Assigned to Matthew Paul Thomas (mpt)
[03:51] <Fujitsu> I've seen that.
[03:51] <kiko> mpt, Not For Us is slightly different
[03:51] <Fujitsu> But NFU is somewhat different.
[03:51] <mpt> But then Ubuntu's Mozilla team disillusioned me
[03:52] <mpt> How is it different?
[03:52] <kiko> it means that we /could/ fix the problem but we don't want to
[03:52] <kiko> whereas in this cas
[03:52] <Fujitsu> Right.
[03:52] <kiko> e it means that the problem needs to be fixed somewhere else
[03:52] <kiko> for us to benefit
[03:52] <mpt> I'm not really interested in a difference in meaning
[03:52] <mpt> I'm interested in a difference in use case
[03:52] <mpt> in effect, I mean
[03:52] <kiko> I just explained though
[03:52] <mpt> Is there a listing on which Not For Us bugs should appear but Seomeone Else's Problem bugs should not, or vice versa?
[03:53] <kiko> it depends
[03:53] <kiko> you could say there's a useful listing of things broken in X that depend on work done elsewhere
[03:54] <mpt> SEP is included in my definition of NFU in the bug report: "for example, it should be fixed in a toolkit or kernel instead"
[03:54] <Hobbsee> have 2 categories of bugs, easy for developers to split.  "fixable in $product" and "not for us"
[03:54] <Hobbsee> or whatever
[03:55] <mpt> kiko, you could get that with an advanced search (which could be a canned search, even)
[03:55] <kiko> mpt, yeah.. I don't care so much TBH.
[03:55] <mpt> In the SearchingBugs-spec syntax, it would be "status:not-for-us elsewhere:open"
[03:57] <kiko> ah right
[04:44] <johan> Hi. Is codebrowse.launchpad.net known to be down ?
[04:46] <matsubara> the man has arrived. mthaddon: <johan> Hi. Is codebrowse.launchpad.net known to be down ?
[04:46] <mthaddon> matsubara: yes, restarting it now
[04:46] <matsubara> mthaddon: thank you
[04:46] <johan> thanks!
[04:47] <mthaddon> ok, should be working now
[04:47] <johan> yeah, seems to be working, excellent
[04:47] <mwhudson> grumble
[05:20] <ubotu> New bug: #117565 in launchpad-bazaar "Seems to use URL quoting instead of HTML in links" [Undecided,Unconfirmed]  https://launchpad.net/bugs/117565
[06:41] <ubotu> New bug: #117582 in launchpad "Duplicated bugs in bugs.launchpad.net/~user" [Undecided,Unconfirmed]  https://launchpad.net/bugs/117582
[08:06] <mthaddon> edge.launchpad.net is going to - server being rebooted
[08:11] <LaserJock> hi kiko 
[08:13] <mthaddon> edge.launchpad.net is back up
[08:14] <kiko> hey LaserJock 
[09:31] <carlos> good night!
[09:50] <kiko> siretart, ping?
[09:50] <siretart> kiko: pong
[09:50] <siretart> these ppa's are giving me headaches...
[09:50] <kiko> siretart, did you do https://bugs.launchpad.net/ubuntu/+source/rats/+bug/63561/comments/8 yourself?
[09:50] <ubotu> Launchpad bug 63561 in rats "Segmentation fault when auditing code" [Undecided,Fix released]  
[09:50] <kiko> siretart, or was it done through changelog-closes-bug?
[09:51] <siretart> kiko: this was done via changelog-closes-bug.
[09:51] <kiko> siretart, you are a genius! I love you
[09:51] <siretart> kiko: I'm using it now in every upload :)
[09:51] <kiko> ROCK ON!
[10:00] <LaserJock> siretart: wow, awesome
[10:01] <siretart> LaserJock: can you add the following to your sources.list:
[10:01] <siretart> deb http://ppa.dogfood.launchpad.net/siretart/ubuntu gutsy main universe multiverse
[10:01] <siretart> deb-src http://ppa.dogfood.launchpad.net/siretart/ubuntu gutsy main universe multiverse
[10:01] <siretart> and check if you have the package emacs-snapshot-common with version 1:20070521-1 in your apt-cache?
[10:02] <siretart> It doesn't show up for me, but it does appear in http://ppa.dogfood.launchpad.net/siretart/ubuntu/dists/gutsy/main/binary-amd64/Packages.gz
[10:02] <siretart> cprov: ^^^
[10:03] <cprov> siretart: one sec
[10:04] <LaserJock> siretart: yes, I've got it
[10:05] <kiko> siretart, thanks for testing, I really appreciate it
[10:05] <LaserJock> mantha@luck:~$ apt-cache madison emacs-snapshot-common
[10:05] <LaserJock> emacs-snapshot-common | 1:20070521-1 | http://ppa.dogfood.launchpad.net gutsy/main Packages
[10:05] <LaserJock> emacs-snapshot-common | 1:20070302-1 | http://archive.ubuntu.com gutsy/universe Packages
[10:05] <LaserJock> emacs-snapshot | 1:20070302-1 | http://archive.ubuntu.com gutsy/universe Sources
[10:05] <LaserJock> emacs-snapshot | 1:20070521-1 | http://ppa.dogfood.launchpad.net gutsy/main Sources
[10:05] <siretart> LaserJock: are you on i386 or amd64?
[10:05] <LaserJock> i386
[10:06] <siretart> I'm on amd64, and only see the version from archive.ubuntu.com, not the one from dogfood
[10:06] <cprov> siretart:      1:20070521-1 0
[10:06] <cprov>         500 http://ppa.dogfood.launchpad.net gutsy/main Packages
[10:06] <siretart> cprov: amd64 or i386?
[10:06] <cprov> siretart: i386
[10:06] <siretart> please try on amd64
[10:07] <cprov> siretart: not 
[10:08] <siretart> cprov: puh, then the problem is (at least) not on my side :)
[10:08] <geser> siretart: apt-cache madison on amd64 lists only the source for emacs-snapshot-common but not the binaries
[10:09] <siretart> which is why I cannot install emacs-snapshot :/
[10:09] <geser> but I've a file /var/lib/apt/lists/ppa.dogfood.launchpad.net_siretart_ubuntu_dists_gutsy_main_binary-amd64_Packages
[10:10] <siretart> interesting. there, I get the package version in question
[10:10] <siretart> what the heck is going on here?
[10:10] <geser> and Package: emacs-snapshot-common has Architecture: i386
[10:11] <geser> apt-cache policy emacs-snapshot-gtk lists also your ppa version
[10:12] <geser> that package is listed with Architecture: amd64
[10:13] <siretart> geser: hmmm. it should be arch: all
[10:13] <siretart> cprov? can you imagine whats wrong here?
[10:14] <siretart> wow. manually fiddling in /var/lib/apt/lists/ppa.dogfood.launchpad.net_siretart_ubuntu_dists_gutsy_main_binary-amd64_Packages indeed helps
[10:14] <siretart> geser: good eye, http://ppa.dogfood.launchpad.net/siretart/ubuntu/dists/gutsy/main/binary-amd64/Packages.gz is indeed fishy
[10:15] <cprov> siretart: well, it's quite possible that I'm generating the index in the wrong way
[10:15] <cprov> siretart: geser: why should it be 'all' ?
[10:16] <siretart> cprov: because it is an architecture: all package
[10:16] <siretart> cprov: Filename: pool/main/e/emacs-snapshot/emacs-snapshot-el_20070521-1_all.deb
[10:16] <siretart> (pasted from the Packages.gz file)
[10:17] <cprov> whole cow, you're right .. I'm annotating the arch where it was built, i386
[10:17] <cprov> siretart: ok, can you file a bug about it 
[10:18] <cprov> s\whole\holly ... 
[10:18] <kiko> holy
[10:18] <kiko> :)
[10:19] <LaserJock> and here I thought PPA was perfect
[10:19] <LaserJock> all my hopes have been shattered ;-)
[10:22] <cprov> LaserJock: come one, I'm glad that it's such simple bug 
[10:22] <cprov> LaserJock: i can fix it in a minute.
[10:24] <siretart> cprov: you still want a bug about that? against what?
[10:25] <cprov> siretart: soyuz
[10:25] <siretart> k
[10:26] <cprov> siretart: thanks a lot for identifying this.
[10:29] <LaserJock> \o/ for testing :-)
[10:29] <cprov-out> LaserJock: indeed
[10:32] <asabil> hello all
[10:32] <asabil> does launchpad provide any sort of wiki ?
[10:40] <siretart> cprov-out: I think this is https://bugs.launchpad.net/soyuz/+bug/40096
[10:40] <ubotu> Launchpad bug 40096 in soyuz "do not show architecture 'all' builds as i386" [Medium,Confirmed]   - Assigned to Diogo Matsubara (matsubara)
[10:42] <cprov-out> siretart: not really, we have a much more specific issues like 'PPA archive indexes do not properly list architeture-independent package'
[10:43] <siretart> cprov-out: filed as https://bugs.launchpad.net/soyuz/+bug/117625
[10:43] <ubotu> Launchpad bug 117625 in soyuz "architecutre: all packages appear as architecture: i386 packages in Packages.gz" [Undecided,Unconfirmed]  
[10:44] <cprov-out> siretart: perfect
[10:51] <ubotu> New bug: #117625 in soyuz "architecture: all packages appear as architecture: i386 packages in Packages.gz" [High,In progress]  https://launchpad.net/bugs/117625
[11:51] <ubotu> New bug: #117631 in malone "Dell Optiplex GX50, Cannot Install From CD" [Undecided,Unconfirmed]  https://launchpad.net/bugs/117631