[02:49] <guest345345> Does anyone know if it's possible to use the indicator/notify-osd APIs with the seed JavaScript engine yet?
[02:50] <guest345345> Or can someone point me to the most relevant mailing list?
[02:52] <ohsix> does seed have ctypes? you could cheat ;]
[03:33] <RAOF> craigbarnes: libindicate* has gobject-introspection data, doesn't it?  I'm pretty sure seed can load any introspectable library.
[09:42]  * persia notes that one can also do amd64 builds on an i386 install using qemu, but that this is painfully slow, and ought be avoided unless one has a very good reason.
[14:56] <bluefoxicy> what in the friggin hell
[14:56]  * bluefoxicy burns launchpad down
[14:56] <bluefoxicy> ?no-redirect okay.
[16:26] <maco> bdrung_: sorry about that. i woke up this morning and realised i needed to double-check that branch
[16:27] <bdrung_> np
[17:26] <shadeslayer> doko_: around?
[17:31] <shadeslayer> doko_: just wanted to confirm if the toolkit is broken, someone told me you uploaded a gcc build, and i can't seem to build a package ( http://paste.ubuntu.com/611482/ << Build log (
[18:51] <geser> shadeslayer: is your used mirror uptodate? gcc-4.6 build on all architectures successfully
[19:35] <leex> hi
[19:35] <highvoltage> hi leex
[19:38] <leex> I am currently trying to install ubuntu 11.04 on my machine, but it fails with the rather generic error message: A step failed. Select and Install Software. What should I do? How can I see which package fails? Btw. I am using cryptsetup to decrypt my disks before entering the partitioner. this error happens with both the alternate amd64 daily and alternate amd64 "stable" iso. any hint on how to fix it would be welcome
[19:39] <highvoltage> perhaps that question is better suited for #ubuntu, you can also get help there on filing bugs, if required
[19:41] <leex> highvoltage: hmm, I posted my question there like 4 times the last 2 days on got no (let me put it nicely: helping) reply
[19:41] <holstein> leex: you can try #ubuntu-beginners if #ubuntu is too busy... this is just not that kind of support channel
[19:42] <leex> holstein: k
[19:42] <leex> I will, sorry for bothering u guys
[19:42] <holstein> no worries
[19:43] <highvoltage> leex: I haven't used it myself, but I'm told that askubuntu.com is fast and very helpful
[19:52] <leex> bb
[19:57] <slangasek> bryce, tjaalton: any reason against merging libx11 and friends from unstable?  I think this should be orthogonal to the X server decision for oneiric, but X has surprised me before :)
[20:33] <djustice> question, a binutils change/update was just pushed, how can i see which repo it was changed in? and how can i see the reason/actual change? besides apt-get source binutils -> debian/changelog i mean..
[20:33] <persia> How do you mean "which repo"?
[20:33] <djustice> no problems, just curious about the information's whereabouts.
[20:34] <djustice> eg, was it pushed as a security change or a normal update?
[20:34] <Ampelbein> djustice: do you mean something like 'aptitude changelog <packagename>'?
[20:35] <persia> There are more specific resources for more specific questions, but I'd suggest you look at https://launchpad.net/ubuntu/+source/binutils
[20:35] <persia> You'll find there all recent uploads into Ubuntu, with details available including changelogs, diffs, etc.
[20:35] <djustice> Ampelbein: close.. but not exactly what i want. i want to "kompare previous_binutils_debsrc new_bintutils_debsrc" basically..
[20:35] <djustice> persia: ha! awesome. thanks!
[20:36] <persia> Or rather, all uploads into Launchpad: seems that it shows unrecent ones, and untrusted ones.
[20:40] <djustice> haha the 'which repo' was paradigm shift from pacman/cpkg :) the ordered/stacked repo style.
[20:48] <tjaalton> slangasek: no, go ahead. and, tbh, you could drop the silly delta :)
[22:33] <slangasek> tjaalton: hum, there are users of that "silly delta" who are likely to reintroduce it if it were dropped, anyway.  Have these changes been forwarded to Debian / upstream and rejected?
[22:38] <tjaalton> slangasek: yep, rejected
[22:39] <slangasek> well, feel free to drop that in the next upload, then; there's still a delta in any case right now due to multiarch
[22:39] <tjaalton> but we can deal with that later, keep it there for now
[22:39] <tjaalton> right