[02:03] <maxb> TheMuso: ok, will do - thanks
[07:31] <ebroder> The mit-scheme package is currently complete broken - uninstallable. Do I have a chance of getting a freeze exception to essentially re-merge with Debian?
[07:32] <ebroder> (Actually coming up with something like a minimal path would be more work than I'm interested in doing, but I think I mostly have the merge finished)
[07:37] <Hobbsee> quite likely
[07:38] <Hobbsee> is that even a new upstream version?  You could probably just do it, without the exception
[07:38] <ebroder> It's...not technically an upstream version, but it seems that the "releases" for a while have just been dated snapshots
[07:40] <ebroder> Cool - I have one more build to try. If it works I'll go ahead and open a bug
[07:47] <ebroder> Hmm...if I'm putting multiple LP closers in a changelog entry, is that "(LP: #123456, #654321)"?
[07:48] <Mithrandir> iirc we made that work, yes.
[17:04] <bluefoxicy> rhythmbox is eating freaking lots of CPU
[17:04] <bluefoxicy> 87% to play this MP3
[17:13] <xtknight> what configuration file is written to when the primary mixer track is changed under Sound Preferences?
[17:13] <xtknight> i'm having a problem where my system forgets the device i select upon next reboot.  trying to debug it
[17:27] <xtknight> also where is the sound preferences applet stored since there is no capplets/sound-properties in capplets-data
[18:34] <calc> cjwatson: i was reading on tytso blog that for non dual boot systems that are being freshly installed using GPT may be a better idea than using msdos partition format, has there been any discussion on doing this in ubuntu?
[18:34] <ITechJunkie> Does anyone here know why my terminals don't seem to be refreshing right? I have to press enter twice just to see the text output of the next line...
[18:34] <RainCT> ITechJunkie: Same here, please tell me if you find out how to fix it :P
[18:35] <ITechJunkie> gnome-terminal is the worst, xterm isn't quite as bad
[18:35] <RainCT> Well, it only happens some times here with irssi and such, not always
[18:35] <ITechJunkie> RainCT: I'm wondering if it was an update...
[18:35] <ITechJunkie> Yeah, i'm using irssi now and it's being janky...
[18:36] <RainCT> ITechJunkie: as a workaround, pressing Ctrl+L will force it to refresh and after doing that a few times it may work again
[18:36] <ITechJunkie> is that for irssi or gnome-term?
[18:37] <RainCT> ITechJunkie: for the terminal, I think
[18:37] <ITechJunkie> Is there a log where I can see the updates I have installed recently?
[18:38] <Laney> :q
[18:38] <Laney> whoops
[18:39] <geser> ITechJunkie: /var/log/dpkg.log
[18:40] <ITechJunkie> geser: thanks
[18:41] <ITechJunkie> I really hope it wasn't that kernel update that came out...
[18:42] <ITechJunkie> but I bet it was, i've had several problems since then including nvidia drivers
[18:53] <zyga> hello, I'd like to ask if pydoc3 is broken by design or is something invalid with py3 in jaunty? compare: 'pydoc os' vs 'pydoc3 os'?
[18:57] <ebroder> Do I need to argue for a freeze exception for bug #339618?
[19:03] <RainCT> kirkland: Uhm.. Where did the key binding to close windows in screen-profiles go?
[19:09] <JanC> zyga: there is a thread on c.l.py about that, I think
[19:58] <Laney> Is it possible to sync from lenny instead of sid or am I better off just uploading myself?
[19:58] <slangasek> it's possible, yes
[20:03] <slangasek> ArneGoetje: can you help me understand why we have -base vs. non-base langpacks?  the latest langpack uploads with duplication of the xulrunner translations have contributed to kicking us back oversize on CDs - I'd like to keep the CDs packed as tight as possible during development so we have early warning when something's getting bigger than it should, but that doesn't work so well when I get a full langpack's-worth of fluctuation from the langpack
[20:03] <slangasek> ... themselves :)
[20:21] <johanbr> tkamppeter: I recently tried printing 40 pages out of a 350 page pdf document with total size 4.5 megs. Those 40 pages were run through gs to produce a 100 meg ps file. Cups then converted this to pdf again to mess with it for a bit, giving a 166 meg temporary pdf file. Finally this was piped to pdf2ps to send to the printer.
[20:21] <johanbr> Is this really the way things are supposed to work? This is with Jaunty, by the way.
[20:36] <tkamppeter> johanbr, the plans are that no PostScript at all is involved in that process.
[20:37] <tkamppeter> The first conversion to PS is probably caused by the application from which you are printing. Which app did you use?
[20:38] <johanbr> evince
[20:38] <johanbr> which uses the gtk printing libraries
[20:40] <tkamppeter> CUPS is PDF-centric from Intrepid on. This means it turns everything to PDF and if it gets PDF it leaves it as PDF. Then it does page management (N-up, selecting pages, ...) on a PDF data stream which is more reliable than on PS. Now it converts PDF directly to the printer's native language (the native language of some printers is PostScript, here we have to convert to PS).
[20:41] <slangasek> but no one told our primary pdf viewing software about this?
[20:42] <tkamppeter> If your printer is not a PostScript printer make sure that you have a PPD file of Intrepid or later (with two or more "cupsFilter" lines), if not, re-create your print queue with system-config-printer.
[20:44] <johanbr> It is a postscript printer (HP Laserjet). And the print queue was created on a fresh install with a Jaunty daily build from a month or so ago.
[20:46] <tkamppeter> GTK has standard functionality for generating print data, opening a print dialog, ..., but unfortunately there are many ways to call these functions, and this makes a simple patch like in bug #258421 bot switching all apps to PDF. Some apps need to be taken care of individually. Patches welcome ...
[20:47] <johanbr> from bug: "Other programs, like evince and Firefox still send PostScript. Here there are probably similar patches needed in the applications themselves."
[20:48] <johanbr> I see. Thanks for the explanation.
[20:48] <tkamppeter> slangasek, perhaps the patch needed for evince is as simple as the patch of bug 258421.
[20:50] <calc> anyone able to spot what is wrong with my compiler args here: http://paste.ubuntu.com/128477/  ?
[20:51] <slangasek> tkamppeter: I just don't understand why it wasn't a priority to make sure the PDF viewer was doing the right thing as part of the cups transition...
[20:52] <calc> it compiles the code it just refuses to link it for some reason
[21:01] <johanbr> tkamppeter: looks like a simple patch to line 1016 of ev-print-operation.c would work.
[21:02] <johanbr> http://svn.gnome.org/viewvc/evince/trunk/shell/ev-print-operation.c?view=markup
[21:12] <RainCT> Arr.. If you move a file which Totem is playing it stops.. This didn't happen before :(
[21:13] <tkamppeter> johanbr, so I will add an evince task to bug 258421, please add the link to the bug report.
[21:14] <johanbr> tkamppeter: Sure. I'm now compiling evince with the change I mentioned. If it works, I'll attach the patch.
[21:17] <tkamppeter> johanbr, it looks like that the line 1016 gets the desired output format (PS or PDF) from some centralized configuration. Perhaps we should change this configurationm to get more apps to print in PDF.
[21:23] <TheMuso> dtchen: Will we be able to push a new rev of pulseaudio before Tuesday?
[21:25] <johanbr> tkamppeter: Right. Looking at that now.
[21:43] <UnixOne> hi
[21:43] <UnixOne> I've had some problems with the package comerr-dev. Kind of dependancy problems.
[21:43] <UnixOne> Is that a known error?
[21:43] <ebroder> What exactly are you running into?
[21:45] <UnixOne> ebroder: I tried compiling the latest kernel that requires installation of several -dev packages. which was never a problem for me. But my apt got stuck with the package comerr-dev which has some dependancies that were defect also because of it.
[21:45] <UnixOne> ebroder: It's a clean system no foreign repositories except the backports.
[21:45] <ebroder> You're still not being specific enough
[21:46] <UnixOne> ebroder: the un/install routine of comerr-dev is defect
[21:47] <ebroder> What version of Ubuntu is this on?
[21:48] <UnixOne> Intrepid
[21:49] <jdong> could you pastebin the exact error message?
[21:49] <UnixOne> only checking the backports maybe even the proposed updates. causes that huge error.
[21:49] <UnixOne> jdong: I've manuall uninstalled it by hand.. I don't like to run into that trouble again.
[21:49] <jdong> well then the short answer is no, this is not a known problem.
[21:50] <UnixOne> jdong_: I removed the installed files and reset the status of dpkg
[21:50] <ebroder> The group that I work with uses a lot of software that depends on comerr, and we haven't had any problems with it
[21:50] <jdong> *cringe*
[21:50] <jdong> you hand edited *WHAT*?
[21:50] <ebroder> (Well, I mean, we have, but those are related to comerr being worthless, not the packaging being wrong :-P)
[21:50] <UnixOne> ebroder: did you enable backporst and proposed updates?
[21:50] <jdong> I use both here on all my Ubuntu machines.
[21:51] <UnixOne> jdong: are you running kubuntu?
[21:51] <ebroder> I use -backports on virtually all of my machines, although not -proposed
[21:51] <ebroder> Shouldn't matter
[21:51] <jdong> backports doesn't do anything related to comerr
[21:51] <UnixOne> maybe proposed-updates is the key factor
[21:51] <jdong> and kubuntu vs ubuntu use the same repositories.
[21:51] <UnixOne> jdong_: indeed
[21:51] <jdong> I'm looking at this month's and last month's propsoed uploads
[21:51] <jdong> see nothing comerr related.
[21:52] <jdong> next time, please capture a precise error message -- without it diagnosing something like this is next to impossible
[21:52] <UnixOne> jdong how can I find the cause of that error?
[21:52] <ebroder> That's impossible to say without knowing what the error was
[21:52] <UnixOne> I mean how do I reversely look into that dependancy problem
[21:53] <jdong> I don't even know what error you are referring to.
[21:53] <ebroder> There is no dependency problem. The package installs cleanly
[21:53] <UnixOne> ebroder: ok, I'll install it again
[21:53] <jdong> and "some package has a defect" is not really helpful
[21:55]  * jdong notes there is some irony about errors in libcomerr :)
[21:55] <ebroder> You know what the best thing about the common error library is? There are so damn many of them
[21:56] <UnixOne> jdong: a question before I do install it. may it affect the system when I used backports+proposed to upgrade my system, when I remove proposed now?
[21:56] <jdong> not really?
[21:56] <UnixOne> k
[21:56] <slangasek> ebroder: only one in Ubuntu :-P
[21:56] <ebroder> slangasek: Incorrect
[21:56] <UnixOne> I'll uncheck proposed updates then
[21:57] <ebroder> AFS ships its own com_err :)
[21:57] <slangasek> eh, really?
[21:57] <jdong> well AFS is weird in all its own ways :)
[21:57] <slangasek> krb5 uses the common one
[21:57] <ebroder> Right
[21:58] <slangasek> I would've thought someone would send up the AFS stuff by now
[21:58] <ebroder> There's a lot of muttering about how someone really should, but I don't think anyone's actually gone and unified the libraries
[21:58] <ebroder> Actually...I bet Heimdal has a separate com_err from MIT Kerberos
[21:58] <ebroder> So that might be 3
[21:58] <slangasek> heimdal may not use it at all
[21:58] <UnixOne> comerr-dev is an error for me :P but it's installing.. will pastebin the logs
[21:59] <jdong> libopenafs-dev: /usr/include/afs/com_err.h
[21:59] <jdong> AFS definitely has its own :)
[21:59] <UnixOne> yay I've an errror with comerr
[21:59] <jdong> so we've heard the first time
[21:59] <ebroder> Yeah - the default API calls have afs_ prepended onto them, but there's a #define you can set to make it collide
[22:02] <UnixOne> ehrm how do I copy the log out of the terminal window in synpatic? STRG+C or STRG+SHIFT+C don't do it. Synaptic asks I really want to terminate. I say no. And I can't copy it.
[22:02] <UnixOne> but I was able to copy the popup that appeared before
[22:02] <jdong> ctrl-shift-c will do it
[22:03] <jdong> otherwise use mouse paste
[22:03] <jdong> or use a screenshot
[22:03] <jdong> I think /var/log/apt/term.log or something stores transcripts too
[22:06] <UnixOne> jdong: yes, I got it. It was related to klipper a clipboard tool default in kubuntu. It just gave me the earlier content of the clipboard. I deleted the clipboard history have done another ctrl+shift+c and voila.
[22:07] <UnixOne> short version(popup) http://paste.nn-d.de/839 very very long version -> (terminal) http://paste.nn-d.de/840
[22:08] <ebroder> Well, English is definitely my only language, but I'm pretty sure that the problem is with gettext, not comerr-dev
[22:09] <slangasek> both give the error
[22:09] <ebroder> Hmm...good point
[22:09] <UnixOne> I tried installing THIS http://paste.nn-d.de/841 in short build-essential kernel-package qt4-dev-tools libqt4-dev
[22:09] <slangasek> 'subprocess post-installation script returned 1'
[22:09] <jdong> well yay.
[22:10] <slangasek> UnixOne: 'info' is broken on your system
[22:10] <UnixOne> info ?
[22:10] <UnixOne> :D
[22:10] <UnixOne> lol
[22:10] <slangasek> specifically, the install-info script provided by dpkg to register info documentation
[22:10] <UnixOne> first the error was broken, now it's info
[22:10] <jdong> install-info --quiet --section "Development" "Development" \ --description="" /usr/share/info/gettext.info
[22:10] <jdong> that is what gettext attempts to do
[22:10] <slangasek> it's failing in the postinsts of any program that calls it
[22:11] <ajmitch> but which install-info is being used here?
[22:11] <UnixOne> I there's a part that needs translation or is important I could translate it
[22:13] <UnixOne> it is  info_4.11.dfsg.1-4_i386
[22:13] <UnixOne> the default one I guess
[22:13] <slangasek> UnixOne: what's the output of 'debsums -s dpkg' on your system?
[22:14]  * ajmitch was meaning more along the lines of 'whereis install-info', in case you have one in /usr/local/bin or otherwise
[22:14] <UnixOne> that package isn't installed currently
[22:15] <UnixOne> slangasek: debsums: checksum mismatch dpkg file /sbin/start-stop-daemon
[22:15] <slangasek> well, that's interesting
[22:15] <slangasek> but not directly relevant
[22:15] <UnixOne> yes, has nothing to with comerr-dev.. somehow. strange
[22:16] <slangasek> UnixOne: does /usr/local/bin/install-info exist, as ajmitch suggests?
[22:16] <jdong> which install-info
[22:16] <UnixOne> slangasek jdong yes /usr/local/bin/install-info
[22:16] <slangasek> yeah... you'll need to get rid of that
[22:17] <jdong> uhh.
[22:17] <jdong> yeah...
[22:17] <jdong> that could be problem #1...
[22:17] <jdong> though maybe dpkg shouldn't be operating with /usr/local in the PATH?
[22:17] <jdong> or is there actually a use-case for that
[22:17] <slangasek> jdong: the general principle is that dpkg shouldn't behave differently than the rest of the system wrt PATH
[22:18]  * jdong nods
[22:18] <ebroder> I could imagine wanting it for testing purposes
[22:18] <jdong> indeed the rest of the system is no different about succumbing to /usr/local poison
[22:19] <ScottK-desktop> That's by design.
[22:20] <ebroder> If the system didn't respect /usr/local, then you'd have people putting a bunch of stuff in /usr, and that just doesn't end well
[22:20] <ScottK-desktop> If an admin installs something, it should take precendence because presumably they know what they are doing.
[22:35] <andersk> python3-minimal is currently getting pulled into all Jaunty installs. Can someone look at my debdiff in bug 330613?
[22:40] <UnixOne> ebroder jdong can you help me?
[22:43] <UnixOne> I've sent you all logs. do you know what I can do to fix that error?
[22:46] <ebroder> UnixOne: remove the install-info in /usr/local
[22:48] <UnixOne> ebroder: sudo mv /usr/local/bin/install-info  /usr/local/bin/install-info.backup ?
[22:48] <ebroder> Sure
[22:48] <UnixOne> ok
[22:48] <UnixOne> and then reinstall those packages, right?
[22:48] <ebroder> Should work
[22:48] <UnixOne> ok
[22:48] <ebroder> If you've got anything else lying around in /usr/local/bin or /usr/local/sbin, you should think long and hard about whether they should be there
[22:49] <UnixOne> ebroder: why? I've just texlive2008 installed
[22:49] <UnixOne> in the default location
[22:50] <UnixOne> that's /usr/local/bin
[22:52] <UnixOne> ebroder: it worked wow
[22:52] <UnixOne> genius!
[22:54] <TheMuso> dtchen: With the work you are doing on pulse, will things be in a state such that we can push a change for alpha 6, due this week?
[22:54] <UnixOne> ebroder: why did install-info in /usr/local cause an error?
[23:09] <dtchen> TheMuso: yes
[23:09] <TheMuso> dtchen: ok great.
[23:10] <ebroder> Anyone willing to sponsor an upload for bug #339449?
[23:15] <rbrito> Hi there.
[23:15] <rbrito> I am an experienced linux user and I would like to help with the PowerPC port of Ubuntu.
[23:16] <rbrito> I have 5 packages on the Debian archive and I use PowerPC since 2000.
[23:16] <rbrito> I have also contributed some patches to the Linux kernel.
[23:17] <rbrito> What would it be necessary to be a contributor so that PowerPC gets in a better shape?
[23:22] <rbrito> For the task of helping with the PowerPC port, I can test it under an OldWorld computer (a PowerMac 9500/180MP upgraded to a G3/400MHz), a NewWorld computer (an iBook 12" G3 600MHz) and a Kurobox (an embedded device using a Freescale processor).
[23:22] <rbrito> Of course, the easier task would be to get things running with the NewWorld computers.
[23:23] <TheMuso> rbrito: please head over to #ubuntu-powerpc and we can chat there.
[23:23] <rbrito> But I would like to know how the ports of Ubuntu are maintained, so that I can take the proper measures.
[23:23] <rbrito> TheMuso, Thank you very much.
[23:25] <johanbr> tkamppeter: Forcing evince to export pdf doesn't seem to work very well. The pdftopdf filter runs out of memory on large documents, and on small ones I get black borders and similar artifacts.
[23:27] <tkamppeter> johanbr, can you direct the PDF printing output of evince into files to investigate the integrity, for example to see of acroread or gv handle this PDF correctly?
[23:27] <tkamppeter> johanbr, what is your Launchpad user name?
[23:36] <johanbr> tkamppeter: Sorry, I partially take that back. I think the small pdf document I started with was not very good.
[23:36] <johanbr> and I just subscribed myself to the bug
[23:37] <johanbr> For the "large" pdf document, pdftopdf grew to 1.6 gig resident size and the computer started swapping like crazy. Even though the original size is less than five megs.
[23:45] <johanbr> tkamppeter: Which options does cups use when it calls pdftopdf? I tried running it by hand, and it worked fine (even if the resulting pdf file is a bit large, about 100 megs).
[23:47] <tkamppeter> johanbr, can you attach the large PDF file which causes problems for you to the bug report?
[23:47] <tkamppeter> To test CUPS filter chains there is a utility named "cupsfilter". See also its man page.
[23:50]  * calc didn't realize he was going to end up learning how to write gnome code to fix bugs in OOo, heh
[23:50] <tkamppeter> In general a CUPS filter (or backend) is called with 5 or 6 options. See "man 7 filter".
[23:51]  * calc hopes he learns fast enough to fix the gvfs/gio bugs in OOo by beta
[23:54] <tkamppeter> johanbr, you can call CUPS filters simply with "<filter> 1 1 1 1 '' <input file>" and get the output file on stdout.
[23:55] <LaserJock> calc: OOo uses gcfs/gio directly?
[23:55] <LaserJock> *gvfs
[23:56] <johanbr> tkamppeter: Unfortunately I can't attach the document to the bug, but I could send it to you privately.
[23:57] <tkamppeter> johanbr, then please do so: till dot kamppeter at gmail dot com
[23:57] <johanbr> Interestingly enough, calling pdftopdf directly produces a large file (~ 100 megs), but calling cupsfilter produces a file of the same size as the original (~5 megs).
[23:58] <tkamppeter> johanbr, is the file too big to attach or is it of confidential content?
[23:59] <johanbr> The latter. Well, semi-confidential.


[00:57] <c_smith> hello
[00:57]  * c_smith is at Broadway Commons hoping someone shows up
[16:08]  * bkerensa gets ready to head down to PSU
[16:08] <bkerensa> slangasek: I'm bringing the bluetooth :)
[16:11] <blkperl> bkerensa: i need door minions
[16:11] <blkperl> unfortunately their locked
[16:20] <bkerensa> blkperl: what does that mean?
[16:21] <bkerensa> should I not come? :P
[16:23] <blkperl> bkerensa: no you should come, to help me
[16:23] <blkperl> :)
[16:24] <bkerensa> ok well just a FYI its going to talk be a half hour at best.... I am still gettined proper and will be heading out shortly
[16:24] <bkerensa> gotta bring some kind of swag ya know
[16:26] <blkperl> ok
[16:35] <kees> Room 86-01!
[16:35] <kees> on my way
[16:37] <blkperl> kees: theres a sign on the EB front door call that number and ill let you in :)
[16:40] <kees> blkperl: cool
[16:45] <blkperl> lame someone not going to Ubuntu day just used me to get in...
[16:46] <bkerensa> blkperl: tell them "Not cool man"
[16:46]  * bkerensa waits on bus to arrive
[16:47] <bkerensa> blkperl: you just missed the bagel request on mailing list :P
[16:47]  * blkperl really wishes the conference room had a phone <.<
[16:47] <bkerensa> speaking of it how far deep into the catacombs is this room?
[16:48] <blkperl> down the stairs and to the left
[16:48] <blkperl> whopper922: are you coming today
[17:12] <slangasek> bkerensa: ack; will bring mine as well for cross-product testing
[17:13] <slangasek> I'm running a bit late as you can see, but should be there in about a half hour I think
[17:23] <c_smith> hello
[17:28] <blkperl> c_smith: hi
[17:28] <c_smith> how goes it?
[17:30] <blkperl> good, you coming to ubuntu bug day?
[17:33] <c_smith> nope, don't have time to get down there, nor do I have a ride there.
[17:33] <c_smith> actually, I have time, but no ride.
[17:34] <c_smith> gotta love it when you don't have your day straight.... >.<
[17:53] <nathwill> https://wiki.ubuntu.com/UbuntuDevelopment/GettingSetUp
[17:53] <nathwill> https://wiki.ubuntu.com/Bugs/HowToFix
[17:53] <c_smith> nathwill, those are links I should have put in my bookmarks long before now.
[17:53] <nathwill> :D
[17:54] <nathwill> run through them in the same order
[17:54] <c_smith> bookmarking now.
[17:54] <nathwill> they're pretty useful
[17:54] <nathwill> holler if you hit problems
[17:54] <c_smith> eh, I have a bit going on now (ubuntu blew up, so I'm installing 32-bit instead of my usual 64-bit, my PC only has 3 GB of RAM, anyway)
[17:56] <c_smith> plus my C&C The FIrst Decade doesn't like 64-bit Wine.  but it runs fine on 32-bit Wine
[18:02] <blkperl> marut: hi
[18:02] <marut> hi all
[18:02] <c_smith> hello, marut
[18:03] <vagrantc> ah, this looks more promising
[18:03]  * kees waves "hi"
[18:03] <KorvinSzanto> Hi
[18:03] <kees> hola!
[18:03] <KorvinSzanto> Not able to make it until later
[18:03] <nathwill> gruesse!
[18:03] <jpiroshky> cheers!
[18:05] <houk__> hello?
[18:05] <KorvinSzanto> Hi
[18:05] <kees> hi!
[18:05] <amj> hi
[18:05] <houk__> Yay, no bubble !!!
[18:05] <kees> anyone wanting a build environment for the day, please email me<EMAIL_ADDRESS>and I'll send details
[18:06] <KorvinSzanto> I'm trying to grep for trailing spaces using [ \t]+$, how do I format that regex to work with grep?
[18:06] <slangasek> tngodup: welcome :)
[18:06] <kees> details on using environment: http://wiki.debian.org/BSP/2011/12/us/Portland/Builders
[18:06] <slangasek> http://wiki.debian.org/BSP/BeginnersHOWTO
[18:07] <tngodup> thanx
[18:12] <blkperl> spw2: hi
[18:12] <blkperl> spw2: http://wiki.debian.org/BSP/BeginnersHOWTO
[18:12] <c_smith> could I possibly participate from where I am (home)?
[18:12] <kees> c_smith: sure!
[18:13] <c_smith> cool, once I have these updates done, I'll be starting.
[18:14] <c_smith> although, I'll likely be focusing on easy (bytesize) bugs in Ubuntu, I am in no way a programmer, nor do I have coding knowledge.
[18:15] <spw2> c_smith: right there with ya, but on the opposite. I am a programmer, but have nearly NO linux knowledge. feel lost.
[18:15] <slangasek> http://udd.debian.org/bugs.cgi?release=wheezy_and_sid&fnewer=&fnewerval=7&rc=1
[18:15] <c_smith> spw2, well, first time for everything, eh?
[18:16] <spw2> i sure hope so.
[18:19] <tgm4883> c_smith, why are you running it on 64-bit wine
[18:19] <tgm4883> even the wine developers admit 64-bit wine sucks
[18:19] <c_smith> tgm4883, because that was the version installed on 64-bit Windows.
[18:20] <c_smith> *64-bit Ubuntu, not Windows.
[18:20] <c_smith> might have been running in compatibility mode, but the installshield wizard didn't like even that.
[18:20] <tgm4883> c_smith, wait, you mean wine 32
[18:20] <c_smith> probably.
[18:20] <tgm4883> you have to compile wine64 by hand
[18:21] <tgm4883> so it should run the same on both 64-bit ubuntu and 32-bit ubuntu, since the wine is the same
[18:21] <tgm4883> wine64 is for running 64-bit windows programs
[18:22] <c_smith> not sure. it had "Program Files" and "Program Files  (x86)" in the wine prefix.
[18:22] <tgm4883> hmm
[18:22] <c_smith> so that lead me to believe it had installed Wine64.
[18:22] <tgm4883> strange
[18:22] <tgm4883> sounds like that to me too
[18:22] <c_smith> might have changed. eh?
[18:23] <c_smith> anywho, suffice it to say, I'm running 32-bit now, the architecture my laptop was built for.
[18:23] <tgm4883> well now I'm just confused, which means it's time for me to go get coffee
[18:23] <c_smith> I'm not really getting any benefit on the laptop by running 64-bit over 32-bit.
[18:51] <bkerensa> Don't forget to signup for the mailing list and launchpad http://ubuntu-oregon.org
[18:59]  * c_smith is already there
[18:59]  * c_smith continues to wait for pbuilder
[19:10] <vagrantc> pbuilder? :(
[19:12] <c_smith> vagrantc, what's wrong with pbuilder?
[19:12] <slangasek> it's a NIH kludge, and anything that behaves differently under pbuilder than under sbuild is a pbuilder bug by definition because sbuild is what the buildds use :)
[19:13] <c_smith> lol
[19:14] <c_smith> gnupg is useful for not just development, like if you wanted to encrypt a file.
[19:14] <c_smith> just saying.
[19:15] <c_smith> >.< think I attracted someone from #linuxdistrocommunity
[19:15] <corp769> yes you did, lol
[19:15] <c_smith> not that it's a bad thing :P
[19:15] <corp769> just checking it out man
[19:16] <c_smith> corp769, you aren't from Oregon, are you?
[19:16] <corp769> no i'm not
[19:16] <corp769> why do you ask?
[19:16] <c_smith> oh, ok
[19:16] <c_smith> simply because this LoCo is for that state.
[19:16] <corp769> yeah i noticed
[19:17] <corp769> i was just checking out the channel, that's all
[19:17] <corp769> but i'm out
[19:17] <corp769> take care man
[19:17] <c_smith> and it'd be nice to be able to invite you to an Ubuntu Hour.
[19:17] <c_smith> cya
[19:17] <corp769> ubuntu hour?
[19:18] <corp769> what's ubuntu hour, c_smith?
[19:18] <c_smith> corp769, I sent you a message with the wiki page about it.
[19:19] <corp769> oh ok
[19:19] <corp769> i'm checking it out, thanks man
[19:19] <c_smith> no prob
[19:39] <c_smith> does anyone here know if Harvest is working yet?
[19:39] <slangasek> "working"?
[19:41] <c_smith> if I remember, the opportunities weren't refreshing back when the Global Jam was happening.
[19:41] <nathwill> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617938 ?? seems like it's wontfix.
[19:41] <c_smith> has that changed?
[19:42] <c_smith> slangasek, the opportunities weren't refreshing back at the Global Jam, has that changed?
[19:45] <c_smith> if I'm working with wrong dependencies, is that purely in the debian rules file?
[19:46] <slangasek> c_smith: refreshing> ah, I couldn't say
[19:47] <slangasek> c_smith: dependencies are always in debian/control, not debian/rules
[19:47] <c_smith> slangasek, ok
[19:47] <c_smith> and thanks for the tip on the dependancies, I knew it was one of the debian files.
[19:48] <c_smith> another question: if I manage to fix this bug, would it be good practice to upload it to Debian first?
[19:48] <c_smith> being as it's Pidgin.
[19:50] <slangasek> r0csteady: http://udd.debian.org/bugs.cgi?release=wheezy_and_sid&fnewer=&fnewerval=7&rc=1
[19:54] <c_smith> meh, looks like the bug was fixed.... >.<
[20:15] <slangasek> tngodup: so once you have a handle on the build environment, you would want to do: schroot -u root -c sid; apt-get install zhcon gdb; GGI_DISPLAY=really_long_string_to_try_to_reproduce_the_crash zhcon; then if it does crash, GGI_DISPLAY=really_long_string_to_try_to_reproduce_the_crash gdb zhcon
[20:15] <tngodup> ok
[20:28] <c_smith> hello
[20:28] <c_smith> bkerensa, has the meeting ended?
[20:29] <c_smith> or has it not begun?
[20:36] <c_smith> bkerensa, did I miss the meeting?
[20:40] <bkerensa> Are there any agenda items?
[20:42] <c_smith> don't know. let me check
[20:42] <bkerensa> I think there is not and we have nothing to discuss her unless you do?
[20:44] <c_smith> nah, just wanted to make sure I didn't miss anything.
[20:44] <c_smith> now I have some stuff to do.
[20:45] <c_smith> cya
[20:55] <slangasek> closed Debian bug #603405
[20:55] <slangasek> would put an RC bug count in the topic, but it's locked ;)
[20:58]  * vagrantc ponders #debian-bugs
[21:18] <r0csteady> ohai jpiroshky
[21:19] <c_smith> hello, r0csteady
[21:29] <jpiroshky> hey j00 guys, lets be good friends ^_^
[21:44] <c_smith> hello, jpiroshky
[21:44]  * c_smith goes back to listening to a talk about IP and DNS
[21:47] <jpiroshky> man -k pxe
[21:47] <jpiroshky> oops ^_^
[23:05] <nathwill> so... i'm pretty sure that this bug is wrong
[23:05] <nathwill> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631257
[23:10] <slangasek> nathwill: wrong how?
[23:19] <devxdev> any one on thats @ bsp?
[23:30] <vagrantc> things are winding down on the BSP
[23:31] <devxdev> :( just got back from the beach, that was the agreement with the wife, I go if she gets to go to the beach lol
[23:40] <vagrantc> well, there are still people here
[23:46] <kees> come back nathwill!
[23:46] <vagrantc> wait a minute...
[23:48] <kees> his bug looks valid to me
[23:48] <kees> dovecot postinst will overwrite half a cert. oops


[14:11] <ytzvan> Chanservv
[14:11] <ytzvan> ChanServ
[14:31] <ytzvan> ytzvan
[14:32] <ytzvan> @ytzvan


[21:30] <CommunistWolf> I can see ubports runs telepathy. can I add an arbitrary connection manager without issue?
[21:30] <CommunistWolf> I mean, I'm about to try it :D, as soon as this cross-compile completes
[22:19] <CommunistWolf> drat, foiled by ancient openssl


[04:03] <ojwb> hi, cheeky question - any chance of getting the priority bumped on a ppa build?  I have a samba compatibility fix I was hoping to test today but it's estimating 17 hours to start
[04:04] <ojwb> I only need i386: https://launchpad.net/~ojwb/+archive/experimental/+build/2667436
[07:45] <aminpy> http://dpaste.com/587830/ <- can anybody help me?
[07:45] <aminpy> I'm using vpn connection
[07:45] <aminpy> how can I fix this problem^?
[08:48] <aminpy> http://dpaste.com/587858/plain/ <- can anybody help me?
[12:02] <ujjain> Hi. What kind of translation files does launchpad generate, .po?
[16:07] <TheEvilPhoenix> if I have a project on launchpad, and I wish to add my own supplementary license to dictate stricter terms than the GNU GPL v3, and I provide the complete text of that supplementary license, does LP have to review said supplementary license?
[20:26] <andrejz> Hello! I was wondering if someone can look at this bug, please - https://bugs.launchpad.net/launchpad/+bug/809791
[20:27] <andrejz> Situation was reasonably acceptable until recently
[20:27] <andrejz> But as of today I get timeout on every string
[22:35] <TheEvilPhoenix> did anyone ever answer my question... my logs don't include any text that qualifies as a response...
[22:36] <TheEvilPhoenix> this was the original question: <TheEvilPhoenix> if I have a project on launchpad, and I wish to add my own supplementary license to dictate stricter terms than the GNU GPL v3, and I provide the complete text of that supplementary license, does LP have to review said supplementary license?
[22:38] <wgrant> TheEvilPhoenix: Supplementary how?
[22:39] <wgrant> TheEvilPhoenix: You cannot force people to distribute something under GPLv3 + other restrictions.
[22:39] <wgrant> You can give them the option of GPLv3 or some other license, but not GPLv3 with restrictions.


[00:58] <StevenK> lifeless: ^ Did you get distracted?
[01:00] <lifeless> yes
[01:07] <lifeless> StevenK: uhm
[01:07] <lifeless> auditorfixture appears to be auditor ?
[01:08] <StevenK> How the heck did I screw *that* up
[01:10] <lifeless> NFI
[01:10] <lifeless> but
[01:10] <lifeless> you did :)
[01:10] <StevenK> Yeah, I'm just about to push --overwrite
[01:14] <StevenK> lifeless: It should look better now?
[01:20] <lifeless> p[-;;;;;;;;;;;;;;;;;;;;;xccccccccccccccccccbvvvvvvvvvvvvvvvvvvvvv
[01:20] <lifeless> uhm, cat.
[01:20] <StevenK> Hah
[01:21] <lifeless> does runserver support dynamic port allocation ?
[01:23] <StevenK> lifeless: From what I saw, yes.
[01:23] <lifeless> StevenK: you did something similar to txlongpollfixture, I presume; that did what I did for rabbit, which doesn't support dynamic port allocation
[01:24] <lifeless> a better thing, if its doable is to just run runserver and watch what port it chooses
[01:24] <lifeless> StevenK: that said, if this works, great.
[01:24] <StevenK> Which it doesn't.
[01:25] <StevenK> But I've hit the limit of Django-ness -- I dislike the idea of forking off python to run it
[01:25] <lifeless> StevenK: my main concern looking at is is that we'll have the same bugs that rabbitfixture has had w.r.t. race conditions on startup (such as the timeout logic); we should perhaps consolidate the common code into fixtures
[01:25] <lifeless> StevenK: running django in a subprocess is entirely appropriate
[01:26] <lifeless> StevenK: we /do not want/ to try and import django into our python environment - for multiple reasons, including django having a honking great set of global variables that will collide
[01:26] <lifeless> https://docs.djangoproject.com/en/dev/ref/django-admin/#runserver-port-or-address-port suggests it does not do dynamic ports.
[01:27] <lifeless> StevenK: ok, so it doesn't work. What happens, specifically ?
[01:29]  * StevenK rips out the devnull, so he can see what is going on
[01:29] <lifeless> StevenK: oh, I see the devnull. Don't do that :)
[01:30] <StevenK> Hm, smoking gun
[01:30] <lifeless> StevenK: you can capture the stdout to e.g. the logfile
[01:30] <lifeless> StevenK: and you won't lose information that way
[01:30] <StevenK> devnull is for stdin
[01:30] <StevenK> However, for this I wanted the output to the terminal
[01:31] <StevenK> python manage.py is all well and good -- when you're in auditor's directory
[01:31] <lifeless> bleep, I misread.
[01:31] <lifeless> yes.
[01:32] <StevenK> So I wonder if auditor is hiding somewhere I can call it ...
[01:32] <lifeless> why did you want terminal? To see what was up ?
[01:32] <lifeless> The failure message should have given you the log file ocontents.
[01:32] <StevenK> lifeless: Nope, I was just getting the raise Exception("Timeout ....
[01:33] <lifeless> StevenK: so you have a fixture object
[01:33] <lifeless> that.getDetails() should give you a path in, for future reference.
[01:33] <lifeless> e.g. f.getDetails().items()[0].itertext()
[01:33] <StevenK> lifeless: In _start(), that's going to be self, isn't it?
[01:33] <lifeless> StevenK: yes, but _start doesn't need to change.
[01:34] <lifeless> StevenK: you already attach the logfile; the caller can choose to look
[01:34] <lifeless> StevenK: TestCase.useFixture attaches the details before it sets up, IIRC, so it should be doing this.
[01:34] <StevenK> lifeless: I think _start() does need to change, since the error is "python: can't open file 'manage.py': [Errno 2] No such file or directory" :-)
[01:34] <lifeless> StevenK: doesn't need to change w.r.t. reporting :P
[01:35] <lifeless> StevenK: you need to introspect to get the path to the auditor egg, txlongpoll should have example code.
[01:35] <StevenK> txlongpoll or txlongpollfixture?
[01:35] <lifeless> the latter
[02:00] <StevenK> lifeless: Right, I see how txlongpollfixture does it. But auditorfixture doesn't have parts/auditor :-(
[02:01] <StevenK> lifeless: And I have a [auditor] section in buildout.cfg
[02:08]  * wgrant cries
[02:08] <wgrant>             for team in administers_and_in:
[02:08] <wgrant>                 if (bug_supervisor is not None and
[02:08] <wgrant>                     not team.inTeam(bug_supervisor)):
[02:08] <wgrant>                     continue
[02:08] <wgrant> inTeam is not preloaded
[02:09] <lifeless> StevenK: uhm, your auditor section doesn't define an entry point
[02:09] <StevenK> lifeless: It needs to? My buildout-foo is very weak
[02:10] <lifeless> StevenK: I *think* so, it generates the right interpreter etc
[02:10] <lifeless> I just realised, running 'python manage.py' is wrong because of that, it should be a buildout created python executable
[02:11] <lifeless> which the entry points are used to do
[02:12] <StevenK> lifeless: I still need a path to manage.py, I don't think it matters which interpreter I use.
[02:12] <StevenK> txlongpollfixture somehow ends up with parts/txlongpoll
[02:14] <lifeless> uhm
[02:14] <lifeless> not sure where to pull on this one
[02:15] <lifeless> you don't run the manage.py from auditor directly
[02:15] <lifeless> python version mismatch etc stuff
[02:15] <StevenK> Not even the unpacked egg?
[02:15] <lifeless> indeed
[02:15] <lifeless> txlongpollfixture doesn't either.
[02:18] <StevenK> Ah. So what should I do?
[02:18] <lifeless> so the basic idea
[02:19] <lifeless> is you have a function which can be an entry point
[02:19] <lifeless> e.g. def foo(argv=None):
[02:19] <lifeless>     if argv is None: argv = sys.argv
[02:19] <lifeless>     ...
[02:19] <lifeless> that is probably inside manage.py already
[02:20] <lifeless> you point at the *python path* to that function, which will be inside auditd (and you'll probably know far more about django glue than you want to by the time you're done)
[02:20] <lifeless> buildout generates a local executable for you in bin/ when you set scripts=
[02:20] <lifeless> see entry-points = twistd-for-txlongpoll=twisted.scripts.twistd:run
[02:20] <lifeless> scripts = twistd-for-txlongpoll
[02:20] <lifeless> for instance, in LP's buildout.cfg
[02:20] <lifeless> so you'll have something like
[02:21] <lifeless> entry-points = auditord-manager=auditord.manager:run
[02:21] <lifeless> scripts = auditord-manager
[02:21] <lifeless> then, the fixture runs bin/auditord-manager
[02:22] <lifeless> probably adjusted to be os.path.join(os.getcwd(), 'bin/auditord-manager')
[02:22] <lifeless> because of the cwd param to Popen
[02:23] <lifeless> StevenK: does that make sense?
[02:23] <StevenK> lifeless: Barely
[02:24] <StevenK> lifeless: So I need a auditord module now?
[02:24] <lifeless> you have one
[02:24] <lifeless> the django app
[02:25] <lifeless> whats the auditord project name ?
[02:25] <StevenK> auditor
[02:28] <lifeless> auditlog is your module name
[02:29] <lifeless> you need to move / symlink or something manage.py within auditlog from the looks of things
[02:29] <lifeless> and ugh yeah the one thing I really don't like about django - settings
[02:30] <wgrant> Um
[02:30] <wgrant> That's the one thing?
[02:30] <StevenK> Haha
[02:30] <wgrant> It's one of the worst things, but lots of the rest is also hideous :)
[02:30] <StevenK> lifeless: And apparently a fixture would be *easy*
[02:30] <StevenK> ... and other lies I've been told. :-)
[02:32] <StevenK> lifeless: I'm not sure what module you want me to jump into?
[02:32] <StevenK> auditor.manage seems pointless
[02:34] <wgrant> lifeless: Shouldn't manage.py be replaced by a buildout-generated bin/manage?
[02:35] <lifeless> wgrant: yes, thats what I'm describing
[02:36] <lifeless> StevenK: you have a package 'auditlog'
[02:36] <lifeless> StevenK: We have a project 'auditord', with a public name of 'auditor' and package 'auditlog' - I think you should choose one and go with it
[02:37] <StevenK> lifeless: I can't!
[02:37] <lifeless> StevenK: why not ?
[02:37] <StevenK> You can't call the app 'auditor' if the project is.
[02:37] <lifeless> .expand()
[02:37] <wgrant> I'm pretty sure you can.
[02:38] <StevenK> lifeless: I never picked the name auditord, that was you
[02:38] <wgrant> It just gets a bit odd, due to implicit relative imports.
[02:38] <lifeless> ok, so, auditor, fine.
[02:38] <lifeless> What happens if you use the name auditor for the package ?
[02:39] <StevenK> steven@undermined:~% django-admin startproject foobar
[02:39] <StevenK> steven@undermined:~% cd foobar
[02:39] <StevenK> steven@undermined:~/foobar% python manage.py startapp foobar
[02:39] <StevenK> Error: You cannot create an app with the same name ('foobar') as your project.
[02:39] <wgrant> Try it anyway
[02:40] <wgrant> It'll probably work
[02:40] <StevenK> I just did?
[02:40] <wgrant> You tried using Django's stupid tool to do it.
[02:40] <StevenK> And?
[02:41] <StevenK> I'd been avoiding Django just fine until you two railroaded me into auditor.
[02:42] <lifeless> https://code.djangoproject.com/ticket/1908
[02:43] <wgrant> Well
[02:43] <wgrant> I never suggested Django is a good fit.
[02:43] <wgrant> It's really not.
[02:43] <lifeless> 5 months ago
[02:43] <lifeless>     Triage Stage changed from Accepted to Fixed on a branch
[02:43] <lifeless> The bug has been fixed in trunk, apps with same name as project name can be created now
[02:44] <StevenK> wgrant: I think that was lifeless
[02:44] <lifeless> StevenK: what was me ?
[02:44] <StevenK> Suggesting Django
[02:45] <lifeless> its a preferred tech
[02:45] <lifeless> I've said explicitly that I think its sufficient for the small targeted things we need
[02:45] <lifeless> that it has some very good values around lean-ness, clean& understandable code, and performance
[02:46] <wgrant> Um
[02:46] <lifeless> and that it may be too heavyweight for some things (like gpg-httpd)
[02:46] <wgrant> The problem is not that it's insufficient.
[02:46] <StevenK> And then you try and write a fixture and go insane
[02:46] <lifeless> StevenK: you're breaking new ground
[02:46] <wgrant> It's that all of the awkward stuff it provides is entirely useless for this sort of service.
[02:46] <wgrant> For auditordloger, the useful stuff it provides over raw WSGI is an ROM
[02:46] <wgrant> ORM
[02:47]  * lifeless notes that this is a distraction
[02:47] <StevenK> Clearly you want the app to be called auditor too, which means I need to look at packaging Django 1.4
[02:47] <lifeless> StevenK: auditlog is a package name, that is the package you need to make a manager.py exist in, it's probably easiest to have it be a new file with contents derived from the django made one.
[02:48] <lifeless> StevenK: I do, but even that is a distraction
[02:48] <lifeless> StevenK: and, its one that can be solved later. Because nothing in LP will know about *either* auditor or auditlog.
[02:48] <StevenK> lifeless: Why does it need to exist under auditlog?
[02:48] <lifeless> StevenK: so that buildout can import it.
[02:48] <StevenK> But buildout can import from auditor too?
[02:48] <StevenK> auditor/__init__.py exists, so it import auditor should work
[02:49] <lifeless> wait, what
[02:49] <lifeless> OHHH
[02:49] <lifeless> crazy f*d up layout.
[02:49] <lifeless> ok, so yes, auditor.manage:run
[02:49] <lifeless> and edit manage.py to have a run() method
[02:49] <lifeless> (and the usual if __name__ == '__main__': boilerplate
[02:50] <StevenK> manage.py already has __main__ boilerplate
[02:50] <lifeless> it does, it needs altering
[02:52] <lifeless> e.g. http://paste.ubuntu.com/998398/
[02:54] <lifeless> StevenK: btw, we probably want to change auditor from being a django project to being a django app (and then have a project which is for testing created on the fly, and one for prod deployment)
[02:54] <lifeless> StevenK: but again, Future Work.
[02:55] <lifeless> StevenK: I will make one note on the naming of things; the reason I propose auditord is so that auditor is available for a client library, if you were to decide you want one.
[02:55] <lifeless> StevenK: as it is, you'll have to use auditorclient or something instead.
[02:56] <StevenK> Client library? Err?
[02:56] <StevenK> It returns JSON, how can that possibly require a client library?
[02:57] <lifeless> you never know your own future :)
[02:58] <lifeless> I'm not asking you to rename it, I'm explaining why I'm sticky on the d's - its an easy default and makes it easier for me to think about names.
[02:58] <StevenK> I can see a gun and my temple in my future
[02:58] <lifeless> I don't think quake3 supports that.
[02:58] <StevenK> Who said anything about Quake 3?
[02:59] <StevenK> lifeless: bin/auditor-manage can not import auditor.manage
[03:00] <lifeless> StevenK: I did, because why not?.
[03:01] <lifeless> StevenK: so, thats python path debugging time
[03:02] <StevenK> sys.path = ['/home/steven/auditorfixture/parts/auditor', '/home/steven/auditorfixture/bin', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-linux2', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/home/steven/auditorfixture/eggs/auditor-0.0.1-py2.7.egg', '/home/steven/auditorfixture/eggs/Django-1.4-py2.7.egg']
[03:02] <lifeless> and is manage.py present within /home/steven/auditorfixture/eggs/auditor-0.0.1-py2.7.egg ?
[03:03] <StevenK> Sigh, no.
[03:04] <StevenK> I guess that's due to find_packages() in auditor's setup.py
[03:12] <lifeless> StevenK: yes, I suspect so
[03:13] <lifeless> StevenK: note that its not finding the top level __init__.py at all
[03:13] <lifeless> StevenK: so your egg only contains auditlog.
[03:13] <StevenK> Yes
[03:18] <lifeless> http://paste.ubuntu.com/998418/
[04:01] <wgrant> lifeless: Oh yeah
[04:01] <wgrant> lifeless: I discovered on Friday evening that my optimisation of bugsummary was bad.
[04:02] <wgrant> lifeless: I'd accidentally typoed so it flushed the journal into the journal, so it was writing to a temp table, not a real one.
[04:02] <wgrant> So it's only about 2.5x faster than before.
[04:03] <wgrant> s/flushed the jounral into the journal/flushed the temp journal into the temp journal/
[04:03] <wgrant> And that's with journal FKs removed.
[04:04] <lifeless> wgrant: still, 2.5x is fast enough to run two in parallel
[04:05] <wgrant> lifeless: I have a cunning plan to avoid having to do that.
[04:05] <wgrant> A couple of unresolved issues, but it should work.
[04:08] <lifeless> StevenK: that pastebin was to you, should work.
[04:10] <wgrant> StevenK, wallyworld_: https://code.launchpad.net/~wgrant/launchpad/bugsummary-v2-app-no-fixed-upstream/+merge/106557
[04:11]  * wallyworld_ looks
[04:17] <wallyworld_> wgrant: looks ok to me. lots of code deletion :-)
[04:17] <wgrant> wallyworld_: Yup. Thanks.
[04:47] <mwhudson> https://bugs.launchpad.net/lava-deployment-tool/+bug/1000819/@@+huge-vocabulary timeouts are known?
[04:47] <_mup_> Bug #1000819: uwsgi 1.0.3 no longer available <LAVA Deployment Tool:New> < https://launchpad.net/bugs/1000819 >
[04:48] <mwhudson> https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-f6d562060ee52035ead5254827fee6ab\
[04:52] <wgrant> mwhudson: Yeah, branch search is criminally bad
[04:53] <mwhudson> :(
[04:54] <mwhudson> is it just select from branch where unique_name like '%${TERM}%' or something?
[04:54] <wgrant> The query is awful awful awful
[04:54] <wgrant> But it shouldn't be as slow as it is.
[04:55]  * mwhudson looks at the code
[04:55] <wgrant> It's in the OOPS
[04:55] <wgrant> Top statement.
[04:55] <mwhudson> i think my bad version is a lot better than this
[04:55] <wgrant> Oh
[04:55] <wgrant> wut
[04:56] <wgrant> SELECT Branch.id
[04:56] <wgrant> FROM Branch,
[04:56] <wgrant>      Product
[04:56] <wgrant> WHERE Branch.product = Product.id
[04:56] <wgrant>   AND Product.name LIKE u$STRING)
[04:56] <wgrant> I'm pretty sure that comes under "who could possibly think that was useful or a good idea"
[04:56] <wgrant> I didn't realise it did that too
[04:56] <mwhudson> OR Branch.url = u$STRING) is my favourite useless bit i think
[04:56] <wgrant> Why?
[04:57] <mwhudson> branch.url is NULL for !mirror branches
[04:57] <wgrant> Oh, so it is.
[04:57] <mwhudson> and noone case about mirror branches any more
[04:57] <wgrant> Not unique_name, right
[04:57] <wgrant> Yeah
[04:57] <mwhudson> Product.name LIKE u$STRING is pretty special yes
[04:57] <wgrant> The theory behind it seems to be "find ALL the things"
[04:58] <wgrant> And then leave the user to page through the 9s batches.
[04:58] <mwhudson> itym "try to find all the things, but timeout instead'
[04:58] <StevenK> Apparently, find_packages() looks for __init__.py in directories. I think it lies. :-(
[04:58] <wgrant> It works sometimes!
[04:58] <wgrant> mwhudson: Part of the problem is bugtasks.
[04:58] <wgrant> mwhudson: Because there's no logical context to search in.
[04:58] <mwhudson> oh right
[04:58] <mwhudson> well
[04:59] <wgrant> So you have to search everywhere, probably.
[04:59] <mwhudson> you could look in the context for all the extant bugtasks i guess?
[04:59] <wgrant> Yeah
[04:59] <mwhudson> but that gets a bit complicated
[04:59] <wgrant> We introduced that concept with disclosure.
[04:59] <wgrant> It's possible.
[04:59] <mwhudson> cool
[04:59] <wgrant> Then I'd do name LIKE '%foo%' or unique_name = 'foo', I think...
[04:59] <mwhudson> seriously though unique_name like $string would be as good as this
[04:59] <wgrant> Not sure it needs much more than that.
[04:59] <lifeless> StevenK: it does, but it starts with listdir()
[04:59] <lifeless> StevenK: did you apply my patch ?
[04:59] <wgrant> unique_name LIKE '%foo%' is a bit bad, as it matches the product name.
[05:00] <wgrant> But maybe.
[05:00] <mwhudson> (of course, unique_name is only 4 years old or whatever, so much newer than this code)
[05:00] <StevenK> lifeless: I was out for lunch with a friend, so if it was a patch to setup.py, I'm sorry but I missed it
[05:00] <mwhudson> wgrant: not saying mine is good, just better than existing
[05:00] <lifeless> 15:18 < lifeless> http://paste.ubuntu.com/998418/
[05:00] <wgrant> mwhudson: With 9.1 we can even use trigram indices to make LIKE '%foo%' very fast.
[05:00] <lifeless> (its now 17:00 and EOD)
[05:00] <mwhudson> bug 372591
[05:00] <_mup_> Bug #372591: Branch vocabulary and search needs thought and cleaning up <lp-code> <tech-debt> <Launchpad itself:Triaged> < https://launchpad.net/bugs/372591 >
[05:00] <wgrant> mwhudson: That title has a few too many euphemisms.
[05:01] <mwhudson> it's a dup of https://bugs.launchpad.net/launchpad/+bug/793830 anyway
[05:01] <_mup_> Bug #793830: Branch:+register-merge time out due to substring matching many tables <critical-analysis> <timeout> <Launchpad itself:Triaged> < https://launchpad.net/bugs/793830 >
[05:01] <wgrant> Yeah
[05:01] <wgrant> That's the one that wallyworld was hitting a lot last week
[05:02] <StevenK> lifeless: Right, I did miss it -- I scanned backlog until I hit wgrant begging for a review and stopped.
[05:02] <wgrant> Oh, the prereq or target branch you specified doesn't match a unique_name exactly? Let me just do a 10s search for you.
[05:02] <mwhudson> heh
[05:02] <mwhudson> that makes the pain less avoidable i guess
[05:03] <mwhudson> (my oops was from the suggestions in the 'link a branch' overlay)
[05:09] <StevenK> lifeless: error: can't copy 'uditor.egg-info/PKG-INFO': doesn't exist or not a regular file
[05:09] <StevenK> EWTF
[05:09] <wgrant> mwhudson: I don't know about you, but my distribution of searches is roughly this: 95% of the time it's one of the last 5 branches I touched; 4% I want to search by substring of name in the current project; 1% I want to search by full unique_name (optionally including lp:)
[05:12] <mwhudson> wgrant: certainly "last branch i touched" is a good guess a lot of the time
[05:13] <mwhudson> and in this case it was a mixture of the first two points
[05:13] <wgrant> Yeah, but ranking like that is hard.
[05:13] <wgrant> So we tend to try to avoid combining them like that.
[05:14] <mwhudson> solr-as-a-service!
[05:14]  * mwhudson goes back to real work
[05:15] <StevenK> mwhudson: We know where you live!
[05:38]  * StevenK stabs PlainPackageCopyJobTests.createCopyJob() for failing
[06:08] <lifeless> mwhudson: patches solicited
[06:08] <lifeless> mwhudson: if you get tired of doing easy things
[06:19] <StevenK> wgrant: Should I need to do anything after running acceptFromQueue() on the PU and then re-running the PCJ?
[06:20] <StevenK> wgrant: Since IArchive.getPublishedSources(name=) is returning [] :-(
[06:23] <wgrant> StevenK: Sounds like the PCJ is not running.
[06:29] <StevenK> Oh, it does run, it just raises CannotCopy
[06:29] <StevenK> Which it doesn't tell me
[06:30] <StevenK> unique-from-test-packagecopyjob-py-line361-100000 1.0-1 in breezy-autotest (The signer of this package has no upload rights to this distribution's primary archive.  Did you mean to upload to a PPA?
[06:30] <StevenK> Right
[06:52] <lifeless> StevenK: how are you going ?
[07:13] <StevenK> lifeless: I gave up in disgust
[07:14] <StevenK> Trying to get my SPPH linked to PUs working with PCJs
[07:18] <bigjools> why are you doing that?
[07:19] <StevenK> bigjools: Because we'd like to know who accepted something, and that information is directly realted to the PackageUpload, and PCJs create PackageUploads if needed.
[07:20] <bigjools> sounds like a hack
[07:20] <StevenK> How?
[07:20] <bigjools> did you consider any other solutions?
[07:21] <StevenK> Like adding yet another column onto SPPH that shows who accepted it? Now that is a hack.
[07:21] <bigjools> like an audit trail table
[07:22] <StevenK> lifeless nacked it
[07:22] <StevenK> Which is what auditor is for
[07:22] <bigjools> linking to PU is horrible
[07:22] <StevenK> But the acceptance is for the *PackageUpload* there is no publication at that point
[07:22] <bigjools> not all SPPHes result from a PU
[07:22] <StevenK> Of course
[07:22] <bigjools> so, yet another nullable FK
[07:23] <StevenK> Like sponsor? :-P
[07:23] <bigjools> yes :/
[07:23] <wgrant> Nullable FKs are only a problem in theoretical relational algebra.
[07:23] <bigjools> I'm just interested in how you arrived at this solution
[07:24] <bigjools> if it's the least horrible then fair enough
[07:24] <StevenK> bigjools: It was the solution that made the most sense -- with auditor being used and keeping track of a PU as it moves through the queue, we needed a way to easily look up the PU for an SPPH
[07:25] <wgrant> I think it's least bad for now.
[07:25] <bigjools> the whole model is a mess :/
[07:25] <wgrant> Eventually we should replace PU with something that tracks each operation on the archive.
[07:25] <wgrant> Copies and uploads.
[07:25] <wgrant> And overrides.
[07:25] <wgrant> And deletions.
[07:25] <bigjools> like an audit table ...
[07:25] <wgrant> Audit tables have been vetoed.
[07:26] <wgrant> Audit services have not.
[07:26] <wgrant> So StevenK is writing an audit service.
[07:26] <bigjools> what SPPH should have been
[07:26] <wgrant> SPPH only tracks sources.
[07:26] <bigjools> not audit audit ... just a history
[07:26] <wgrant> That'll work OK if we can convince Ubuntu to turn into Gentoo.
[07:26] <wgrant> But I think cjwatson might not approve.
[07:26] <bigjools> lol
[07:27] <bigjools> the lack of any recording on who did what action was a terrible omission from the start
[07:27] <bigjools> but what is done is done
[07:28] <wgrant> As long as we learn from our mistakes.
[07:28] <wgrant> Which we haven't classically done, but we're hopefully getting better.
[07:28] <bigjools> we mostly do
[07:29] <wgrant> The audit service will hopefully mean we can do it easily.
[07:29] <wgrant> For everything.
[07:29] <wgrant> For every action.
[07:30] <bigjools> well I see auditing as two things
[07:30] <bigjools> hysterical data for later analysis
[07:31] <bigjools> and stuff that affects immediate decisions
[07:31] <bigjools> I can't see how a service helps with the latter
[07:41] <lifeless> wgrant: bigjools: is there a link from bug(task) -> packageupload for fixed bugs?
[07:41] <lifeless> bigjools: the service lets you query the actions on an object, so it should handle the latter nicely.
[07:42] <StevenK> wgrant: https://code.launchpad.net/~stevenk/launchpad/populate-spph-pu/+merge/105601 now knows about PCJs. You can review it now if you wish, or tomorrow when you're OCR. :-P
[07:42] <StevenK> lifeless: Fixing bugs does not use the PU, but the changesfile
[07:42] <wgrant> lifeless: There isn't. You'd have to look for the comments
[07:42] <lifeless> StevenK: so if ev wants to get from bug -> BPPH, he goes bug -> changesfile -> SPPH -> BPPH  or some insanity ?
[07:42] <wgrant> StevenK: I'll do it tomorrow
[07:43] <bigjools> lifeless: the upload code scans the changelog
[07:43] <lifeless> bigjools: yah, is the other way round we want
[07:43] <bigjools> I know :)  just telling you how shit it is right now
[07:43] <lifeless> bigjools: so, schema work needed? Thats ok, just want to be sure.
[07:43] <bigjools> it doesn't store the refs
[07:43] <bigjools> just pokes the bugs
[07:43] <StevenK> lifeless: Absolutely schema work needed
[07:44] <StevenK> lifeless: Anyway, you want the SPPH, not the BPPH
[07:44] <lifeless> StevenK: no, we want the BPPH
[07:44] <bigjools> lifeless: bear in mind that ultimately it'd be really nice to serviceify soyuz
[07:44] <lifeless> users don't download sources to fix bugs
[07:44] <StevenK> lifeless: The bug is closed when the *source* is uploaded, not the binaries
[07:44] <lifeless> bigjools: orly :P :P :P
[07:44] <lifeless> StevenK: I know
[07:44] <bigjools> lifeless: bugs are not filed on binaries
[07:44] <lifeless> I know that too
[07:45] <lifeless> expand your minds
[07:45] <StevenK> I've been dealing with buildout and setuptools today. Maybe my mind will uncurl from the fetal position tomorrow morning.
[07:45] <bigjools> linking at schema level adds more hurdles to serviceifying
[07:46] <lifeless> bigjools: it changes the work needed, thats true.
[07:46] <bigjools> lifeless: what is it that you're trying to achieve?
[07:47] <bigjools> coz you're breaking your own rule here :)
[07:49] <lifeless> otp right now, happy to expand later
[07:49] <lifeless> what rule am I breaking ?
[07:50] <bigjools> lifeless: report the problem not a proposed solution
[07:50] <bigjools> no prob anyway, I am about to scoot off for dinner
[07:51] <lifeless> The problem is how to map from bugs (apport ones specifically) to the binary packages that fix problems for users
[07:51] <lifeless> ev and I are discussing how to do that, and trying to identify big stroke work needed to do that
[07:53] <wgrant> Putting that in LP seems like entirely the wrong thing to do.
[07:53] <wgrant> Isn't that a daisy thing?
[07:55] <bigjools> lifeless: This info is in the bug comments
[07:55] <lifeless> yah, we established that
[07:55] <lifeless> sorry, really otp
[07:55] <bigjools> so where's the problem?
[07:56] <wgrant> Like
[07:56] <lifeless> parsing bug comments in a service
[07:56] <bigjools> ah "parsing", you didn't say that ;)
[07:56] <wgrant> Why not have an external service do the same thing.
[07:56] <lifeless> we're discussing that as an option
[07:56] <wgrant> Keep a list of (bug#, package, version)
[07:56] <adeuring> good morning
[07:56] <wgrant> Done
[07:56] <wgrant> Problem solved
[07:56] <wgrant> No LP crap :)
[07:56] <lifeless> wgrant: needs to cross reference tasks
[07:56] <lifeless> wgrant: so no, its not that simple.
[07:56] <wgrant> lifeless: package is there
[07:56] <wgrant> package + bug => task
[07:56] <wgrant> done
[07:56] <wgrant> no LP crap :)
[07:56] <lifeless> wgrant: + series.
[07:57] <wgrant> (bug#, series, package, version)
[07:57] <wgrant> => task
[07:57] <wgrant> done
[08:06] <jam> wasn't there a simple script (that isn't setuplx
[08:06] <jam> setuplxc) for setting up a dev environment? Just rocketfuel?
[08:06] <jam> For some reason I remember a different command (like lpsetup) from the mailing list
[08:10] <lifeless> ev: http://en.wikipedia.org/wiki/Tarjan%27s_strongly_connected_components_algorithm
[08:28] <lifeless> ev: you have frozen
[08:28] <lifeless> ev: http://www.apple.com/xsan/
[08:28] <lifeless> ev: or rather, my desktop has
[08:28] <ev> I'm back at "connecting..."
[08:28] <ev> heh
[08:28] <lifeless> power button pushed.
[08:28] <lifeless> doo be doo
[08:29] <wgrant> jam: lpsetup is being written.
[08:29] <ev> haha
[08:29] <wgrant> jam: But I don't think it's ready yet.
[08:29] <lifeless> frankban is working on it in slack time
[08:29] <wgrant> jam: https://dev.launchpad.net/Running/LXC is the recommended thing to do these days
[08:31] <lifeless> vonderbar, hung on BIOS on reboot
[08:31] <lifeless> OTOH it may have been probing RAM or something; silly quasi-server that it is.
[10:13] <rick_h_> morning
[10:14] <wgrant> stub: Does avahi work for you?
[10:14] <wgrant> stub: It normally fails because the initscript sets a ulimit for the user process limit
[10:14] <wgrant> stub: Which prevents more than ~1.5 avahi instances from running on a single kernel
[10:15] <wgrant> Unless you were lucky and got different UIDs over your two installations.
[12:17] <rick_h_> benji: morning, time for a quick review when you get a sec please? https://code.launchpad.net/~rharding/maza-server/sso_cleanup/+merge/106615
[12:18] <benji> rick_h_: sure, it will be a few minutes (on a call)
[12:18] <rick_h_> benji: no rush, thanks
[12:19] <mgz> so, my after-lunch question, when running launchpad and it gives a 503 on https://launchpad.dev/ where do I go to find out more?
[12:19] <mgz> nothing in logs is very helpful
[12:19] <wgrant> mgz: Sounds like it's not running.
[12:19] <wgrant> Have you started it?
[12:19] <wgrant> (make run or make start)
[12:19] <mgz> I did make run
[12:20] <mgz> and get the :( page
[12:20] <wgrant> Oh
[12:20] <wgrant> That sort of 503
[12:20] <wgrant> That means there's no DB .
[12:20] <wgrant> Possibly postgres isn't running
[12:20] <mgz> that's something neither rocketfuel nor make run do?
[12:21]  * mgz unskips the building step
[12:22] <wgrant> mgz: launchpad-database-setup
[12:22] <mgz> seems not, looks like new log to me
[12:22] <wgrant> Hm?
[12:23] <mgz> I'd wrongly assumed that would be done as part of the bootstrap
[12:23] <wgrant> It wipes out your postgres installation.
[12:23] <wgrant> So doing it implicitly would be a little impolite.
[12:24] <mgz> the output lives in the launchpad tree under database?
[12:24] <mgz> or in a system dir?
[12:25] <wgrant> It rebuilds and reconfigures and populates your default system postgres instance.
[12:25] <wgrant> Usually /var/lib/postgresql/9.1/main
[12:25] <mgz> ace, thanks, so will need this as part of my instance setup
[12:26] <wgrant> That's why it's in the instructions :)
[12:27] <mgz> I blame the red rectangle for making me want to ignore that section
[12:28] <mgz> okay, looks good, thanks wgrant
[12:28] <mgz> really lunchtime
[12:29] <wgrant> Heh
[13:55] <jam> jtv: there seems to be a problem with the clean-up-the-database script that we were running trying to get Q translations working again.
[13:56] <jam> I've heard that you're the guy who knows whats up, if you can give me a pointer, I can try to take it from there.
[14:12] <jamestunnicliffe> benji: Hi, could I get a review started? https://code.launchpad.net/~dooferlad/launchpad/upcomingwork_show_incomplete_bp
[14:12] <benji> jamestunnicliffe: you have good timing, I was just looking at it
[14:12] <jamestunnicliffe> benji :-)
[14:21] <benji> jamestunnicliffe: I approved your branch with a couple of small suggestions.
[14:22] <jamestunnicliffe> benji: Thanks. I have another branch waiting you have a moment, but I don't want to hog all your reviewing time!
[14:23] <benji> jamestunnicliffe: I just started on it too
[14:23] <jamestunnicliffe> benji: Ah, thanks for the tal:conditional tip. I could not find a code example showing that. Clearly google was broken on Friday...
[14:24] <benji> my pleasure
[14:47] <benji> jamestunnicliffe: review done; I saw that you could remove a couple of (pre-existing) calls to float that aren't needed, if you feel like it.  Other than that the branch looks good.
[14:48] <jamestunnicliffe> benji: I am up for changing to <tal:upcoming_work_class_name define="global upcoming_work_class_name string:expanded"/> but I have a question. The tal:<string> seems to be required but <string> doesn't seem to matter. Is it just convention that we match it (namespace?) with the name of the thing we are defining?
[14:49] <benji> jamestunnicliffe: right, the element name can be whatever you want, people often use "<tal:block>" for those, so that's an option too
[14:50] <jamestunnicliffe> benji: Thanks.
[14:51] <benji> np
[14:55] <jamestunnicliffe> benji: I have uploaded a new branch. I don't have merge privs though. Can you kick that into action?
[14:55] <benji> jamestunnicliffe: sure
[14:56] <jamestunnicliffe> benji: Will get rid of those float calls and ping you to merge that in a moment.
[14:56] <benji> jamestunnicliffe: cool
[15:02] <jamestunnicliffe> benji: lp:~dooferlad/launchpad/postponed-is-done is ready as well now. Thanks!
[15:02] <benji> k
[18:24] <lifeless> morning
[18:30] <jelmer> hey lifeless
[18:32] <lifeless> hey jelmer
[18:32] <lifeless> any luck on subunit ?
[19:06] <cjwatson> benji: Thanks for your review of https://code.launchpad.net/~cjwatson/launchpad/germinate-stale-files/+merge/106626; I've made adjustments.  Can you set Status to Approved if you're happy with that, and I'll land it?
[19:07] <lifeless> jelmer: ^?
[19:08] <benji> cjwatson: I've set it to approved.  You should feel free to do so too.
[19:09] <cjwatson> Thanks
[19:11] <benji> oh, and cjwatson: yes, you're weird ;)
[19:12] <cjwatson> heh
[19:13] <cjwatson> I guess I find it easier to be consistent about using context managers everywhere possible rather than having to think about (even trivial) exceptions
[19:13] <cjwatson> or something.  hard to cognitively unpack
[19:39] <cjwatson> Or possibly that it means that the safest ways to create an empty file and create a non-empty file are spelled more similarly
[22:25] <wgrant> WebOps: how many OpenIDs are on https://launchpad.net/~dachary/+reviewaccount?
[22:29] <spm> wgrant: just the 1
[22:32] <wgrant> Oh hm
[22:32] <wgrant> spm: SELECT * FROM openidrpsummary WHERE account = (SELECT id FROM account WHERE openid_identifier='dnTeEXH');
[22:32] <wgrant> On SSO
[22:32] <wgrant> Or equivalent web UI if there is one.
[22:33] <spm> itt, we learn that wgrant is single handedly responsible for wvg task queuing
[22:33] <spm> >:)
[22:33] <wgrant> No, that's users who somehow create more than one SSO account without noticing.
[22:36] <czajkowski> special
[22:37] <spm> czajkowski: yes, yes I am. thanks for noticing!
[22:38]  * czajkowski peer at spm have you been taking lessons from mr. StevenK
[22:38]  * StevenK raises an eyebrow.
[22:38] <spm> pfft. try other way around. the grasshopper learns from the master
[23:26] <StevenK> wgrant: Is bug heat dead enough to nail bug 705713 shut?
[23:26] <_mup_> Bug #705713: Bug:EntryResource Timeout trying to set bug private - death by sql / late evalation <timeout> <Launchpad itself:Triaged> < https://launchpad.net/bugs/705713 >
[23:28] <StevenK> Oh my god, I know what I need to fix
[23:28] <wgrant> StevenK: Indeed, thanks.
[23:56] <StevenK> RARGH
[23:57] <StevenK> Any OOPS I've tried to see from following links in bug reports gives no such oops
[23:57] <StevenK> And then Firefox crashed


[04:54] <Mirv> rvr: ok hmm let's continue it today. mzanetti did not see the problem anymore but as mentioned it's hard to reproduce. then again the patch (http://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/io/qlockfile_unix.cpp?id=4accd865c24b7ed918cb705913478bab5aeb5e6e) of calling fsync is definitely safe
[10:09] <rvr> Mirv: mzanetti: Good morning
[10:10] <rvr> Mirv: mzanetti: I see silo 9 was rebuilt
[10:35] <Mirv> rvr: err, no
[10:36] <Mirv> rvr: https://ci-train.ubuntu.com/job/ubuntu-landing-009-1-build/build 19.5.
[10:36] <rvr> Mirv: I got a new card
[10:36] <Mirv> rvr: someone has restarted some autopkgtests, mysterious
[10:36] <Mirv> I've seen that happen earlier too, I've been wondering if it's a bug somewhere or Foundations team doing some master restart operations
[10:37] <Mirv> rvr: anyway, no rebuild or changes
[10:37] <rvr> Ok
[10:37] <bzoltan> Mirv:  ^ argh... that changelog entry is there
[10:38] <Mirv> bzoltan: I'm staring and staring at the numbers, I can't see anything wrong
[10:39] <Mirv> bzoltan: argh, found
[10:40] <Mirv> bzoltan: fixed trunk http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/1324
[10:40] <Mirv> package name was wrong
[10:52] <bzoltan> Mirv: ehh... those small things. Thank you
[10:53] <Mirv> "sorry"
[12:57] <mterry> robru, heyo.  I have a silo (59) that I was trying to approve and have the autopkg tests run.  They did...  But seemed to fail because of a time out and no actual error?  Do you know how I might find out more information?  Here's a sample artifacts file<EMAIL_ADDRESS>[12:57] <mterry> ar.gz
[12:58] <robru> mterry: ugh i can't open .gz on mobile
[12:59] <mterry> robru, summary says: "qmluitests.sh        FAIL timed out
[12:59] <mterry> autopilot.sh         PASS"
[12:59] <mterry> robru, and stdout just... ends.   And stderr says "dh_auto_build: make -j1 -k xvfballtests died with signal 13"
[13:00] <mterry> robru, seems like autopkg runner killed the tests for taking too long.  What is "too long?"
[13:00] <robru> mterry: did you read the log<EMAIL_ADDRESS>[13:01] <mterry> no...?
[13:01] <robru> mterry: that's what you get when you click "regression" on the excuses page
[13:02] <mterry> robru, yup, adt-run just timed out the test...
[13:02] <robru> mterry: if that log doesn't answer your question then you need pitti. I just run britney i have no idea what it does
[13:03] <mterry> robru, looks like default timeout is 166 minutes
[13:03] <mterry> robru, which we seemed to pass
[13:04] <robru> mterry: no idea how to change that, sorry
[13:12] <dobey> mterry, kenvandine: could either of you re-run https://autopkgtest.ubuntu.com/request.cgi?release=xenial&arch=amd64&package=unity8&trigger=unity-scope-click%2F0.1.1%2B16.04.20160525-0ubuntu1&ppa=ci-train-ppa-service%2Fstable-phone-overlay&ppa=ci-train-ppa-service%2Flanding-047 please?
[13:12] <mterry> dobey, done
[13:12] <dobey> mterry: thanks
[15:22] <rvr> bzoltan: Hi
[15:23] <rvr> bzoltan: Silo 29 has automated signoff set as failed
[16:44] <dobey> yay finally
[16:44] <dobey> now just need qa to test these silos
[19:14] <bzoltan> rvr: it must be some flakyness in the tests... no idea, maybe Mirv could restart those tests. There is no change in the package what would effect those tests.
[19:30] <dobey> gah
[22:58] <ToyKeeper> dobey: There's a bug in ticket 1424, pay-service.  Probably can't land without fixing the new bug.  https://trello.com/c/IVZD5InN/3252-1424-ubuntu-landing-056-pay-service-dobey
[22:58] <ToyKeeper> (doesn't work in U1 account wasn't already logged in)
[22:58] <ToyKeeper> s/in/if/