[00:02]  * Chipzz feels a very strong urge to break the CoC wrt fargiolas
[00:02] <Chipzz> *bleep* *bleep* *bleeeeeeeeep*
[00:03] <cjwatson> Chipzz: I would appreciate it if you put an end to your comments on the subject here
[00:03] <Chipzz> cjwatson: ^^^ I censored myself :)
[00:03] <cjwatson> I responded because I was addressed. You were not
[01:02] <Aquina> hy
[01:49] <ScottK> I wish if someone were going to do a complete giveback of all the build failures in the archive (I think that's what's happened) they'd have given some warning.  I certainly wouldn't have spent all the time over the last 3 week carefully picking through for retries worth doing.
[01:54] <ScottK> If LP is at all right this'll take two weeks to build out.
[01:55] <wgrant> ScottK: Keep in mind that lots of stuff will likely fail early.
[01:55] <ScottK> True.
[01:55] <ScottK> I realize it'll likely be much less.
[01:55] <wgrant> And hppa and sparc are special.
[01:56] <ScottK> Actually I think most of what's there will fail.  I wasn't kidding about spending the last 3 weeks going through failures looking for stuff to retry.
[01:56] <ScottK> Just finished today.
[01:56] <wgrant> Oh wow. That's a lot of queued builds...
[01:57] <ScottK> Yes.  It's a retry on every single FTBFS for Jaunty.
[01:57] <directhex> any way to abort the attempted rebuilds?
[01:57] <wgrant> Not without SQL access.
[01:58] <bluefoxicy> is it possible to package VirtualBox OSE on Ubuntu CDs such that they run from INSIDE WINDOWS when you pop them in?
[01:58] <ScottK> https://launchpad.net/ubuntu/jaunty/+builds?build_text=&build_state=failed doesn't know about a FTBFS more than ~1 hour old.
[01:58] <bluefoxicy> seeing as QT is GPL now
[01:58] <directhex> bluefoxicy, not sensibly. need drivers & reboots to install virtualbox on windows
[01:59] <ScottK> bluefoxicy: Qt has been GPL for year.
[01:59] <ScottK> years even.
[01:59] <bluefoxicy> scottK:  It's always had a restrictive Windows license
[01:59] <ScottK> bluefoxicy: How is that even possible.
[01:59] <bluefoxicy> Well, a commercial entity controlled Qt
[01:59] <ScottK> It can't be GPL unless you run Windows.
[02:00] <ScottK> That's not GPL.
[02:00] <bluefoxicy> so they published the Linux version as GPL, and patched it to run on Windows but only distributed binaries of that, under a restrictive license
[02:00] <ScottK> I suspect what you're thinking of is it's now LGPL.
[02:00] <bluefoxicy> possibly
[02:00] <ScottK> I don't think so.
[02:00] <bluefoxicy> my brain may be busted.
[02:00] <ScottK> You can run KDE on Windows with no problem.
[02:00] <bluefoxicy> I know the Linux version had a different license
[02:00] <directhex> ScottK, the qt3 license certainly used to be gpl-or-proprietary, with the windows port only available as proprietary. there were efforts to port the gpl version, but they, erm, sucked
[02:01] <ScottK> OK.  Qt3 is not been developed in a long time.
[02:01] <directhex> didn't say it was. just sayin'...
[02:01] <ScottK> For Qt3 I think you're correct.
[02:01] <bluefoxicy> directhex:  also there's lots of install-and-run software (openoffice) on the Ubuntu CDs
[02:01] <bluefoxicy> wouldn't installing a driver fall under install-and-run?
[02:02] <ScottK> Licensing for Qt3 hasn't changed.
[02:02] <bluefoxicy> and preconfigure the installed VBox to have a "boot LiveCD with 384M RAM" option
[02:02] <ScottK> Licensing for Qt4.4 hasn't changed either.  LGPL is only Qt4.5.
[02:04]  * ScottK isn't kidding about being disheartened about a couple of dozen hours of work over the last several weeks turning out to be totally unnecessary.
[02:05] <directhex> the blanket rebuild must've been queued y someone who doesn't pay their server power bills
[02:08] <ScottK> This does cause some actual problems for how we'd planned on doing the KDE 4.2.1 upload next week.
[02:08] <ScottK> Urgh.
[02:12] <ScottK> So far 2 successes, 252 failures.
[02:13] <directhex> ScottK, totally worthwhile!
[02:15] <wgrant> ScottK: How do you calculate that?
[02:15] <wgrant> There's no way to sort builds lists, AFAICT.
[02:16] <wgrant> Ah, through +history?
[02:16] <ScottK> https://launchpad.net/ubuntu/jaunty/+builds?build_text=&build_state=built and python-cjson was a fresh upload.
[02:16] <ScottK> Any success after that is the retries
[02:16] <Aquina> Short westion: Where are these outputs on system startup generated? I wanna modify them.
[02:17] <ScottK> And then all of https://launchpad.net/ubuntu/jaunty/+builds?build_text=&build_state=failed are from the retries
[02:17] <wgrant> There's nothing after that.
[02:17] <wgrant> Oh. WTF.
[02:17] <wgrant> Why does it sort differently depending on the filter?
[02:18] <Aquina> (posted in #ubuntu before): Someone knows where the usplash messages come from? I removed the parameter "quiet" from defoptions ind menu.lst. I searched through all the /etc/init.d/ scripts but couldnt find these messages printed. Search engines didn't help. Please do you...
[02:18] <wgrant> Compare state=built and state=all.
[02:18] <ScottK> It's interesting that the time sort isn't correct.
[02:18] <wgrant> Which time sort?
[02:19] <wgrant> AFAICT for state != all, the key is start time.
[02:19] <wgrant> For state == all, the key is queue time.
[02:19] <wgrant> (I think)(
[02:19] <ScottK> The failed ones were not entirely in time sequence
[02:20] <ScottK> All doesn't seem to show failures.
[02:20] <ScottK> Ah.  That'd make sort of sense.
[02:21] <wgrant> I think it does.
[02:21] <wgrant> But nothing queued recently has failed.
[02:21] <ScottK> BTW, every one of the build failures will land in one or two inboxes too.
[02:21] <wgrant> Oh yes, I know this well.
[02:21] <ScottK> I wonder if this is revenge for me filing a bug about notification of translations success spamming my inbox.
[02:22] <StevenK> I seriously doubt that
[02:22]  * ScottK was kidding
[02:22] <wgrant> Even I have to doubt that :P
[02:22] <ScottK> StevenK: Do you know why this was done?
[02:23] <wgrant> Mass-givebacks happen.
[02:23] <StevenK> What wgrant said
[02:23] <wgrant> Frequently.
[02:23] <ScottK> BTW, I was looking at the failures wrong.  They are sorted by fail time.
[02:23] <StevenK> Mass-givebacks are done at points throughout the cycle
[02:28]  * wgrant likes how the distribution build failure list is preceded by empty build records created by the unembargoing process.
[02:34] <mluser-home> Anyone know how I can disable pulseaudio system wide?
[02:34] <wgrant> mluser-home: This is not the correct channel.
[02:35] <mluser-home> wgrant: sorry
[02:35] <wgrant> You want #ubuntu, or to realise that you don't want to disable PulseAudio system wide.
[02:35] <mluser-home> I'm having this problem in Jaunty, and I thought #ubuntu was just for hardy and intrepid
[02:35] <wgrant> #ubuntu+1, then.
[02:36] <mluser-home> wgrant: thanks again
[02:36] <wgrant> np
[03:33] <calc> bryce: i don't think bug 322202 is UXA specifc
[03:48] <jdong_> installer gods: We should have a brown-and-orange color scheme for the alt installer :)
[03:54] <LaserJock> heck yeah
[03:55] <jdong_> dear virtualbox: Please stop turning green when I resize you.
[04:00] <jdong_> whee relabel ahoy
[05:37] <Codd> I just installed jaunty Alpha 5 on my machine (clean install) and I'm noticing that every once in a while cpu usage spikes for just a second and everything locks up (GUI, background tasks,mp3 playing, video, downloads) and then it all returns to normal.  If I load a complex ajax page in firefox the cpu still goes upto 99% but I don't get a lock up,   Right now it seems to occur when I play media files (xvid, mp3) I formatted usin
[05:40] <dtchen_> Codd: if the symptom is persistent when playing/recording audio, there's a known issue in the current jaunty pulseaudio package causing the daemon to spin in a tight loop due to bogus data being passed from the sound driver. it has been fixed in a bzr branch and will land in the next upload.
[05:47] <Codd> dtchen_: sweet it does look like pulseaudio is bouncing around alot in top, I guess since the system was freezing up I didn't see it peak :)  I'm loving the new release though, keep up the amazing work!
[06:14] <calc> anyone know of an easy way to determine how much space on a disk a certain file type is taking up?
[06:15] <calc> eg all jpg's, etc
[06:41] <Hobbsee> calc: du?
[06:43] <Hobbsee> calc: looks like you want du, -c, and probably a few other switches
[06:43] <calc> i found a script that does it with find and awk
[06:43] <calc> just have to determine how to make it work with spaces in filenames :\
[06:44] <calc> resetting IFS seems to break it too much
[06:48] <calc> cool -print0 and xargs -0 is your friend :)
[07:00] <maco> calc: for dealing with odd characters in filenames: http://calypso.tux.org/pipermail/novalug/2009-February/017524.html
[07:01]  * jdong_ thinks one should not be scripting in such ambiguous languages anyway :)
[07:01] <maco> also, anyone using the sidebar for firefox?
[07:01] <jdong_> anything accepting user input that doesn't take explicit typed-list style arguments is broken for today's environment.
[07:01] <maco> the all-in-one sidebar?
[07:03] <TheMuso> c
[07:04] <jdong_> Open Mailbox ('?' for list):
[07:34] <maco> ah sorry thought i was in #ubuntu+1 before
[08:06] <fargiolas> cjwatson: I usually don't ask for support here. it was a particular case where I needed to know a thing that only the involved ubuntu developer could know so I asked here. I could have probably found the answer myself but I was tired after hours fighting with a broken windows installation and not able to concentrate anymore, this could also explain why I may have seemed unpolite.
[08:15] <fargiolas> cjwatson: also I still believe it was not a support question. It was more a question about an ubuntu-specific implementation detail. I'm really sorry I was OT here.. I did it in good faith.
[08:17] <cjwatson> let's call an end to it :)
[08:18]  * cjwatson doesn't really want to continue the argument
[08:18] <fargiolas> cjwatson: me neither :)
[10:03] <savvas> hi, which is the default administration group? adm?
[10:31] <ogra> savvas, adm is used for access to logfiles only
[10:32] <savvas> ah thanks
[10:32] <ogra> if you mean the group that has sudo access by default, thats "admin"
[10:32] <savvas> that's it :)
[11:09] <RainCT> doko: Thanks for the tip. I tried to fix that yesterday but didn't get it to work (each build takes half an hour..)
[11:35] <Hobbsee> kirkland: found you a bug.  it's your lucky day!
[11:45] <StevenK> doko: Want to commit/push your changes to launchpad-integration into bzr?
[13:04] <RainCT> Why does notify-osd leave space for an image when there isn't one?
[13:05] <RainCT> the bubble is already small enough as to waste more space like this
[16:22] <kirkland> Hobbsee: ping
[16:22] <kirkland> Hobbsee: Could you try editing /usr/share/screen-profiles/profiles/ubuntu-black
[16:22] <kirkland> and changing "~" to "$HOME", and see if that works?
[16:23] <kirkland> Hobbsee: If so, this is a very easy fix...
[16:34] <ion_> dpkg dependencies don’t allow one to depend on (ruby1.8, libjson-ruby1.8) OR ruby1.9, do they?
[16:35] <directhex> you could work around that with a metapackage
[16:36] <directhex> i.e. myapp-ruby1.8 | ruby1.9, where myapp-ruby1.8 has no contents & only a dep on ruby1.8, libjson-ruby1.8
[16:36] <directhex> or wouldn't a dep on libjson-ruby1.8 pull in ruby1.8?
[16:36] <ion_> Nope, only libruby1.8, which doesn’t include the binary.
[17:25] <ilowe> Do Ubuntu devs prefer to receive new packages into Ubuntu or should they go upstream to the Debian repos first?
[17:25] <directhex> ilowe, generally, the latter
[17:26] <ilowe> directhex: thanks; so I should follow the procedure to get the package accepted into Debian and it will just get pulled down into Ubuntu (in theory at some point in the future)?
[17:27] <directhex> ilowe, that's the best way for everyone - so debian & debian-based dists also gain from your work
[17:27] <directhex> ilowe, but delays can sometimes make it a sucky route
[17:28] <ilowe> Cool, thanks. I'll start with that and see how the delays go :)
[17:29] <directhex> ilowe, given where we are now, you have about 5 months for automatic syncing into ubuntu 9.10
[17:30] <ilowe> yikes....it's more an issue of having the package available on my own systems; I guess I'll keep it in my local repos while it makes it's way into Ubuntu
[17:30] <directhex> ilowe, yes, that can work - the ubuntu PPA system allows you to build a personal repo available to everyone
[17:31] <ilowe> hmmm... then, would I propose to Debian *and* upload to a PPA? In which case would I just abandon the package in the PPA once it reaches Ubuntu?
[17:31] <ScottK> Since we're past feature freeze for 9.04 working through Debian now won't actually make it take longer.
[17:32] <ilowe> ScottK: I'm more trying to get a handle on how the repos get updated; not to worried about official releases
[17:32] <directhex> ScottK, right now, i don't know whether i'd agree. NEW is... taking its time. assuming no delays getting as far as NEW
[17:33] <ScottK> directhex: It's also just after a release in Debian, so no suprise.
[17:33] <ScottK> ilowe: If you get your package into Debian it will automatically come into Ubuntu in the next release.
[17:38] <slytherin> are daily iso builds for ports architectures turned off?
[17:40] <Nafallo> I believe so yes.
[17:46] <slytherin> Nafallo: any particular reason?
[17:46] <ScottK> Yes.
[17:46] <Nafallo> slytherin: ports.ubuntu.com have been struggling a bit.
[17:47] <slytherin> oh
[17:47] <ScottK> There was a locking problem that caused all CD builds to fail.
[17:47] <ScottK> So they had to turn off ports.
[17:53] <slytherin> ScottK: thanks for info
[18:24] <ilowe> http://tinyurl.com/dkrvw7 states that the original package name should be <pkg>-<ver> but the resulting name should be <pkg>_<ver>; if I maintain the upstream as well, should I be naming my package <pkg>-<ver> and updating it in the .deb or can I name it <pkg>_<ver>? dh_make chokes on the "_" version when doing the initial debianization
[18:28] <geser> ilowe: the upstream tarball should unpack to <pkgname>-<upstreamversion>
[18:28] <ilowe> geser: thanks
[18:28] <geser> and the tarball itself has to be named <pkgname>_<upstreamversion>.orig.tar.gz
[18:29] <ilowe> OK, but that will get generated by dh_make? I have a proper <pkg>-<ver>.tar.gz file.
[18:29] <geser> the _ is used as separator in package files
[18:29] <geser> ilowe: dh_make will make then a symlink to your <pkg>-<ver>.tar.gz
[18:30] <ilowe> cool, thanks
[19:41] <Notch-1> hi, since i made a loop/raid root filesystem the hibernation stopped working, any idea on where to put loop/raid information to properly restore the system?
[20:53] <NCommander> hey all
[20:54] <jpds> Hey NCommander.
[20:54] <NCommander> hey jpds
[20:54]  * NCommander has just upgraded his VAIO :-)
[20:56] <RainCT> NCommander: upgraded = to Jaunty?
[20:56] <NCommander> RainCT, no, hardware
[20:56] <RainCT> ah
[20:56] <NCommander> Total of 4GB, and a half a TB of disk space :-)
[20:56]  * NCommander is waiting for Xubuntu 9.04 A5 to download 
[20:57] <RainCT> nice :)
[20:58] <NCommander> Yup
[21:07] <hunger> Is there a trick to get fglrx running in jaunty?
[21:08] <stgraber> hunger: no trick, you just need to wait.
[21:08] <hunger> stgraber: Would have been nice to mention that in the release notes of alpha5.
[21:09] <stgraber> "A new XServer, version 1.6, is included in Alpha 4. The binary proprietary fglrx driver is not yet supported for this server and will exhibit various serious issues if run against it. Users of this driver are encouraged to wait or to switch to the open source -ati driver in the meantime. 313027"
[21:09] <stgraber> from the release notes for alpha-5
[21:09] <stgraber> http://www.ubuntu.com/testing/jaunty/alpha5#Known%20issues
[21:11] <hunger> stgraber: Hmmm... you are right. I read the kubuntu release notes. They do not mention this little fact.
[21:14] <DetlefvomBahnhof> hallo
[21:47] <ia> hello. Have someone (from developers) clashed with this bug - https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/335953 ? I asking about it, because would like, that someone from developers check this bug; I think, that problems in interfaces of apps - one of valuable and primary issues, that should be fixed (cause interface - it's a face of distro)
[21:57] <cjwatson> ion_: apply boolean logic. (ruby1.8, libjson-ruby1.8) | ruby1.9 -> ruby1.8 | ruby1.9, libjson-ruby1.8 | ruby1.9