[00:14] <fta> bug 331841
[11:38] <asac> james_w: help ... do you know this: http://paste.ubuntu.com/120546/
[11:38] <asac> major breakage ;9
[11:38] <asac> is that builddeb doing that to me?
[11:39] <asac> oh loom
[11:39] <james_w> yeah, upgrade loom
[11:39] <james_w> reading NEWS.Debian for the update of bzr-builddeb is probably a good idea for you
[11:39] <asac> james_w: i am up-to-date in jaunty
[11:39] <james_w> it's not in jaunty is it?
[11:40] <asac> james_w: not sure ... i had a package installed. thought it was from archive
[11:40] <asac> james_w: yes. i will look in NEWS. i had to downgrade builddeb
[11:40] <asac> on my other system
[11:40] <james_w> why?
[11:40] <asac> seems it doesnt understand --export-upstream* properly anymore
[11:40] <asac> in jaunty
[11:40] <asac> let me look in NEWS
[11:41] <james_w> yeah
[11:41] <james_w> it's gone away
[11:41] <james_w> because it was broken
[11:41] <asac> james_w: it worked well for me (finally)
[11:41] <asac> i used merge = TRue
[11:41] <asac> and export-upstream-revision=
[11:41] <asac> (but not export-upstream)
[11:42] <asac> so when i needed tarball i could specify --export-upstream=.
[11:42] <asac> keeping stuff with warning for one cycle would be nice ;)
[11:42] <asac> err
[11:42] <james_w> could you tell me a bit more about what you wanted to do with it, then I can make builddeb work better for you
[11:43] <asac> james_w: i just want to have info to produce upstream tarballs on the fly in my try
[11:43] <james_w> yeah, I would have liked to have done that, but using it would just lead to trouble
[11:43] <asac> tree
[11:43] <asac> just like i had with --export-upstream=
[11:43] <james_w> ok
[11:43] <asac> (i filed a bug about that ... which would have made that perfect for me)
[11:43] <asac> but now i migrated a bunch of branches there
[11:43] <asac> and the feature is gone
[11:44] <asac> i have 2.1~0ubuntu1
[11:44] <asac> and bzr help builddeb still tells me about --export-upstream
[11:44] <james_w> https://bugs.edge.launchpad.net/bzr-builddeb/+bug/317111
[11:44] <james_w> that's yours
[11:44] <asac> yeah
[11:44] <james_w> I think I know how to fix your case
[11:45] <james_w> I kind of forgot about merge mode
[11:45] <asac> james_w: well. currently export-upstream seems to be broken
[11:45] <asac> or removed (according to you)
[11:46] <asac> ok the initial issue i had with bzr st is gone ... seems it was intermediate while upgrades were running
[11:46] <james_w> I think adding an "export-upstream" command is the way to fix this
[11:46] <asac> james_w: my branches are not always full sources
[11:47] <asac> james_w: i cannot use merge-upstream
[11:47] <james_w> then you can invoke that as you like, without having to first find the combination of configuration options that makes it work for you
[11:47] <asac> e.g. i used it for the new network manager branches
[11:47] <asac> which are just debian tree
[11:47] <asac> worked great
[11:47] <james_w> sure
[11:47] <james_w> I want to fix it
[11:47] <asac> so i could easily still the right revision into the tree
[11:47] <asac> ok
[11:47] <asac> so what should i do for now?
[11:47] <james_w> making this change made merge-upstream much much better, so I don't regret it
[11:47] <asac> hold back the upgrade?
[11:47] <james_w> give me a few hours?
[11:48] <asac> sur3e
[11:48] <james_w> sure
[11:48] <asac> ;)
[11:48] <james_w> I'll include the command in the next upload
[11:48] <asac> james_w: can you still honour the export-upstream-revision = config?
[11:48] <james_w> as you were essentially simulating such a command
[11:48] <asac> that would be great
[11:48] <asac> i adde that info now in a bunch of branches
[11:48] <james_w> my current thought is this
[11:48] <james_w> upstream-branch = foo
[11:49] <james_w> to allow it to be remembered
[11:49] <asac> ok
[11:49] <james_w> bzr export-upstream [BRANCH]
[11:49] <asac> and the revision?
[11:49] <james_w> which takes a -r option
[11:49] <james_w> and creates a tarball for you
[11:49] <asac> can you support legacy support for my config?
[11:50] <james_w> I didn't want to support legacy in that upload, as it would have led to odd behaviour
[11:50] <james_w> but I imagine I can in this upload
[11:50] <asac> james_w: its just the -revision info that i want
[11:50] <asac> i didnt add export-upstream =  in most cases
[11:50] <james_w> why do you want it to be stored in the config file?
[11:50] <asac> james_w: because then the branch is mostly self maintained
[11:50] <asac> i want to commit the revision info right in the tree when i bump changelog
[11:51] <james_w> got it
[11:51] <james_w> seems like a valid use case
[11:51] <asac> great ;)
[11:51] <james_w> let me think about it for a bit
[11:51] <james_w> I want to see if we can make it work even better for you
[11:52] <james_w> would you want it to change the changelog at all?
[11:52] <james_w> not by default it seems
[11:53] <james_w> but perhaps an option to write the revision to the config file and bump the changelog would be nice
[11:53] <asac> james_w: would be ... but its not required.
[11:53] <james_w> sure
[11:53] <asac> james_w: maybe if i do bzr merge
[11:53] <asac> but for debian only trees
[11:53] <asac> i dig the revision info on my own anyway
[11:53] <james_w> I'll get it working for you first, then we can make it better
[11:53] <asac> (its usually not the tip)
[11:54] <james_w> bzr export-upstream --remember-revision -r 246 BRANCH
[11:54] <asac> james_w: i want to publish the revision info
[11:54] <asac> so i would probably need a bzr commit after that?
[11:55] <james_w> yeah
[11:55] <asac> for me the revision is tightly associated with the current tree
[11:55] <asac> so its not somethig i just want locally (like parent branch)
[11:55] <james_w> that would write the revision id to the config file, and also add a new changelog stanza
[11:55] <asac> hmm
[11:55] <james_w> not sure it's the right thing though
[11:55] <asac> james_w: we could do that.
[11:56] <asac> but i usually i just open new changelog upstream revision
[11:56] <asac> and document the revision change in the same commit
[11:56] <asac> like "* new upstream snapshot (revid:xxxx)
[11:56] <james_w> "open new changelog upstream revision" what does that mean?
[11:56] <asac>   - update .bzr-builddeb/default.conf
[11:56] <asac> "
[11:56] <james_w> yeah
[11:56] <asac> james_w: yes, but everybody has his own format for that
[11:57] <asac> if we can standardize that it would be great
[11:57] <james_w> merge-upstream does things like this for you in full source mode, so having it for merge mode may help you
[11:57] <asac> sometimes i say: "new upstream snapshot" ... but on other times i say : "new upstream release xxx"
[11:57] <james_w> but I'll leave all that for later improvements, and fix it for you first
[11:57] <asac> yeah.
[11:57] <asac> just tell me when there is something to test for me ;)
[11:58] <james_w> sure
[11:58] <asac> i can then see how it feels
[11:58] <asac> and complain or cheer ;)
[11:58] <james_w> are you happy to test from bzr?
[11:58] <asac> why not
[11:58] <james_w> k, makes it easier for me :-)
[11:58] <asac> if i can just branch it in .bazaar/plugins
[11:58] <asac> its good
[11:58] <james_w> yeah
[11:58] <asac> do .bazaar/plugins checkouts win over global things?
[11:58] <asac> or does it check for higher version when having conflicting plugins?
[11:58] <asac> (just curious)
[11:58] <james_w> .bazaar/plugins wins
[11:59] <asac> good
[11:59] <asac> so even if its lower
[11:59] <asac> thats the same for mozilla
[11:59] <asac> thought a bit whether it would make sense to chnage that
[11:59] <asac> but probably profile should win
[11:59] <james_w> I'll need an FFe for this, so I'll report a bug later you can make some noise on
[12:00] <asac> james_w: heh. you could even  make bzr bd try export-upstream
[12:00] <asac> when the other download options fail ;)
[12:00] <asac> just an idea
[12:00] <asac> james_w: its  regression bug
[12:00] <asac> not sure if that needs a FFe
[12:00] <asac> ;)
[12:00] <james_w> :-)
[12:01] <asac> but well i can state that in the bug
[12:01] <asac> "all my magic branch wizardry broke" ;)
[12:01] <james_w> perhaps you are right about bd
[12:01] <james_w> having it beat the other options was definitely the wrong thing
[12:01] <asac> yeah. i think woudl be elegant. e.g. factor out export-upstream to its own clean operation and then make use of it
[12:02] <asac> if there is not arball
[12:02] <james_w> however, it can lead to problems anyway
[12:02] <james_w> that's the reason it's gone really
[12:02] <asac> sure. but in most casese you have the archives you will upload to in your sources
[12:02] <asac> if not you have to figure on your own
[12:02] <james_w> it was too easy to shoot yourself in the foot
[12:02] <james_w> I'll consider it though
[12:02] <asac> yeah ;)
[12:02] <asac> the solution was not to add export-upstream = .
[12:02] <asac> to default.conf
[12:03] <asac> and only run --export-upstream if you didnt find a tarball
[12:03] <asac> worked well ;)
[12:03] <james_w> but it also fails in that a -2 upload won't be accepted
[12:04] <james_w> if the .orig.tar.gz was from export-upstream the second time
[12:04] <james_w> it's harder to hit now that it doesn't overwrite
[12:04] <james_w> but it is still an issue
[12:04] <james_w> but anyway, everyone should use full source branches and merge-upstream anyway :-)
[12:05] <asac> hehe
[12:05] <asac> james_w: the main problem is what i had now
[12:05] <asac> james_w: upstream moves branches and then you can trash everything
[12:06] <asac> james_w: so i went back to debian only tree for NM
[12:06] <asac> just sounds more "long-term sustainable"
[12:06] <asac> unfortunately i must admit
[12:06] <james_w> "upstream moves branches"
[12:06] <james_w> what do you mean by that?
[12:06] <asac> yes. NM main branch went to git
[12:06] <asac> and the openvpn branches were moved to their own svn tree
[12:07] <james_w> ah, so all revision ids changed
[12:07] <asac> yes
[12:07] <asac> and the svn -> git migration was a lethal injection obviously
[12:07] <asac> with no proper bzr-git yet
[12:09] <asac> james_w: that reminds me of the git archive issue
[12:10] <asac> james_w: currently i cannot use git archive to produce tarballs
[12:10] <james_w> that one is fixed :-)
[12:10] <asac> because bzr bd sees a file on top
[12:10] <asac> ah good
[12:10] <asac> maybe i didnt see because i downgraded
[12:10] <james_w> yeah
[12:10] <asac> before trying to use that kind of tarball
[12:10] <asac> greawt then ;)
[12:22] <fta> asac, what java plugin is good on amd64? i'm fighting remotely with a dead server and the admin web site in that IBM box needs java. I can't access it from home so i need to setup java remotely on a trusted desktop
[12:24] <asac> fta: i dont think there is much choice
[12:24] <asac> use the latest ice tea thing ...
[12:25] <asac> there is no java plugin with javascript integration though (e.g. oij)
[12:25] <asac> so if the java stuff wants to communicate with website its not going to work on amd64
[12:25] <fta> nm, i figured out how to avoid java
[12:26] <fta> the kernel is spitting insanities in loop
[12:27] <fta> basically, out of memory everywhere, and no way to reclaim anything
[12:48] <asac> fta: hmm so gwibber team build also failed?
[12:48] <fta> yes, jaunty
[12:48] <fta> they silently push python2.6 and python is still 2.5
[12:49] <fta> +ed
[12:50] <fta> i just re-triggered the bot => gwibber_0.9.1~bzr246-0ubuntu1~daily2
[13:30] <fta> lol, bug 31589 :)
[13:30] <fta> no
[13:30] <fta> lol, bug 331589 :)
[13:49] <james_w> asac, fta: do you ever make use of "bzr bd --use-existing"?
[13:50] <fta> nope
[13:50] <fta> what is that?
[13:50] <fta> last bzr regressed? http://paste.ubuntu.com/120589/
[13:51] <james_w> you need to upgrade loom
[13:51] <james_w> the option makes it not extract the upstream tarball again
[13:53] <james_w> just wondering if I have to preserve that
[13:54] <fta> do you mean it's equiv to moving to build-area/foo and doing dpkg-buildpackage -nc ?
[13:54] <asac> james_w: --use-existing? is that like --quick?
[13:54] <asac> that didnt help for me as it somehoe rebuild everything even if i use debuild -nc
[13:55] <asac> if --quick would work that way it would be great
[13:55] <james_w> it deletes debian from the last build directory, then re-exports your branch in to it
[13:55] <james_w> then builds the result
[13:56] <fta> deletes debian = remove the stamps, so it forces a rebuild
[13:56] <james_w> oh, didn't think of that
[13:56] <james_w> I've never really used it myself
[13:57] <james_w> if you don't delete debian it won't work if you delete a file though
[13:57] <fta> indeed
[13:57] <james_w> but that is probably rarer
[13:57] <james_w> what I want to do is make the build-dir default to .. as well
[13:58] <fta> gasp
[13:58] <james_w> but that means using tempdirs to build in, rather than pkg-version directories
[13:58] <fta> that means polluting my branches repository
[13:58] <james_w> how so?
[13:58] <fta> with tons of files i really don't care about
[13:59] <fta> when i need disk space, i just rm -rf build-area
[13:59] <fta> if it's now in .. relative a packaging branch, i will no longer be able to do that
[13:59] <james_w> I said default
[14:00] <fta> i have ~200 branches
[14:00] <james_w> but I don't really see what you mean by "tons of files"
[14:00] <james_w> it would make it work the same way as not using bzr and just calling "debuild"
[14:01] <fta> well, i have my aliases already
[14:01] <fta> bdm = bd --merge --dont-purge --result-dir=../build-area
[14:01] <fta> bdn = bd --native --dont-purge --result-dir=../build-area
[14:01] <fta> ppa = "bd --merge --build-dir=../ppa --builder='dpkg-buildpackage -rfakeroot -S -sa -kB6EE20E8'"
[14:01] <fta> ppa2 = "bd --merge --build-dir=../ppa --builder='dpkg-buildpackage -rfakeroot -S -sd -kB6EE20E8'"
[14:01] <fta> ppan = "bd --native --build-dir=../ppa --builder='dpkg-buildpackage -rfakeroot -S -sa -kB6EE20E8'"
[14:02] <fta> so i don't mind
[14:03] <fta> my bot forces --result-dir too
[14:04] <james_w> why not set "merge" and "native" in the config file so that anyone can build them without figuring that out?
[14:05] <james_w> and the latest version will mean you don't have to use --builder anymore
[14:05] <fta> i don't expect others to build with bzr bd
[14:06] <james_w> "bd --merge --build-dir=../ppa -- -S -sa -kB6EE20E8" will work
[14:06] <fta> and i'm not very in sync with all the new bzr goodies :P
[14:22] <fta> asac, https://edge.launchpad.net/ubuntu/jaunty/+queue?queue_state=0&queue_text=gwibber
[14:25] <asac> fta: thanks. you could have reused the version btw.
[14:26] <asac> fta: can you ask seb politely if he has some cycles to look at it now?
[14:26] <fta> i wanted but cjwatson asked me to bump it
[14:26] <asac> at least inform him that there is a new
[14:26] <asac> ok
[14:26] <asac> doesnt really matter. its easier for archive admin to spot which to take
[14:26] <asac> if you bump version
[14:26] <asac> ok ... preparing for a call
[14:27] <asac> bb in ~1h
[14:42] <cros13> Hi, there is a patch up that fixes this bug:
[14:42] <cros13> https://bugzilla.mozilla.org/show_bug.cgi?id=404314
[15:30] <fta> i'm sick of this crappy sound.
[15:30] <fta> dtchen, do you think my issues with p-a are caused by a crappy driver or crappy h/w ?
[15:31] <BUGabundo> fta: have you tried the workaround?
[15:31] <BUGabundo> to make it speech free or what ever its called?
[15:31] <fta> ?
[15:31] <fta> what is that?
[15:31] <BUGabundo> humm
[15:31] <fta> glitch free?
[15:32] <BUGabundo> there's a mail from crisum and the muson on the lists about it
[15:32] <BUGabundo> yeah that's it
[15:33] <fta> "3 revisions were removed from the branch." (gwibber trunk). gasp, my bot will probably hate that
[15:33] <BUGabundo> eheh
[15:33] <BUGabundo> oh I saw that ryan bumped the gw vers
[15:34] <BUGabundo> so its should now be higher
[15:34] <BUGabundo> as you wished
[15:35] <fta> yep, my description was a bit confusingn, 0.9 vs 0.9.1, ryan used 0.9.1 while 0.9 would have made more sense, my bad
[15:35] <fta> -n
[15:35] <BUGabundo> eheh
[15:36] <fta> i'm not caching the upstream branch for gwibber, good, my bot will cope with the removal
[15:37] <fta>  /me looking for a better sound card... so many: http://www.rue-montgallet.com/prix/75012/comparer/114/Cartes-son/?i1=698&f1=2759&i2=700&f2=2760&i3=701&f3=&i4=702&f4=&mq=0&pxmin=0&pxmax=0&od=nom&show=1&nbf=4
[15:43] <fta> no "works well with ubuntu" list?
[15:46] <BUGabundo> eheh
[15:46] <BUGabundo> did your current got fried yesterday?
[15:47] <fta> no
[15:48] <fta> but i keep having issues on this desktop since p-a entered ubuntu, while on my other desktop and my laptop, it's fine (well, sort of)
[15:48] <asac> keep your eyes open when NM ubuntu2 gets on your system
[15:48] <asac> it might break your carrier detect
[15:49] <asac> escalate to me if you suddenly cannot connect to wired anymore ;)
[15:54] <fta> i don't have the osd notifs, should I?
[15:54] <asac> fta: yes
[15:54] <asac> do you have notify-osd installed?
[15:54] <fta> nope
[15:54] <fta> but i'm up-to-date
[15:54] <asac> fta: install it ;)
[15:54] <asac> maybe you nuked something else
[15:55] <asac> like ubuntu-desktop
[15:55] <asac> ii am not sure how that is supposed to get pulled in
[15:55] <BUGabundo> ahhhhhhh asac? really
[15:55] <BUGabundo> ?
[15:55] <fta> oh right, i no longer have ubuntu-desktop
[15:56] <BUGabundo> I'll have to look at it
[15:56] <BUGabundo> and inform users on +1
[15:56] <BUGabundo> yah I lost ubu-deskt twice now!
[15:56] <asac> yeah. if you removed ubuntu-desktop there is no guaranteey you really track the ubuntu desktop experience
[15:56] <asac> similar if you uninstall firefox package you wont get auto migrated to firefox-3.1
[15:57] <fta> The following packages will be REMOVED:
[15:57] <fta>   gnome2-user-guide restricted-manager restricted-manager-core scrollkeeper
[15:57] <asac> fta: not srue. i think the restricted manager is now called jockey
[15:57] <BUGabundo> asac: but UM -d should make sure its there
[15:57] <asac> might be that its just a normal removal
[15:57] <asac> due to control hints
[15:57] <asac> BUGabundo: i am not sure about that. ask mvo. there might be reason to not pull that in again
[15:57] <BUGabundo> fta: what ever you do, DON'T force anything
[15:57] <BUGabundo> parcial installs suck
[15:57] <asac> i even think so. if you opted out of ubuntu-desktop there is no reason to force it on you gain
[15:58] <BUGabundo> UM should never ofer them
[15:58] <BUGabundo> asac: yeah I have to ask him
[15:58] <fta> BUGabundo: lol, i'm not a noob ;)
[15:58] <BUGabundo> already did, but did not get a reply
[15:58] <asac> partial upgrades are ok
[15:58] <BUGabundo> yestreday
[15:58] <asac> you just shouldnt confirm upgrade if there are a bunch of removals you dont understand ;)
[15:59] <fta> http://paste.ubuntu.com/120629/
[15:59] <fta> too much crap in there
[15:59] <BUGabundo> seems fine to me
[15:59] <BUGabundo> lololol
[15:59] <BUGabundo> how long have you been without U-deskt?
[16:01] <fta> apparently a long time ago
[16:01] <BUGabundo> already got mvo on +1
[16:01] <BUGabundo> trying to get this strait
[16:01] <fta> fta@ix:~ $ zgrep ubuntu-desktop /var/log/dpkg.log*
[16:01] <fta> fta@ix:~ $ L /var/log/dpkg.log* | head -1
[16:01] <fta> -rw-r----- 1 root adm  120156 2008-03-30 15:20 /var/log/dpkg.log.12.gz
[16:01] <fta> fta@ix:~ $
[16:01] <asac> you should go to network-manager ;)
[16:01] <BUGabundo> ehehehehehehehe
[16:02] <fta> so probably more than a year ago
[16:02] <asac> anyway ... justinstall notify-osd  for now;)
[16:02] <asac> folks on +1 should use ubuntu-desktop though
[16:02] <BUGabundo> yeah
[16:02] <BUGabundo> but a few of us lost it
[16:02] <BUGabundo> trying to clear that out with mvo
[16:03] <asac> thats a good time to learn ;)
[16:03] <fta> n-m for an always wired desktop /w fixed ip is useless
[16:03] <BUGabundo> works for me (TM)
[16:03] <BUGabundo> if it discover it's the same network
[16:03] <BUGabundo> avahi magic ?!
[16:03] <fta> i don't need that
[16:04] <fta> i will just cherry pick what i need from the list
[16:04] <BUGabundo> yeah I do that too, when it fails
[16:04] <fta> app-install-data-partner ? hmm
[16:05] <BUGabundo> asac: fta mvo said UM should install ubu-deskt!
[16:06] <asac> then you lost it after upgrading to jaunty ;)
[16:06] <asac> fta probably used apt-get dist-upgrade ;)
[16:06] <BUGabundo> yeah
[16:07] <BUGabundo> he shouldn't
[16:07] <BUGabundo> lol
[16:07] <fta> no, maybe i removed it to prevent n-m from trashing my prefs at each reboot
[16:07] <BUGabundo> "that's not the Recommend way on Ubuntu"
[16:07] <BUGabundo> according to the Wiki
[16:07] <BUGabundo> lol
[16:09] <fta> mobile-broadband-provider-info on my desktop, no thanks
[16:12] <fta> ok, 29 instead of 54
[16:19] <fta> asac, it's not transparent at all and it's not using my prefs
[16:19] <fta> metacity
[16:19] <asac> fta: did you fix the gwibber team build? (me desparately wants the new thing due to annoyance)
[16:20] <asac> fta: yes metacity needs still some fixes.
[16:20] <asac> but it works at least (first it didnt show anything)
[16:20] <asac> fta: metacityy also supports a bit composite ... you can try to enable that
[16:20] <asac> but i guess its still lacking support
[16:21] <asac> fta: ask macslow about his plans
[16:21] <fta> i know, but i don't want composite for my other windows
[16:21] <fta> it's slower for no benefit
[16:21] <asac> yeah. ask him
[16:21] <asac> ;)
[16:22] <fta> i can't read the text, white on black but too small, and it disappears too fast
[16:22] <fta> the time my eyes move and focus on the notif, it's gone
[16:22] <asac> yeah. tell that him ;)
[16:22] <asac> and file bugs
[16:22] <asac> bugs bugs
[16:22] <fta> :)
[16:22] <asac> thats the important part. notify-osd
[16:30] <fta> i wish someone fixes bug 328932 soon
[16:36] <asac> fta: it says its fixed since 13 hours
[16:37] <asac> This bug was fixed in the package libsdl1.2 - 1.2.13-4ubuntu3
[16:37] <fta> really?
[16:37] <asac> Great work Luke! Thanks for fixing it. All games work again on my machine after I installed the update.
[16:37] <asac> yes
[16:37] <asac>   * debian/control:
[16:37] <asac>     - add libglu1-mesa-dev as a build dependency, so SDL gets built with
[16:37] <asac>       OpenGL support (LP: #328932)
[16:37] <asac>     - Fix typo in svn URL (LP: #330457)
[16:38] <fta> unpinning
[16:39] <fta> great
[16:39] <fta> i just have tomboy left unupgradable
[16:41] <asac> yeah
[16:41] <asac> tomboy disappeared from my panel
[16:41] <asac> i think i removed it ;)
[16:41] <asac> oh its back :)
[16:41] <asac> no its normal sticky notes ihave now
[16:41] <asac> let me kill those
[16:42] <asac> tomboy installs with removing libgmime2.2-cil
[16:42] <asac> and instead getting 2.2a-cli
[16:44] <fta> oh, better then, it was removing tons of vital stuff up to yesterday
[16:49] <asac> yeah. probably the build systems are catching up finally from the FF rush
[16:57] <fta> i have plenty of new sounds for events now
[16:59] <fta> I can't disable some of them with the ui
[17:06] <fta> asac, https://edge.launchpad.net/~gwibber-team/+archive/ppa
[17:06] <asac> fta: hehe. yeah i get the drum roll every now and then in ffox 3.2
[17:07] <asac> its a bit irritating
[17:39] <asac> \o/ NM finally found a build slot on amd64
[17:39] <asac> maybe i can still test before leaving for the night
[18:24] <BUGabundo_> asac: ping
[18:38] <BUGabundo_> asac: ping
[18:38] <BUGabundo_> lets see if 3G hands for a while
[18:39]  * BUGabundo_ typing from an eeepc with no light on the keyboard is not easy
[18:42] <fta> back
[18:47] <BUGabundo_> need tips on how to share 3G/UMTS net, via wired
[19:54] <fta> "Karmic Koala", yeahhh, i guessed koala
[22:15] <gnomefreak> asac: did you say that network-manager 0.7.1~rc1-0ubuntu2 is broken for wired connection?
[22:24] <[reed]> fta: hehe
[22:24] <[reed]> fta: Koalas are so cute ;)
[22:25] <gnomefreak> i just read that too
[22:27] <gnomefreak> why do i get a badf feeling about sunbird
[22:29] <gnomefreak> [reed]: are they talking about just dropping lighnting to its own code base or are they talking about stepping back from both
[22:33] <gnomefreak> i had already known lightning wasnt gonna be part of tb3 if it was it would have been done in alpha# but this whole no team for sunbird bothers me
[22:33] <[reed]> well
[22:34] <[reed]> I think Sun's pulled out
[22:34] <[reed]> of a lot of what it was doing
[22:34] <[reed]> which is what is causing this :/
[22:34] <gnomefreak> damn
[22:34] <[reed]> Sun has been killing stuff left and right
[22:34] <[reed]> same for others like IBM
[22:34] <[reed]> just companies in general
[22:35] <gnomefreak> that would be the start of a big rolling downfall assuming it didnt have 50+ companies
[22:36] <[reed]> MoMo is really wanting Lightning for Thunderbird, but they decided the add-on path works better
[22:36] <[reed]> which I can agree with
[22:36] <gnomefreak> [reed]: it would have been nice for the people that like the intergration, for me i hate lightning and stick with sunbird
[22:37] <[reed]> developers welcome
[22:39] <gnomefreak> first i hear daniel martin berend ect... left but daniel says he is still very much a prat of team and he suspects the others are as well
[22:39] <gnomefreak> s/prat/part
[22:43] <gnomefreak> 15+ extensions and he wonders why it crashes :(
[22:44] <gnomefreak> sorry 24 to be exact
[23:02] <VicTheHunter> Hello, please help? When I watch videos with Cheese, or totem-plugin-viewer 2.22.1, the images come out looking interleaved, and the bottom half is columns of solid colors.  How can I fix this?
[23:02] <VicTheHunter> Sometimes, the images are ghosted, or doubled side-by-side.  I notice this also in Firefox.