[00:03] <RAOF> gtm: What driver is it?
[00:03] <RAOF> Too slow :)
[00:06]  * BUGa_vacations headbangs on bitlbee
[00:08] <ScottK> SpamapS: I think almost everything is other (for UDS sessions)
[00:10] <SpamapS> ScottK: at least that makes it simple which track you want to attend. ;)
[00:11] <ScottK> SpamapS: It's never simple for me.  I'm interested in a broad range of topics and am not bound by a job description to narrow my focus.
[00:12] <SpamapS> ScottK: right, for you its always been this easy the. :)
[00:13] <RoAkSoAx> I preferred the previos uds tracks naming conventions
[03:22] <RoAkSoAx> Does fixing a missing pkg-config file installation in a package enought for a SRU?
[03:25] <rneese> hey guys
[03:25] <rneese> small issue I think needs fixing
[03:25] <rneese> php5 pkg
[03:25] <rneese> it should not force you to use apache when you apt-get install php5
[03:25] <rneese> as there are other web servers out there
[03:25] <micahg> rneese: it doesn't
[03:26] <rneese> php5 should be its own install
[03:26] <rneese> yes it does
[03:26] <RAOF> RoAkSoAx: That sounds like a reasonable candidate for me; safe (as such things can be), correct, and fixes other people's builds.
[03:26] <rneese> The following extra packages will be installed:
[03:26] <rneese>   apache2-mpm-prefork apache2-utils apache2.2-bin apache2.2-common libapache2-mod-php5 libaprutil1-dbd-sqlite3 libaprutil1-ldap libcap2 php5-common
[03:26] <rneese>   ssl-cert
[03:26] <rneese> thats with apt-get install php5
[03:26] <micahg> !pastebin | rneese
[03:27] <sanduz2> i agree with rneese, if any of that stuff is not necessary for php5, id like to see it removed as well. many people are not using apache these days
[03:27] <RAOF> rneese: You're looking for php5-cli
[03:27] <micahg> rneese: apache is the default, if you have another webserver, you don't want to install the php5 package which is a metapackage
[03:27] <RoAkSoAx> RAOF: awesome, thanks ;)
[03:29] <rneese> where do i get php5-fpm
[03:29] <micahg> rneese: you need one of these: http://pastebin.ubuntu.com/512071/, apache is first, hence it's the default
[03:29] <RAOF> micahg, rneese: You can happily install the php5 metapackage and use a different web server; you just need to manually specify what web engine you want (php5-cgi, php5-fpm, etc).
[03:29] <rneese> I am using nginx
[03:30] <micahg> RAOF: I know that, we hashed this out a while back on the -server ML
[03:30] <rneese> Couldn't find package php5-fpm
[03:30] <micahg> rneese: you probably want php5-cgi
[03:30] <micahg> rneese: php5-fpm is only in maverick and up
[03:31] <rneese> it should be on lucid
[03:31] <rneese> need it
[03:31] <sanduz2> so if we just want the pure php5 for use in any webserver, the only thing we need is php5-fpm?
[03:31] <sanduz2> (im on mav)
[03:31] <rneese> if 10.04 uses 5.3.3 then php5-fpm should be in pkgs
[03:31] <micahg> rneese: this is off topic for this channel, try #ubuntu-server
[03:31] <micahg> rneese: 10.04 has 5.3.2
[03:32] <micahg> sanduz2: unless you want FastCGI, you probably want php5-cgi
[03:33] <sanduz2> oh, hm. im using cherokee so im not sure what to get. thanks
[03:36] <RoAkSoAx> cjwatson: http://releases.ubuntu.com/.manifest is again showing maverick ISO's only instead of all the other releases ISO's too
[04:57] <persia> wgrant, I've been saved a couple times by dput's marker that something was uploaded.  I'd much prefer it didn't go away.
[05:18]  * ScottK too.
[05:19]  * ScottK has also foud it useful as a reminder of where stuff was uploaded sometimes.
[05:22] <james_w> probably making it smarter about urls would be a good compromise
[05:23] <persia> james_w, How do you mean?
[05:24] <james_w> IIRC it thinks that if you upload to ppa.launchpad.net once then you don't want to upload there again, even if you are uploading to a different path
[05:24] <persia> Oh, that's clearly a bug.
[05:24] <james_w> plus making the error message clearer would be a good thing to do
[05:25] <persia> Mind you, I don't like PPAs in general, so I'm not particularly excited about fixing that one :)
[06:16] <hifi> whats up with maverick and libgdk-pixbuf2.0? it's missing the .la file for linking
[06:19] <persia> Didn't it switch to pkg-config or something?
[06:20] <hifi> actually I'm a bit confused as my home natty compiled freeciv without problems but my maverick can't
[06:20] <hifi> and the packages are still the same
[06:21] <hifi> (not counting the toolchain)
[07:21] <pitti> Good morning
[07:29] <ajmitch> morning pitti
[07:44] <\sh> moins
[07:48] <dholbach> Good morning! :)
[07:50] <jsgotangco> dholbach: good night :)
[07:51] <dholbach> hey jsgotangco
[07:51] <dholbach> long time no see :)
[07:52] <ajmitch> very long time, how are you?
[07:52] <jsgotangco> yep startup work kept me out of irc
[07:54] <jsgotangco> dholbach: i could have joined UDS now if i learned the dates sooner
[07:54] <dholbach> jsgotangco, ugh... hopefully next time - it'd be great to see you again!
[07:55] <jsgotangco> dholbach: i'm actually in the US now but have already scheduled some stuff during those dates
[07:55] <dholbach> ahh ok
[07:55] <dholbach> hey shang
[07:55] <shang> dholbach: hey!!!
[07:56] <shang> dholbach: how's going?!
[07:56] <dholbach> shang, how are you doing?
[07:56] <jsgotangco> dholbach: i dunno probably if you'll be in LA anytime after that
[07:56] <dholbach> jsgotangco, there's no LA plans right now :)
[07:56] <shang> dholbach: I am doing alright~ Congrats to the new release ~
[07:56] <jsgotangco> hehe
[07:56] <shang> dholbach: how about u? how's everything going for ya?
[07:57] <dholbach> shang, very good very good - it's just ....ing cold here :)
[07:57] <shang> dholbach: LOL, already?!
[07:57] <dholbach> yeah, it's down to 4°C already
[07:58] <jsgotangco> wow
[07:58] <shang> dholbach: come visit Taiwan then, 30 right now (feels like 42)
[07:58] <dholbach> holy cow :)
[07:58] <shang> dholbach: wow, that is kind ...ing cold!!
[07:58] <dholbach> sounds much better :)
[07:59] <shang> I am not sure about better, but HOTTER for sure!!
[07:59] <shang> :D
[07:59] <jsgotangco> and humid
[07:59] <dholbach> doko_, are we there yet? :)
[08:00] <persia> dholbach, No.
[08:00] <doko_> ?
[08:00] <dholbach> doko_, I was just checking what was going on with natty :)
[08:01] <shang> humid is about right!!
[08:01] <doko_> no new gnome, so everything is fine
[08:01] <dholbach> doko_, not yet
[08:19] <majeru> hi there, I'm having a problem with 10.10 on my Dell T3500. it constaltly panics with the default 10.10 kernel
[08:19] <majeru> the 10.04 kernel works fine
[08:19] <persia> majeru, Support is in #ubuntu, help tracking down bugs in #ubuntu-bugs
[08:20] <majeru> persia: I asked in Ubuntu a few days ago about this issue, it was a lot of noise and noone answered
[08:21] <majeru> I'll try #ubuntu-bugs, though
[08:21] <majeru> thanks
[09:13] <cjwatson> RoAkSoAx: that's normal around releases.  but we can probably put it back now ...
[09:16] <cjwatson> RoAkSoAx: (done)
[09:25] <nigelb> g28
[09:37] <ChrisH> I was asked from a friend on the option running ubuntu-mobile on a simvalley MOBILE XP-25 (currently installed with WM6). She is not an expert in Linux but using ubuntu on her Desktop for a longer time very happy. Any experience on this specific device? Or an URL to find find hints on ubuntu-mobile on specific devices.?
[09:51] <persia> ChrisH, I'll recommend not attempting to run ubuntu-mobile anywhere.  Nobody is currently supporting it.
[09:51] <persia> If you need a phone UI, the current best selection is kubuntu-mobile.
[09:53] <persia> But that phone can't run current Ubuntu anyway: we no longer support that processor.
[09:53] <persia> For future support requests, I'll recommend #ubuntu for general stuff, and #ubuntu-arm for ARM-architecture-specific questions.
[09:54] <ChrisH> persia: Thanks for that feedback. So the sum-up: She needs to stay with WM6 as this old HW/CPU is no longer supported.
[09:54] <persia> Not in Ubuntu.  Might be for OE or Debian.  I have no familiarity with that specific device.
[09:55] <ChrisH> ubuntu-mobile pointed to ubuntu-devel as followp, thats the reason I am asking here.
[09:55] <persia> Yep.  I don't fault you asking here for that reason: most folk asking for support would get shunted to #ubuntu immediately.
[10:17] <hyperair> urgh. something happened to pulseaudio between lucid and maverick and now i'm getting superb underrun problems whenever system load goes up
[10:19] <persia> Are you sure it was pulse, and not ALSA or the kernel?
[10:19] <persia> Maybe test with JACK to help isolate?
[10:21] <hyperair> persia: it's a custom kernel which hasn't changed since my lucid install.
[10:21] <hyperair> persia: i've merged in alsa-next things during my last build
[10:22] <persia> And you're also maintaining local ALSA userspace?
[10:22] <hyperair> no i'm not.
[10:22] <hyperair> hmm should i?
[10:22] <hyperair> it didn't cause problems with lucid, which should have an older alsa userspace.
[10:22] <persia> If you're maintaining a special ALSA kernelspace setup, I'd think it'd make sense to stay in sync.
[10:23] <hyperair> hrm
[10:23] <diwic> a newer kernel than userspace shouldn't pose a problem
[10:23] <hyperair> i didn't think it would make a difference though
[10:25] <persia> diwic, Theoretically :)  We've had issues with that before which led to a decision to continue to update the userspace stuff up through KernelFreeze rather than just FeatureFreeze.
[10:25] <hyperair> =\
[10:25] <diwic> for underrun problems you can make a PA verbose log to see if the underrun is between app -> PA or PA -> ALSA
[10:26] <diwic> persia, okay, I assume there are always bugfixes we need to pull in
[10:27] <persia> diwic, Basically, yeah.  Most of the upstream development is roughly in sync, so sometimes something gets fixed half here and half there, etc.
[10:28] <persia> (and getting half a fix often results in a regression, because the one expects things the other doesn't supply)
[10:50]  * doko curses 1pixel wide resize borders
[10:50] <ion> doko: Super+middle mouse button
[10:50] <ion> They should scrap the borders altogether whenever shadows are available.
[10:52] <persia> ion, That pushes windows to the back of the stack for me.
[10:54] <pitti> persia: alt+middle mouse (resize) and alt+left mouse (move) WFM
[10:54] <pitti> but on a laptop, middle mouse is no easier than trying to grab a window border with a touchpad
[10:54] <pitti> so for resizing you are doomed on a laptop either way
[10:54] <ion> Whoops, alt indeed.
[10:55] <ion> pitti: alt-F8
[10:55] <pitti> ah
[10:56] <persia> pitti, Ah, yes.  Alt+ works fine.  Super+ less so.
[10:56]  * persia usually just uses Alt+space to get a useful menu
[10:57] <persia> And Alt+space works for *any* pointer device you like :)
[13:44] <bilalakhtar> Hi ari-tczew
[13:44] <ari-tczew> hi bilalakhtar
[13:45] <bilalakhtar> So as it was discussed yesterday, at the most Natty should be open my Friday, right?
[13:45] <bilalakhtar> *by
[13:45] <cjwatson> yes, I would expect so
[13:46] <persia> It's really an unknowable date, but "soon", as it depends on everything actually working as the base is set.  Used to take 2-3 weeks, so this time is fast, really.
[13:47] <cjwatson> it hasn't taken 2-3 weeks for a long time.
[13:47] <cjwatson> I posted the figures for the last several releases here a day or two ago.
[13:47]  * soren is still impressed when it's less than that.
[13:47] <persia> True.
[13:47]  * persia too
[13:47] <tgardner> Does soyuz have a known issue? I can't get any of the normal package info from https://edge.launchpad.net/ubuntu/+source/linux-lts-backport-maverick
[13:48] <cjwatson> tgardner: not one I've seen before
[13:48] <cjwatson> I don't know what's up there
[13:49] <tgardner> cjwatson, whom should I point at it?
[13:49] <cjwatson> bugs.launchpad.net/soyuz
[13:49] <wgrant> tgardner, cjwatson: The info there only updates daily.
[13:49] <wgrant> Oh.
[13:49] <wgrant> Another issue.
[13:49] <persia> And this package hit the bad time?
[13:50] <wgrant> That is an odd one.
[13:52] <wgrant> tgardner: For now you want https://edge.launchpad.net/ubuntu/+archive/primary/+sourcepub/1333666/+listing-archive-extra
[13:52] <wgrant> Not sure exactly what has gone wrong, though.
[13:52] <tgardner> wgrant, just file bug #659882
[13:52] <tgardner> filed*
[13:53] <wgrant> tgardner: Do you mean the list of binaries that appears at the top of the page, or the broken expander next to the package version?
[13:53] <tgardner> cjwatson, since you're the morning archive admin according to the wiki, I assume you'll process the maverick NEW queue sometime today?
[13:54] <tgardner> wgrant, both
[13:54] <cjwatson> sucks to be me
[13:54] <nigelb> heh
[13:55] <wgrant> tgardner: So, they're separate issues.
[13:55] <wgrant> tgardner: The broken expander is because it exists only in PROPOSED.
[13:55] <tgardner> wgrant, from a naive user point of view, they are one and the same.
[13:55] <wgrant> The missing binary list is probably just because it is new, and the cron job hasn't cached its data yet.
[13:55] <wgrant> Probably, yes.
[13:56] <tgardner> wgrant, as for the binaries, its been over 24 hours since it was published.
[13:57] <cjwatson> tgardner: linux-linaro/maverick-proposed/armel accepted
[13:57] <wgrant> tgardner: Ah, OK, got it.
[13:58] <wgrant> That one is a bit of both.
[13:58] <wgrant> Sigh.
[13:58] <tgardner> cjwatson, thanks. I was actually more interested in the lts meta package escaping purgatory
[13:58] <cjwatson> oh, well, you said NEW, that one's in UNAPPROVED
[13:58] <cjwatson> but I can look at that too
[13:59] <tgardner> hmm, guess I should become aware of the difference between the 2 queues
[14:01] <cjwatson> wait, I don't see the LTS metapackage anywhere
[14:01] <cjwatson> current state is that maverick-proposed NEW is empty; UNAPPROVED has five items, cluster-glue, ubuntu-sso-client, simple-scan, xfce4-indicator-plugin, and linux-meta-linaro
[14:02] <tgardner> cjwatson, I wonder if soyuz gobbled it up. I'll re-upload i a minute.
[14:03] <cjwatson> tgardner: oh, wait, never mind.  it's the *lucid-proposed* NEW queue, of course
[14:03] <cjwatson> wouldn't make sense for it to be in maverick :)
[14:03] <tgardner> cjwatson, right. sorry if I wasn't clear.
[14:29]  * ari-tczew is still waiting for opened natty.
[14:29] <Keybuk> ARE WE THERE YET?
[14:29]  * cjwatson passes ari-tczew an ice-cream
[14:30] <ari-tczew> cjwatson: why ice-cream? :P
[14:30] <cjwatson> "are we there yet?"  "can I have an ice-cream" :-)
[14:30] <ari-tczew> oh, Keybuk. are you still maintainer of MoM?
[14:30] <Keybuk> no...
[14:30] <cjwatson> currently waiting for linux to finish building so that we have a fresh linux-libc-dev; then test-build something against that to make sure the world hasn't collapsed; then open if it works
[14:37] <jdstrand> cjwatson: hi! is it ok to pocket copy things to natty now, or should I wait until natty opens?
[14:38]  * jdstrand may get an ice-cream for that question
[14:38] <cjwatson> jdstrand: if the copy is with binaries, it's ok
[14:38] <cjwatson> I already did that for a few things
[14:38] <jdstrand> cjwatson: cool, thanks
[14:38] <cjwatson> which packages?
[14:39] <jdstrand> cjwatson: virtinst and vm-builder, when they are done building
[14:39] <cjwatson> from -security or -updates, I take it?
[14:39] <jdstrand> well, -proposed actually
[14:39] <cjwatson> hm, do we have to copy from -proposed?
[14:39] <cjwatson> I guess if you're keeping an eye on it
[14:40] <jdstrand> no, we don't. though as you said, I am keeping an eye on it
[14:40] <jdstrand> (a very close one I might add)
[14:40] <cjwatson> ok then
[14:41] <cjwatson> incidentally, re ice-cream, security's monopolisation of powerpc buildds is slowing natty opening up by several hours ;-)
[14:41] <jdstrand> heh
[14:41] <jdstrand> well, tbh, those particularly builds originated from people outside of our team
[14:41]  * cjwatson improves his life with  bzr alias build-merge="bd -S --package-merge"
[14:42] <jdstrand> s/particularly/particular/
[14:44] <chrisccoulson> cjwatson, sorry about that :(
[14:44] <chrisccoulson> (taking over the buildd's)
[14:45] <jdstrand> what a weird error message from scp:
[14:45] <jdstrand> $ scp -r /tmp/foo sec-maverick-amd64.:/tmp1/
[14:45] <jdstrand> scp: /tmp1/: Is a directory
[14:46] <jdstrand> it actually is *not* a directory...
[14:46] <jdstrand> (it doesn't exist)
[14:47] <Chipzz> jdstrand: but that behaviour shouldn't surprise you?
[14:47] <Chipzz> even if the error message isn't exactly clear
[14:49] <jdstrand> Chipzz: the behavior no. the error message telling that /tmp1 is a directory when it isn't, yes
[14:49] <cjwatson> it's actually from open()
[14:49] <cjwatson> 21548 open("/nonexistent/", O_WRONLY|O_CREAT|O_LARGEFILE, 0755) = -1 EISDIR (Is a directory)
[14:49] <cjwatson> man page says:
[14:49] <cjwatson>        EISDIR pathname refers to a directory and the access requested involved
[14:49] <cjwatson>               writing (that is, O_WRONLY or O_RDWR is set).
[14:49] <cjwatson> so evidently the kernel checks that before it checks whether it exists
[14:49] <cjwatson> not really directly scp's fault
[14:50] <cjwatson> well, maybe it is, it's using O_CREAT of course
[14:51] <cjwatson> https://bugzilla.mindrot.org/show_bug.cgi?id=1768
[14:51] <cjwatson> heh, forwarded by me so I should have known ;-)
[14:51] <jdstrand> hehe
[14:51] <jdstrand> it certainly isn't a devastating bug, which is why I only mentioned it in passing :)
[14:51] <cjwatson> I attached a patch there, but would prefer to wait for upstream to review/apply it
[14:52] <amikrop> Hello, since I installed the proprietary nVidia drivers, my boot splash image disappeared, the boot resolution got too low, and I get ugly big letters instead. So, I installed startupmanager to fix that. But when I set resolution 1600x1200 (and other options such as "use splash image" and "no text during boot") I get a "out of sync" from my screen instead of the boot logo. Any help, please? What can I set as options to startup manager?
[14:52] <amikrop>  to get my old nice boot splash graphics back? My screen resolution is 1920x1080.
[14:55] <Keybuk> amikrop: if you want hi-res graphics, don't use the proprietary nvidia drivers
[14:56] <amikrop> Keybuk: I have to. Can't I have a nice boot logo? I have big ugly letters instead (which are out of correct order, too).
[14:57] <Keybuk> no
[15:15] <ari-tczew> amikrop: might be your issue bug 653274
[15:17] <amikrop> ari-tczew: thanks, I 'll have a look :)
[15:19] <amikrop> ari-tczew: so, do you think that will help? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/653274/comments/13
[15:21] <ari-tczew> amikrop: I didn't use this one, so I won't give a warranty.
[15:21] <ari-tczew> you can use this one on your responsibility
[15:21] <amikrop> ari-tczew: which one did you use?
[15:22] <ari-tczew> amikrop: nothing. I still have ugly plymouth screen.
[15:24] <amikrop> ari-tczew: Every nVidia & Ubuntu user does, right? That is about 1/2 of Ubuntu users. Isn
[15:24] <amikrop> Isn't that a critical bug?
[15:24] <amikrop> It looks unprofessional and broken.
[15:25] <Riddell> mdke: do you know how to get docs translations from po files to docbook?
[15:26] <ari-tczew> amikrop: probably it's related to closed nVidia drivers. IMO it's high priority bug (not critical) and I agree, that a huge of Ubuntu users use this drivers, though Jockey suggests automatically instalation these drivers.
[15:27] <ari-tczew> but core developers think that this bug is not in their responsibility.
[15:27] <pitti> it's got little to do with "think"
[15:27] <pitti> it's a closed-source driver
[15:27] <pitti> we can't modify it
[15:28] <ari-tczew> pitti: so bug should be reported upstream, right?
[15:28] <pitti> ari-tczew: they are well aware of KMS
[15:28] <pitti> but they won't/can't switch to it
[15:28] <pitti> because of licensing issue
[15:28] <pitti> (the kernel APIs necessary for this are GPL only, as far as I remember)
[15:29] <ari-tczew> pitti: so release maverick with that ugly element - booting step making bad feedback about Ubuntu.
[15:29] <ari-tczew> and Canonical should do everything to workaround this problem
[15:29] <amikrop> pitti: I agree :S
[15:30]  * pitti pats his intel card
[15:30] <amikrop> it's very bad marketing, if anything
[15:30] <amikrop> pitti: since there are workarounds (tinker with startupmanager or vga=xxx boot option) why couldn't they be default?
[15:31] <amikrop> I mean, such options should be added automatically by the installation of the nvidia package
[15:31] <pitti> they could, presumably
[15:31] <cjwatson> the problem with setting a non-VGA-text graphics mode in GRUB is that it causes quite a few systems to oops at boot
[15:32] <amikrop> pitti: It would be very good if they would
[15:32] <cjwatson> we tried, and had to back it out
[15:32] <tseliot> pitti: if the bootsplash is the problem, then Nvidia should just provide an fb device, no need for KMS
[15:32] <cjwatson> we'll try again, but it's reliant on kernel improvements
[15:33] <cjwatson> so, as ever, it's not quite that simple ...
[15:39] <amikrop> cjwatson: could you please help me set startupmanager if I tell you some information about my screen, resolution, etc?
[15:39] <apw> cjwatson, is your team aware of this blueprint: https://blueprints.edge.launchpad.net/burg/+spec/burg-as-default-bootloader
[15:40] <cjwatson> apw: it doesn't surprise me, but I'm not interested
[15:40] <cjwatson> burg is very much less well-maintained
[15:40] <apw> cjwatson, fair enough indeed
[15:41] <cjwatson> amikrop: no, I don't know enough about nvidia, sorry
[15:41] <tgardner> that, and we've just barely gotten onto grub2.
[15:41] <cjwatson> burg is a one-man fork by a developer who couldn't work with the grub2 team
[15:42] <cjwatson> it has one or two appealing features which have got people interested, but it's better to work on grub2 which has a development team and a future
[15:43] <apw> works for me
[15:43] <amikrop> cjwatson: who could help me? I am basically looking for what to set to StartUp-Manager's Display->Resolution, Display->Color Depth and Advanced->Bootloader menu resolution as values. My screen resolution is 1920x1080 and depth color (I think) 24
[15:43] <cjwatson> amikrop: I'm afraid I don't know, sorry
[15:44] <amikrop> apw: could you help me, please?
[15:44] <cjwatson> you could ask by methods other than IRC (e.g. askubuntu.com, the forums, ...)
[15:44] <amikrop> cjwatson: aha
[15:44] <cjwatson> asking on IRC is an "I hope there's somebody around in this channel right now who knows the answer" kind of deal
[15:46] <apw> amikrop, yeah i have never used startup manager
[15:46] <apw> is the effort worth it?  it can only be there for a few seconds
[15:48] <amikrop> apw: I would like to see a nice graphic for a few seconds, than some big ugly displaced letters. There are only for a few seconds there, but they are there on every boot. That is, thousands of seconds, summed up :/
[15:49] <amikrop> Anyway, I 'll try to tinker with StartUp-Manager. Thanks, everybody.
[16:02] <slangasek> persia: megabyte changelog files> yeah, I know :/
[16:24] <amikrop> Hmm, can't I find the Plymouth options nouveau used, and apply them now (to the proprietary drivers), as well?
[16:41] <night_fox1> Hello! I'm doing this project which uses object recognition and classification in images to automatically create metadata, which can then be used to search a collection of images. It seems as though the best way to implement this would be as part of an existing search tool, like Tracker. So, I what the situation is in terms of gnome search tools in ubuntu, and if the ubuntu developers were...
[16:41] <night_fox1> ...considering maybe introducing another search tool in a future version?
[16:42] <night_fox1> Sorry, the start of that last sentence should have read "So, I was wondering what the situation is..."
[16:53] <night_fox1> hello?
[17:14] <lool> doko: Hey, I'm merging newlib and I think we can drop the override of confargs_spu; mind confirming?  The new rules look like this http://paste.ubuntu.com/512471/ and I think the first confargs_spu from Debian is actually ok; would you confirm?  (especially --target=/--program-prefix=; the rest definitely seems correct)
[17:52] <doko> lool: can you check with a build on davis that it does build? debian newlib changes didn't always work out well
[17:57] <lool> doko: I tried kicking a build in a non-virtual PPA
[17:58] <lool> but for some reason my upload didn't reach it
[17:58] <lool> I wonder whether uploads to natty PPAs work already
[17:58] <ogra_ac> lool, TI complains too
[17:58] <ogra_ac> (about maverick packages though)
[17:59] <lool> ogra_ac: What's happening for them?
[17:59] <ogra_ac> there might be a general issue with arm PPAs
[17:59] <ogra_ac> nothing, see #ubuntu-arm
[17:59] <slangasek> doko: are there any blueprints for UDS-N about toolchain version selection?
[18:00] <slangasek> doko: I'm assuming there needs to be an ongoing discussion about whether Ubuntu should use the Linaro GCC builds, and that it's not a foregone conclusion :)
[18:01] <lool> ogra_ac: They seem to mention that builds don't start; my upload isn't even accepted here
[18:01] <doko> slangasek: no, just going forward with 4.5 now. I think it's late for 4.5, but yes, we should have an evaluation what to do with 4.6. maybe 4.4 linaro was a special case because it had the whole cs patches too
[18:02] <slangasek> doko: when you say "late for 4.5", what do you mean?  Do you mean it's too late for Ubuntu to take the Linaro patches for gcc 4.5?
[18:03] <lool> actually I have an error message:
[18:03] <lool> Cannot build any of the architectures requested: i386 amd64 armel ia64 powerpc
[18:03] <lool> sparc ppc64 all
[18:04] <doko> slangasek: well, already started with 4.5 linaro for natty, and we had the linaro bits in maverick too
[18:05] <doko> anyway, afk now
[18:05] <slangasek> doko: oh, so the patches are already there so there's nothing to discuss? :-)
[18:05] <slangasek> doko: ok, cheers
[18:06] <doko> slangasek: there is, for 4.6, and there are definitely changes in the branches which are non-optimization changes
[18:10] <slangasek> doko: ack
[18:28] <smoser> stgraber, around ?
[18:57] <jdstrand> cjwatson, pitti, slangasek, kirkland, james_w`, Riddell, StevenK: fyi-- as per the kernel-team@ mailing list, there is a backported maverick kernel in lucid-proposed now. I wanted to bring to your attention bug #660077. This bug is for an apparmor SRU that needs to be pushed before/at the same time as the lucid-proposed backported kernel
[19:25] <highvoltage> ● Edubuntu Meeting in about 30 minutes
[19:31] <highvoltage> (oops, I just realised I pasted that here, it was meant for another channel)
[21:45] <ScottK> jcastro: Does it take some special magic to get LP to update status from remote Bugzillas?  It looks like we aren't getting updates from the clamav bugzila.
[21:46] <jcastro> the bugwatch could be broken
[21:46] <jcastro> it's supposed to be automagic
[21:46] <jcastro> deryckh on #launchpad should know for sure
[21:47] <lifeless> we're about to do an LP upgrade
[21:47] <lifeless> you will want to wait for after that :)
[21:48] <lifeless> ScottK: older bugzillas need a plugin, newer ones have it built in, and LP need an account on the bugzilla
[21:49] <ScottK> lifeless: Is there some LP person who can investigate such things?
[21:49] <ScottK> (I'm certainly not in a position to make LP accounts on remote bug trackers)
[21:50] <lifeless> ScottK: I suggest filing a question on answers.lp.net/malone
[21:50] <ScottK> lifeless: Will do.  Thanks.
[21:50] <lifeless> ScottK: that will end up with folk that know fairly quickly.
[21:51] <ScottK> Thanks.
[22:17] <Chex> third times the charm.
[22:23] <BUGabundo> spammer
[22:23] <BUGabundo> :)
[22:43] <Amaranth> Is it just me or is launchpad logging everyone out after about 5 minutes?
[22:43] <BUGabundo> no idea
[22:43] <micahg> Amaranth: launchpad is about to undergo an upgrade
[22:44] <Amaranth> micahg: Did they break something with the last one? This has been happening for some time now
[22:44] <micahg> Amaranth: are you on edge?
[22:44] <Amaranth> micahg: Yeah
[22:45] <micahg> Amaranth: I've noticed some session issues recently, but I'm hoping they'll be fixed with this release
[22:45] <Amaranth> it boots me off non-edge too
[22:45] <Amaranth> Otherwise when I go to non-edge it would have automatically redirected me to edge
[22:45] <micahg> Amaranth: me too, there was some type of notice of consolidating edge/production into 1 URL, but idk when that'll happen
[22:48] <Amaranth> What the hell
[22:48] <Amaranth> I just logged in on one bug then opened another and it wasn't logged in...
[22:48] <Amaranth> Oh well, if it's still broken after the upgrade I'll file a bug or something
[22:59] <wgrant> Amaranth: I've seen some reports of this happening to some users since the DB maintenance last week. But only a couple.
[23:00] <wgrant> (everyone's sessions were dropped last Wednesday and Thursday, but some have apparently been having subsequent issues)
[23:00] <wgrant> If you still see strangeness after the release, please file a bug.
[23:01] <Amaranth> wgrant: How long is a session supposed to last?
[23:01] <wgrant> Amaranth: A year, I think, except when the session DB is cleared.
[23:02] <Amaranth> Ok, I know it has been less than that for me for longer than a week
[23:02] <wgrant> Odd. I remain logged in for months without trouble.
[23:51] <replicasex> Hey guys, really quick question and I'll be out.  Is the new version of xorg currently in 10.10 going to be pushed to 10.04?  Because it didn't play well with my system and the nvidia driver, just wondering if I'll have to watch out for that update.
[23:52] <ion> It won’t. That’s pretty much the point of stable releases.
[23:53] <replicasex> ion, thank you very much.  I really appreciate the ubuntu community :D  I'll let you get on with your day