[05:04] <Rocket2DMn> ok guys, bug 308978 - xorg or linux?
[05:07] <Ryan52> xorg, I think.
[05:09] <Rocket2DMn> that seems to be it since restarting X fixes it.  But the suspend/resume is suspicious
[05:10] <Ryan52> ya....hrm.
[06:36] <Ziroday> ogasawara: ping
[07:45] <shiunji> ugh, ever since the last hardy update, firefox has been *really* crashy
[07:46] <shiunji> not sure which bug this goes under since i don't have a bt or anything, but i assume it's well known since up until now FF never crashed on my system
[07:47] <shiunji> have there been lots of recent complaints about it lately?
[09:30] <whatisneveritis> how do I find out which package gnome-display-properties belongs to?
[09:31] <Ryan52> whatisneveritis: dpkg -S `which gnome-display-properties`
[09:31] <whatisneveritis> thanks
[09:45] <Hew> Who can access bug 310126? It's referenced in the latest xorg changelog, but apparently even Bug Control can't access it. I haven't come across this situation before..
[13:23] <alinhan> hello
[13:23] <alinhan> can someone help me with reporting a bug?
[13:24] <Hew> alinhan: What do you need help with?
[13:24] <alinhan> today I did my first ISO test and hit a problem right at the beginning
[13:25] <alinhan> and since this is my first test and my first possible bug report, I wan't to make sure that I didn't screw up somewhere in the process
[13:26] <alinhan> the ISO I tested is this: http://iso.qa.ubuntu.com/qatracker/info/2204
[13:27] <alinhan> and the problem that I run into is that the keyboard doesn't work at the graphical boot menu
[13:27] <Hew> alinhan: I wouldn't worry about that, you're not going to break anything :P. Just make sure all the relevant details are there and a triager will check it and ask for any additional info.
[13:27] <alinhan> ok, thanks
[13:27] <Hew> ah ok
[13:28] <Hew> alinhan: Have you tested a previous iso (even a previous release) and had the keyboard working?
[13:28] <Hew> alinhan: If we know that, we can determine where the regression occurred (if it's a regression at all)
[13:28] <alinhan> no, but on that machine I have another OS on another HDD, that works fine
[13:29] <alinhan> the other OS is Windows XP
[13:29] <Hew> alinhan: So this Jaunty daily CD is the first Ubuntu CD you've used on the machine?
[13:29] <alinhan> yes
[13:29] <Hew> Do you have an Intrepid LiveCD lying around?
[13:30] <Hew> it may be worth trying that if you do
[13:30] <alinhan> ok, will try Intrepid
[13:30] <Hew> alinhan: Yea that would be good additional info
[13:30] <alinhan> can I get back to you after that?
[13:30] <Hew> alinhan: In any case feel free to report the bug when you're ready, a triager will ask for any needed information :-)
[13:30] <Hew> alinhan: Of course
[13:31] <alinhan> ok, thanks
[13:31] <Hew> alinhan: Thank you for your help with testing!
[13:31] <alinhan> glad to help
[13:41] <bramlet> i was unable to install 64 bit guest in virtualbox is this just a missing feature?
[13:42] <bramlet> version 2.1 is supposedly able to have 64bit guest on 32 bit host i have 64 bit host
[13:54] <Hew> bramlet: 2.0 was meant to have it but there have been issues, I've already reported a bug for it and there's a 2.1 upgrade bug as well.
[13:56] <Hew> bramlet: bug 271651, bug 304859
[13:58]  * Hobbsee wonders how that can possibly class as 'triaged' without a package attached.
[13:58]  * Hobbsee bumps it back to new
[14:01] <Hew> Hobbsee: Triaged means the bug report has all the necessary info, right? I suppose for upgrade requests there isn't much difference between new and triaged.
[14:05] <Hew> Hobbsee: What should be added to the report to justify triaged status? A debdiff?
[14:18] <Hew> Hobbsee: Bug 304859 was triaged by blueyed who has done the virtualbox-ose uploads in the past.
[14:18] <Lupine> hello all, I wanted to help give something back to Ubuntu and decided to help triage bugs
[14:18] <Lupine> I just read over the: https://wiki.ubuntu.com/Bugs/HowToTriage
[14:19] <Lupine> but I was curious what should be done if I can't duplicate a bug.  simply mark that in the comments, and change nothing else?
[14:20] <Lupine> also, is there anything "formal" I should do, to state that I'm triaging a particular bug?
[14:27] <Hew> Lupine: If you can't reproduce the bug, you should ask the reporter for more information on how to do so, and make sure they are using the latest version of the package. When you ask for additional information, you set the status to incomplete.
[14:27] <Lupine> Hew, great, thx!  Will do.
[14:27] <Hew> Lupine: There is nothing formal you need to do, but if you are triaging it is a good idea to join the Bugsquad if you haven't already.
[14:28] <Hew> Lupine: No worries, thanks for your help :-)
[14:29] <bramlet> I am using version 2.1 of virtual box and still cant get jauntyu alpha 2 64 bit to install....should this be a separate bug from #271651
[14:29] <bramlet> also im not sure if its even ose
[14:31] <bramlet> probably not a ubuntu bug anyway but maybe somebody knows
[14:32] <Hew> bramlet: 2.1 isn't in the Ubuntu archive so that's not an Ubuntu bug, you probably want to report that upstream.
[14:33] <Hew> bramlet: Does it say the CPU is not x86-64 when you try and boot?
[14:33] <bramlet> yeah thats what i figured
[14:33] <bramlet> yeah somthing like that...
[14:35] <bramlet> This kernal requires an x86_64 CPU, but detected an i686 CPU
[14:36] <Hew> bramlet: That may still be bug 271651. I'm not sure whether it's an upstream or Ubuntu packaging bug. I think the next step is to get 2.1 in the archive and see how that performs.
[14:37] <bramlet> I'm assuming its been reported upstream already?
[14:40] <Hew> bramlet: Well I thought it may have been an Ubuntu packaging issue with 2.0, but if you're getting the same issue with (I assume) the upstream 2.1 deb, it's probably an upstream issue. My guess is broken 64-bit guests would already be a known bug, but it's always worth checking.
[14:40] <bramlet> http://www.virtualbox.org/changeset/15251
[14:40] <bramlet> "disabled 64 bit guests for 32bit hosts for now- too much trouble"
[14:41] <bramlet> I have 64 bit host but maybe this disabled all 64bit guests
[14:41] <Hew> bramlet: Yes I have 64-bit host too. If that commit is in their 2.1 release I find that very strange indeed.
[16:01] <aji> Hi,
[16:09] <alimon> someone knows user robert-in-au??
[16:20] <Hew> alimon: No, but why do you ask?
[16:42] <MrKanister> Can someone please set the bug #6297 to "wishlist"? Thanks in advance.
[16:43] <MrKanister> It could also be "low", but i would say it's kind of feature request
[16:49] <Hew> MrKanister: I have set the importance of bug 6297 as low, since it describes a bug. I would also question such anecdotal evidence, I don't think there's anything unusual about hearing a song twice in a short period of time (as long as it's not a regular occurance).
[16:50] <MrKanister> Hew: Thanks
[16:52] <Hew> MrKanister: It's been a while since I studied statistics, but I'm sure a user could run rhythmbox for a while and see what sort of spread they get across their playlist. Also, the original bug description doesn't seem to apply to current rhythmbox. I'm thinking this should either be closed, or asked for more information.
[16:53] <Hew> I think every music player receives criticism of having a non-random shuffle, whether the criticism is deserved or not. The easiest way to check is probably to look at the code, I guess.
[16:54] <MrKanister> Hew: Yes, probably. The bug is very old (I was about to keep up with some old bugs ;)). But the last comment was written on 30.11.2008
[16:57] <Hew> MrKanister: None of the comments relate to the original bug description. I think the bug should just be closed. eg. "I just got the same song to play thrice", what does that prove?
[16:58] <MrKanister> Hew: I know what you mean. I will asked if it is still a problem and set it to "incomplete". Then we will see
[16:59] <Hew> MrKanister: Good idea. Make sure you're clear which issue you are referring to, since there are effectively two bugs in the one report.
[17:00] <alimon> hello
[17:00] <Hew> alimon: Hi
[17:00] <alimon> i want to ask about a bug in ivman
[17:00] <alimon> sorry about my poor english
[17:00] <Hew> alimon: Which bug #?
[17:02] <alimon> i dont know if is a bug but the user RobertH published a patch
[17:02] <alimon> https://bugs.launchpad.net/debian/+source/ivman/+bug/219635
[17:02] <alimon> yes
[17:04] <alimon> i was patching the sources and generate the deb
[17:04] <alimon> and install
[17:04] <alimon> the patch work ok
[17:04] <alimon> but now
[17:04] <alimon> i have another question about ivman
[17:04] <Hew> alimon: The bug is already upstream, where it looks like the patch was taken from.
[17:08] <Hew> alimon: What is the other question?
[17:08] <alimon> a ok
[17:09] <alimon> i want to add a condition in IvmConfigProperties.xml
[17:10] <alimon> i added a property in this file
[17:10] <Hew> alimon: This channel is for bug triage, not for end user support. You might be better off asking support questions in #ubuntu
[17:10] <alimon> a ok
[17:10] <alimon> thanks
[17:10] <Hew> alimon: No worries :-)
[17:26] <MrKanister> What to do with request for closed source printers?
[17:26] <MrKanister> I mean. They can not be included
[17:31] <Hew> MrKanister: I closed bug 6297. Make sure when you set bugs to incomplete that you are actually requesting some information. You should triage the bug that was originally reported.
[17:31] <Hew> MrKanister: As for the printer drivers, what is the request? Perhaps they can be added to multiverse, depending on their license.
[17:33] <MrKanister> Hew: bug #133121 is about the printing (don't mind my last comment on that bug, i did that when I was very very new to launchpad)
[17:34] <MrKanister> Hew: Sorry for not asking the right things bug #6297. the problem was that my english is not good enough and I didn't know how to ask what I wanted to ask. It was quite complicating :/
[17:37] <MrKanister> Information about copying: http://paste.pocoo.org/show/96290/
[17:37] <Hew> MrKanister: No problem, it was a messy bug that had nothing to do with the reporters problem. In many cases you can use the responses at https://wiki.ubuntu.com/Bugs/Responses if you are worried about correct English. In this case it was necessary to tell the commenters that they weren't commenting on the correct bug.
[17:39] <MrKanister> Ok, thanks
[17:40] <pleia2> I maintain a couple packages in debian, and recently there were some launchpad bugs opened against them
[17:40] <Hew> MrKanister: That license doesn't allow the distribution of the software, so it cannot be included even in multiverse.
[17:41] <pleia2> we're going to be uploading something to experimental soon, but I think I need some help with launchpad bug stuff to know how I'm supposed to report/change status/etc
[17:42] <pleia2> is there any documentation for this kind of thing someone can point me to?
[17:42] <MrKanister> Hew: So I can add a comment and close the bug?
[17:43] <Hew> pleia2: I'm not quite sure what you are asking. Are there Launchpad bugs that have been fixed in the experimental released that you want to mark as such?
[17:43] <Hew> pleia2: https://wiki.ubuntu.com/Bugs/Status ?
[17:43] <pleia2> Hew: yes
[17:44] <pleia2> but it's in debian experimental, I'm not really familiar with how ubuntu slurps the packages from debian, and until lenny is released we won't be moving the fixes to unstable and testing
[17:45] <Hew> MrKanister: Yes, notice in the license from about line 33 onwards, that's the problem. The bug should be marked invalid, but make sure you are clear about the reason.
[17:46] <Hew> pleia2: I think Ubuntu automatically takes sid packages. I've seen experimental ones around, but I think they're done manually (not sure on this).
[17:47] <Hew> pleia2: In any case, if the bugs are reported against Ubuntu then they can't be marked Fix Released until the package has landed in Ubuntu itself.
[17:47] <pleia2> Hew: right, so should I comment that it's fixed in experimenta, then mark them as fix-committed?
[17:47] <Hew> pleia2: Yep, that should work :-)
[17:48] <pleia2> awesome, thanks :)
[17:48] <Hew> thank you for providing the fixes!
[17:48] <MrKanister> Hew: I see. The important restriction is "You may not copy the  Software into any public network." I will close the bug with an informal comment
[17:49] <Hew> MrKanister: Yes, that sentence sums it up nicely :-)
[17:52] <MrKanister> Hew: Done
[17:53] <Hew> MrKanister: Perfect, thanks for that.
[17:55] <MrKanister> Hew: Thank you for your patience
[17:55] <pckchem> lp acting funny for others or is it just me. On edge here.
[17:55] <Hew> MrKanister: Thank you for your help triaging!
[17:56] <Hew> pckchem: edge has serious problems atm, disable redirection at https://launchpad.net/ (and in 2 hours, and 4 hours..)
[17:56] <pckchem> Thanks Hew
[17:57] <pckchem> Is it just me or are some font's looking a bit funny, even on production?
[17:58] <Hew> pckchem: I haven't noticed any font problems.
[17:59] <Hew> Standard Launchpad should be fine. If you need help you can ask the guys in #launchpad
[18:00] <pckchem> *shrug* its only on the frontpage, probably intentional I just haven't looked at the page in eons.
[18:01] <Hew> hehe
[18:23] <Rocket2DMn> does anybody think that bug 310122 might qualify for SRU?
[21:29] <MrKanister> Can sombody set bug #206095 to "wishlist"? Thanks in advance
[21:34] <crimsun> MrKanister: done
[21:34] <MrKanister> crimsun: Thank you
[21:35] <crimsun> no, thank you =)
[21:38] <MrKanister> crimsun: Can you now set it to triaged :)
[21:47] <Ryan52> MrKanister, done
[21:47] <MrKanister> Ryan52: Thanks
[23:40] <duanedesign> could someone please set the status of Bug #309953 to 'Wishlist' Thank you
[23:40] <nhandler> Done duanedesign
[23:41] <duanedesign> could someone please set the status of Bug #309953 to 'Wishlist' Thank you
[23:41] <nhandler> I already did duanedesign ;)
[23:49] <duanedesign> thank you for the prompt reply to the 'wishlist' request
[23:49] <nhandler> duanedesign: You're welcome. I'm pretty bored, so you gave me something to do ;)
[23:50] <duanedesign> I have to get my five for today so maybe I will find another:)
[23:54]  * WelshDragon test
[23:55]  * WelshDragon asd
[23:55] <duanedesign> could someone please set the status of Bug #308823 to 'Wishlist' Thank you


[06:31] <kroot> Hello. Is anyone around that can help with translation import queues?
[06:34] <wgrant> kroot: Hi.
[07:18] <kroot> wgrant: Hello.
[07:19] <wgrant> kroot: You are having a problem with translation imports?
[07:21] <kroot> Well, I tried uploading it in the same directory layout it exported in... however, I see that is not the recommended layout for imports.
[07:22] <kroot> I just reuploaded it in the recommended format: https://translations.launchpad.net/connectbot/trunk/+imports
[07:24] <wgrant> henninge: Could you help kroot with his import layout?
[07:54] <henninge> wgrant: sorry, what was the request? I saw your ping but had to go off immediately.
[08:05] <henninge> also, I don't have any scroll-back
[08:05] <kroot> henninge: I was just having a bit of trouble making sure this translations import was in the right format for rosetta
[08:05] <kroot> https://translations.launchpad.net/connectbot/trunk/+imports
[08:05] <henninge> kroot: the new ones are good. I approved the template (it needed that because its path changed).
[08:05] <henninge> kroot: the translations should be approved automatically soon and then imported.
[08:45] <kroot> henninge: great, thanks
[08:47] <wgrant> win 55
[08:49] <kroot> Either that's a mistyped IRC command or you're keeping a score of how many people you help.
[08:54] <wgrant> kroot: It was, regrettably, merely missing a leading slash.
[09:25] <raphink> hello
[09:26] <raphink> I want to upload to a specific PPA, so I used dput ppa:raphink/augeas, but my package ended up on my main PPA
[09:26] <raphink> the uploading machine is running Lucid
[09:26] <raphink> and the raphink/augeas PPA exists
[09:32] <raphink> am I missing something?
[09:35] <wgrant> 2011-02-22 15:25:30 DEBUG   Considering changefile ~raphink/ubuntu/augeas_0.7.4-0ubuntu4~pparaphink1_source.changes
[09:35] <wgrant> dput uploaded straight into ~raphink, not ~raphink/augeas.
[09:35] <wgrant> Do you have a custom 'ppa' stanza in ~/.dput.cf, perhaps?
[10:00] <raphink> wgrant, let me check
[10:00] <raphink> ah right wgrant , I have a [ppa] entry in .dput.cf :-)
[10:01] <raphink> let me try again :-)
[10:01] <raphink> thanks for the debug
[10:20] <leoquant> The server encountered an internal error or misconfiguration and was unable to complete your request.
[10:20] <leoquant> https://wiki.ubuntu.com/BeginnersTeam/TeamReports
[10:20] <cdbs> that isn't a part of Launchpad
[10:21] <cdbs> leoquant: and, 500 errors are common in the wiki
[10:21] <leoquant> cdbs, ok
[10:21] <cdbs> leoquant: wait for 5-10 minutes, probably there is heavy load
[10:22] <cdbs> :o
[12:31] <lundh> Hi
[12:34] <lundh> I know that launchpad primarily is a hosted solution but I'm looking into the possibility to run it as a local install because of secrecy conserns. (We can not let a third party provider have a copy of our development documentation, no matter of how convenient it would be.) Is this being done? What should I keep in mind?
[12:39] <lundh> Registry and Bugs is the important parts that we would use. The code hosting is not really of any use to us (for now)
[13:03] <jml> lundh: in a nutshell, it's possible, but really difficult, and it's a use-case that's not supported by the Launchpad team.
[13:24] <lundh> jml: ok, so your recommendation is to look for another tool=
[13:25] <jml> lundh: or, if possible, re-evaluate your requirements. Launchpad does host private projects.
[13:27] <mikhas> (asked on wrong channel before) Hi, when using launchpad PPA's, can I somehow configure on the website that a package is made available for Lucid *and* Maverick? Or do I really have to re-upload the package, even if only the debian changelog changes?
[14:15] <bigjools> mikhas: you have 2 options. 1) re-upload as you have done, 2) upload to one of the series and use the PPA's copy-packages page to copy across to the other series
[14:23] <mikhas> oy, of course! that's what the combo box with the copying option is for, I guess
[14:23] <mikhas> I feel stupid now
[14:23] <mikhas> do I need to choose rebuild?
[14:46] <bigjools> mikhas: no, it will refuse that if you do
[14:53] <bigon> hi, is there any issue with the ppa's? looks like new packages on https://launchpad.net/~gnome3-team/+archive/gnome3/+packages are not published
[14:55] <hannie> Try reloading this page in a minute or two. This problem persists.
[14:56] <hannie> Can it be that more people are working on this translation at the moment?
[14:56] <bigjools> bigon: I can't see anything pending publishing
[14:56] <bigon> indeed
[14:56] <bigon> but
[14:56] <bigon>      2.90.0-1ubuntu1~build1 0
[14:56] <bigon>         450 http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ natty/main amd64 Packages
[14:57] <bigon> and in the ppa it's version ~build4
[14:57] <bigon> (pkg nautilus-sendto)
[14:58] <bigjools> bigon: no it isn't
[15:03] <bigon> mhhh the binary package has been removed from the source pkg
[15:03] <bigon> sigh
[15:05] <bigjools> bigon: it could be orphan cruft?
[15:06] <bigon> bigjools: indeed, I will readd the pkg
[15:16] <bigon> even worse, I'm stupid, sorry for the noise
[15:37] <hannie> Can anyone help me with this message on LP: Sorry, there was a problem connecting to the Launchpad server.
[15:37] <hannie> Please try again. This doesn't help
[15:38] <hannie> It only occurs with the LoCo Directory translation. All other packages are ok
[15:38] <jcsackett> hannie: what url are you trying to open?
[15:39] <jcsackett> or are you accessing via another means?
[15:39] <hannie> wait a sec
[15:39] <hannie> https://translations.launchpad.net/loco-directory/trunk/+pots/loco-directory/nl/
[15:40] <hannie> I have closed and reopened it, but to no avail
[15:42] <jcsackett> hannie: one sec.
[15:43] <hannie> ok
[15:46] <jcsackett> hannie: i can reproduce; it opens here. can you open translations.launchpad.net alright?
[15:46] <jcsackett> sorry, i *cannot* reproduce.
[15:46] <hannie> I cannot save
[15:47] <jcsackett> hannie: ah. i see. can you run me through exactly what you are doing/trying to do?
[15:47] <hannie> ok
[15:47] <hannie> I changed some strings. When I try to save I get this message
[15:48] <hannie> jcsackett, it started about 30 minutes ago and still doesn't want to save
[15:49] <hannie> Try reloading this page in a minute or two. If the problem persists, let us know in the #launchpad IRC channel on Freenode.
[15:49] <jcsackett> hannie: i see. okay, i am investigating.
[15:50] <hannie> thanks a lot. Please let me know when it is fixed.
[15:50] <jcsackett> hannie: will do. i may have to ask you further questions, or someone else may get pulled into this and ask you some questions as well. :-)
[15:51] <hannie> I can save the gcalctool messages on which I am working too
[15:51] <hannie> I'll hang around
[15:52] <RawChid> I think it's hard to reproduce since hannie had changed a bunch of strings and hit "save".
[15:52] <RawChid> Now she's refreshing in the hope it will actually save (am I right hannie ?)
[15:53] <hannie> I tried several times, but with the same result
[15:53] <RawChid> Did you re-enter the changes?
[15:53] <RawChid> Or back button of browser, and hit "save" again?
[15:53] <hannie> Yes, I test it with one string
[15:53] <RawChid> Ok :)
[15:54] <hannie> Even closed and opened and tried again
[15:54] <jcsackett> hannie: ok, i was just about to ask if you could try with just one string. thanks for clarifying. :-)
[15:54] <hannie> jcsackett, do you want me to close the page?
[15:55] <jcsackett> hannie: you have already completely closed the page and reopened it to try one string, yes?
[15:55] <hannie> yes, I did
[15:56] <hannie> I'll do it once more
[15:56] <jcsackett> hannie: if you want, sure. but i don't think it's necessary.
[15:57] <hannie> Just to be sure
[15:58] <hannie> same error message after closing, reopening, changing and saving
[16:03] <jcsackett> hannie: you said this started about 30 minutes ago; were you able to make changes before that today?
[16:04] <hannie> not today, but yesterday
[16:04] <jcsackett> hannie: ok.
[16:08] <RawChid> When changing this string: https://translations.launchpad.net/loco-directory/trunk/+pots/loco-directory/nl/24/+translate
[16:08] <RawChid> I get the same error as hannie
[16:09] <jcsackett> RawChid, hannie: are either of you getting OOPS numbers when you get the error message?
[16:09] <RawChid> No, nothing
[16:10] <hannie> No, just the text I sent you
[16:10] <RawChid> Here is a screenie: http://picpaste.com/LP-error-is1fngV1.png
[16:11] <hannie> jcsacket: one change was saved (it says 21 seconds ago)
[16:14] <jtv> RawChid, hannie, jcsackett: that doesn't even look translations-related… it's a more basic problem
[16:14] <hannie> It is "save"-related
[16:15]  * jtv asks around in another channel
[16:19] <jtv> hannie, RawChid: the screenshot and URL were very helpful—got someone looking at it now.
[16:19] <hannie> ok, thanks I will leave it to you guys.
[16:22] <RawChid> Good luck!
[16:22] <RawChid> Thanks for helping us out
[16:24] <jtv> RawChid, hannie: thanks for reporting this so carefully, and sorry for the inconvenience.  I'll try to keep you posted, though my shift is ending soon and I may be called away.
[16:24] <hannie> Ok, we'll see tomorrow
[16:27] <RawChid> I'll stick here in this channel
[16:32] <jtv> Cool.
[16:39] <jtv> RawChid: looks like it may be a problem in a proxy on your end… any chance you and hannie are behind one and the same proxy?
[16:40] <RawChid> Don't think so
[16:40] <RawChid> We live in different cities
[16:41] <RawChid> I don't use a proxy. Or are you talking about proxies inside the Launchpad infrastructure...
[16:42] <jtv> It's pretty unclear at the moment, so it was a bit of a guess.
[16:42] <RawChid> FYI, the problem still occurs on that URL I gave earlier
[16:43] <jtv> Oh, that's good to know—I'm passing that on
[16:43] <jtv> (People we wondering :)
[16:56] <jtv> RawChid: investigations are ongoing.  jcsackett is in a better timezone, so he will keep working on it with the admins.
[16:56] <jtv> (where "better" is "more suitable just now," of course :)
[16:57] <jcsackett> best would be a timezone where lunch isn't about to roll around. :-)
[16:57] <RawChid> Hehe, I'll cook diner in about 20 minutes :P
[16:57] <jtv> eet smakelijk dan :)
[16:58] <RawChid> Ah, ook Nederlands, dankjewel. En jij ook straks
[18:27] <till_> almost each time i dput to launchpad i get an ftp error, is that expected?
[18:27] <till_> the "stacktrace" says that the upload was successful
[18:27] <till_> but there was an error closing the connection
[18:27] <till_> the build is started too, it's just a weird error
[18:27] <till_> anyone have any thoughts?
[18:28] <RawChid> I'm just sitting here. But I think it may help if you pastebin the stacktrace
[18:28] <till_> http://friendpaste.com/3GWcB1xf4FUMG7HAx3Zncx
[18:28] <till_> RawChid: good idea ;)
[19:09] <falktx> hey there
[19:09] <falktx> i'm having lots of issues building packages on natty
[19:09] <falktx> afaik, natty has a kinda broken GCC
[19:10] <falktx> how do I force a package to build with an old GCC version?
[19:14] <sinzui> falktx: I do not think you can
[19:14] <falktx> oh, crap
[19:17] <falktx> how am I suppose to fix:
[19:17] <falktx> 'undefined reference to `sigc::signal_base::signal_base()'' ?
[19:17] <falktx> and lots of other errors like these
[19:17] <lifeless> I'd discuss that on #ubuntu-motu
[19:18] <lifeless> who are much more likely to be aware of compilation issues
[19:18] <falktx> lifeless: thanks, I didnt know which was the right channel for this
[19:39] <RedSingularity> Hey everyone!  Anybody available?
[19:41] <chmod755> yup
[19:42] <RedSingularity> I am having an issue turning bugs into questions.  Experienced this a few months ago but it is acting up again.  Maybe someone can look into it?  I will remain in the channel here.
[19:42] <micahg> RedSingularity: that's a known issue
[19:42] <RedSingularity> micahg: ahhh any workaround man?
[19:43] <micahg> RedSingularity: not that I know of
[19:43] <RedSingularity> micahg: just cant use questions for now then?
[19:43] <lifeless> you can make a new question
[19:43] <lifeless> then link the bug to the question
[19:43] <sinzui> RedSingularity: the action timesout?
[19:43] <RedSingularity> sinzui: yep
[19:44] <sinzui> lifeless: you cannot subscribe the bug reporter to the question. You will be the asker and you do not care about solving the issue
[19:45] <RedSingularity> Alright, guess i will create a new question or have the user do it.
[19:45] <lifeless> ah
[19:45] <lifeless> have the user do it
[19:45] <RedSingularity> Any idea how long before a fix?
[19:45] <RedSingularity> lifeless: alright
[19:45] <lifeless> RedSingularity: its in our critical bug list
[19:45] <lifeless> but there are 200 bugs in that list
[19:46] <sinzui> RedSingularity: Question side of the conversion rules are really stupid (/me wrote them) The bug description and the explanation of why it is q question is all that should be converted. The answer contactions should get one email, not one for each comment
[19:46] <RedSingularity> lifeless: 200 bugs filed against launchpad?!?
[19:46] <lifeless> RedSingularity: critical ones
[19:46] <lifeless> RedSingularity: we have 6000 bugs open
[19:46] <RedSingularity> lifeless: WOW
[19:47] <lifeless> https://launchpad.net/launchpad-project
[19:47] <RedSingularity> sinzui: i agree yes
[19:48] <sinzui> RedSingularity: I certainly want to fix this issue. There is 25% I can get this done in the next 4 weeks
[19:48] <RedSingularity> lifeless: so no eta on a fix yet i assume?
[19:48] <lifeless> RedSingularity: nope
[19:48] <lifeless> RedSingularity: its important to us
[19:48] <lifeless> RedSingularity: but we have other equally broken pages
[19:48] <sinzui> RedSingularity: there is a good chance. the convert question bug is a leading timeout. It is in the queue of critical
[19:51] <RedSingularity> sinzui lifeless Thanks for the info!  Just wanted to know whats going on ;)
[19:55] <lundh> hi again
[19:55] <lundh> I asked this a couple of hours ago but had to run so sorry for repeating myself
[19:56] <lundh> I am trying to figure out if launchpad is a viable solution as an internal issue tracking system. We can not have a hosted solution due to secrecy conserns but launchpad fit our need pretty good (private projects as well as (semi)public ones)
[19:57] <lundh> launchpads feature list is miles ahead of redmine or bugzilla as we would use it
[19:57] <jcsackett> lundh: you were asking earlier about internal hosting of launchpad, right?
[19:57] <lundh> yes
[19:57] <sinzui> lundh: This is not that channel to ask about hacking Lp to run internally or other hosting
[19:58] <lundh> which is?
[19:58] <lifeless> #launchpad-dev would be better
[19:58] <sinzui> lundh: We released Lps code to encourage users to contribute to the Lp service
[19:59] <lundh> I'm just trying to figure out what to do as there is no way that our project could be hosted even though that would be very nice
[19:59] <sinzui> Lp requires hacking to be used for anything other that lp.net development. The art is not free. We do not discuss how Lp is setup in prodution
[20:00] <lifeless> lundh: https://dev.launchpad.net/Running/VirtualMachine is a reasonable starting point
[20:00] <lundh> ok, that probably makes it unsuited for our needs, thanks for letting me know :)
[20:00] <lundh> too bad though, the feature list is really nice
[20:00] <lifeless> lundh: its certainly doable, but you'll need to put a reasonable amount of effort in - starting with a rebranding
[20:00] <sinzui> lundh: Companies like dell use Lp. I suspect  have more money at stake than your company
[20:01] <sinzui> s/suspect have/suspect dell has/
[20:01] <lundh> sinzui: money is not the issue, trust is and that is everything for this. no third party is ever allowed in
[20:02] <lifeless> lundh: there are other folk running internal lp instances around
[20:02] <sinzui> lundh: What issues block your company from using Lp.net? If we do not know what they are, Lp has little chance of ever serving your needs.
[20:02] <lifeless> lundh: I'm not aware of anyone running a publically accessible lp instance other than us
[20:03] <lundh> sinzui: The only way we could use lp.net would be to buy a server with it preinstalled and then having it on site at our location. thats the issue
[20:03] <lundh> lifeless: I'm not talking about publically avilable instances. this instance would be accessible by a handful of ips with passwords and encryption
[20:04] <lifeless> sinzui: some organisations have a 'no hosted solutions' policy
[20:04] <lifeless> lundh: you can certainly do that
[20:04] <lifeless> lundh: we'd be delighted if you contributed patches back that make it better for you
[20:06] <lundh> I'll look into it then. might be more then we can cope with though.
[20:07] <lundh> but if you would sell a server with launchpad pre installed (seald or whatever) I'm sure that would be attractive to several companies with similar policies
[20:24] <lifeless> lundh: its an interesting idea
[20:24] <lifeless> lundh: however our current focus is improving our quality and scaling to deal with users coming in from the internet
[20:27] <lundh> I can understand that
[21:31] <JFo> in attempting to accept the nominations on bug 723945 I am encountering a seemingly quick timeout. Anything I can do to avoid this?
[22:18] <wgrant> JFo: Do you have an OOPS ID for that timeout?
[22:19] <JFo> wgrant, Error ID: OOPS-1880K1665
[22:19] <wgrant> JFo: Thanks.
[22:19] <JFo> np :)
[22:41] <lifeless> zomg
[22:42] <lifeless> wgrant: jfo's oops - the ss query in it makes me want to stab my eyeballs
[22:43] <wgrant> lifeless: Would you like some DSP queries?
[22:43] <lifeless> they are nicer
[22:43] <wgrant> Not the ones during heat calculation.
[22:43] <lifeless> actually
[22:43] <lifeless> they are
[22:43] <lifeless> the ss ones are *4* pages long
[23:29] <pindonga> hi, I was wondering if it's possible to use launchpadlib to retrieve a list of bugs that have a specific tag (I don't find this in the api docs)
[23:31] <JFo> lifeless, sorry about that :-)
[23:32] <lifeless> JFo: hmm ?
[23:32] <thumper> pindonga: Possibly, but I'm not sure how
[23:32] <JFo> about the Oops ss query :)
[23:32] <lifeless> pindonga: yes, searchTasks(tag='foo')
[23:32] <lifeless> JFo: not your fault
[23:32] <pindonga> lifeless, that on lp.bugs?
[23:32] <lifeless> pindonga: on any bug context
[23:32] <pindonga> lifeless, cool, thanks