[00:06] <persia> kklimonda, So, we use a namespace on IRC.  We say that a nick identifies a person.
[00:06] <persia> So a nick is really an IPI (IRC Person Identifier)
[00:06] <persia> Similarly, a URI is a Universal Resource Identifier.
[00:07] <persia> And so should not be able to exist without there being a Resource behind it.
[00:07] <kklimonda> so your question is "what does really magnet identify?"
[00:07] <persia> I don't care, but I believe the answer to that question is required in order to use MIME handling, and that without that answer, magnet: is abusing the semantics of URI.
[00:14] <kklimonda> mhm, makes sense. and yeah, I know you don't care about it, I used this figure of speach as a shortcut of sort. I guess the problem is mime-type is not the right right way of doing that.. but KDE's way has its own problems. So we end up with something that is ugly but works.
[00:17] <persia> KDE's is cleaner than Bastien's
[00:18] <persia> Doing it right is extra complicated, and requires writing a bundle of code and migrating all the legacy applications.
[00:18] <persia> But if you can define the nature of the resource, you can then construct a file/stream/whatever that matches, and then have a MIME type for that resource, and things ought just work without too many hacks.
[00:23] <kklimonda> persia: then I can only assume that magnet is abusing uri specification because not all magnet uris can be translated into resources (by resource I mean for example a torrent file you download knowing its hash). Some hashes are just used by p2p clients to ask all peers whether they have the file in question or do they know anyone who has it.
[00:24] <persia> kklimonda, That's why I asked if the resource was a hash.
[00:25] <persia> And remember my "Moby Dick" example: there's no reason a URI can't supply multiple formats (although only a subset may be available for any given resource).
[07:15] <simar> persia, hi
[07:15] <simar> persia, remember
[07:23] <napster> Hello friends
[07:23] <napster> I would like to contribute to ubuntu-natty-gnomeutils-gnomescreenshot project
[07:23] <napster> How can I do that?
[07:24] <persia> simar, Yes.
[07:24] <persia> napster, Where did you get the name of that project?
[07:24] <napster> How to get a branch for natty/ubunu-utils?
[07:24] <napster> persia: https://launchpad.net/ubuntu/natty/+source/gnome-utils
[07:26] <persia> napster, What are you trying to do?
[07:26] <napster> persia: I would like to change the way screeshot program names files while saving
[07:26] <persia> Ah, OK.
[07:27] <persia> napster, So, there's two ways to do this: best is to work on http://live.gnome.org/GnomeUtils upstream: anything in the next release *will* be part of Natty.
[07:28] <napster> persia: And the other way?
[07:28] <simar> persia, How can I contribute to the development release, natty, without getting into merging and syncs .. I mean what are the other ways to contribute?
[07:28] <persia> Second best is to work with the folks in #ubuntu-desktop to get a local patch in Ubuntu.  I don't suspect you'll have much luck with this, as that team really doesn't like patches unless upstream is ignoring them for some reason.
[07:29] <persia> simar, There's a few things that would be great just now.  Fixing some of the bugs.  Working on UEHS to get stuff not in Debian up-to-date.  Cleaning up old Ubuntu-local source packages.
[07:29] <napster> persia: OK, thank you
[07:29] <persia> simar, And more work on FTBFS is always good.
[07:30] <simar> persia, but I think FTBFS, havn't come up for natty yet?
[07:30] <simar> UEHS?
[07:31] <persia> http://qa.ubuntuwire.com/ftbfs/ shows a couple hundred
[07:31] <persia> http://qa.ubuntuwire.com/uehs/ are packages not maintained in Debian, many of which need to be reviewed to either be updated to newer upstream or removed from Ubuntu.
[07:36] <simar> persia, so for UESH, should we get these packages into debian..
[07:36] <persia> Maybe, but probably not now, as squeeze is freezing.
[07:37] <persia> Better to just check for new upstreams, update the packaging, check for bugs and close as many as you can, check other distributions to see if anyone else has cool patches we want, and upload.
[07:38] <persia> Note that lots of UEHS stuff is already in Debian, but just doesn't have a maintainer there.
[07:39] <simar> persia, ok fine, but how to get started i don't know.. But I know somewhat about fixing FTBFS. Should I get to them first?
[07:40] <persia> simar, Sounds like a reasonable plan.  I think it's best to do what you know first, and do what you don't know as you get annoyed enough to learn.
[07:40] <persia> So someone like you should concentrate on FTBFS because you know it, and not worry about new shiny upstream stuff until there's some feature you simply cannot do without that needs one, giving you motivation to learn.
[07:41] <persia> Or one of your FTBFS uploads ends up causing a merge, at which point you have to merge your work, etc.
[07:42] <simar> persia, :)) , ya i get that,  are all these FTBFS for natty ?
[07:42] <simar> persia, ah! the are
[07:42] <persia> On the natty page, yes.
[07:43] <simar> persia, thanks .. then i have the pbuilder for natty and i will get started now ..
[07:43] <persia> And thanks a lot for working on them.  Just because they are easy for you, don't think they are easy for other folk (I find them fairly hard, myself).
[07:45] <simar> persia, perhaps not easy for me either .... last time i had a taste that was bitter that ever.. haha
[07:46] <simar> persia, Infact this is a problem .. I don't know how to choose easy ones. Is there a way out?
[07:46] <persia> My general attitude towards picking things is to look for things that aren't too hard, and then do them.  If they look really hard, I look for something else until there's only the ones I find hard left.
[07:55] <simar> persia, so you say, pick randomly and then look into them and analyse them .. if you can handle them..
[07:56] <simar> persia, i think this is a simple one..
[07:56] <simar> https://launchpad.net/ubuntu/+source/tea
[08:01] <simar> persia, i think this is a simple one.
[08:01] <simar> https://launchpad.net/ubuntu/+source/tea
[08:02] <dholbach> Good morning!
[08:02] <simar> dholbach, same to you  :))
[08:02] <dholbach> hi simar
[08:03] <simar> dholbach, hi
[08:03] <simar> dholbach, actually I was looking forward to fix some FTBFS before getting on to merging..
[08:04] <persia> simar, I suspect you're right.  Looks like the sort of thing mentioned in the natty open announcement.
[08:05] <simar> natty open announcement?? how to see that
[08:07] <persia> https://lists.ubuntu.com/archives/ubuntu-devel-announce/2010-October/000772.html
[08:13] <simar> persia, i have subscribed to natty-changes
[08:14] <simar> persia, I make a note of gcc4.5
[08:16] <simar> persia, as well as to ubuntu-devel-announce
[08:39] <simar> Does anyone here knows how to install a pbuilder for natty in karmic
[08:40] <persia> You probably want to upgrade to at least lucid to get the snazzy tools.
[08:40] <persia> That said, you'll either have to install backports, or make a slightly updated pbuilder, and dist-upgrade it.
[08:42] <dholbach> maybe backport debootstrap yourself (karmic only has 1.0.20), then use pbuilder-dist from ubuntu-dev-tools?
[08:43] <simar> persia, my display goes totally off in lucid and higher . due to incorrect EDID ..
[08:43] <simar> dholbach, what does backport debootstrap yourself means
[08:44] <simar> otherwise i tried using
[08:44] <persia> Newer debootstrap probably runs on older installs fine, although rebuilding from source isn't that hard.
[08:44] <simar> sudo pbuilder create
[08:44] <dholbach> on the karmich machine: dget -xu https://launchpad.net/ubuntu/+archive/primary/+files/debootstrap_1.0.25.dsc; cd debootstrap-1.0.25; debuild && sudo debi
[08:44] <simar> sudo pbuilder update distribution natty ...
[08:45] <dholbach> simar, and then   pbuilder-dist natty create
[08:46] <simar> all this I have do without uninstalling the previous pbuilder tarball
[08:46] <persia> Well, you want the karmic one to do the backport, really.
[08:47] <persia> Also, you may want to devote some time to tracking down the EDID issue: karmic will be unsupported soon, and you'll want to be able to upgrade.
[08:47] <tumbleweed> I doubt you need a newer debootstrap. Ubuntu has been using the same rules since gutsy. I just "ln -s natty gutsy" (I have my pbuilders on debian boxes)
[08:47] <persia> Lots to learn if you chase EDID, but worst case, there's ways to hardcode around it.
[08:47] <persia> tumbleweed, the newer debootstraps have the symlink predefined, and have little workarounds for stuff like installing the mailserver, etc.
[08:48] <tumbleweed> persia: right. Anyway getting past karmic is highly recommended :)
[08:48]  * persia has one machine still sadly stuck on jaunty, and is *really* hoping to get it upgraded in the next week.
[09:13] <simar> persia, i want to fix that EDID thing .. I have also filed a bug in this regard. Could you help me in doing that//
[09:16] <simar> persia, i think this has some relation to my problem https://blueprints.edge.launchpad.net/ubuntu/+spec/hardware-desktop-n-xorg-configuration-the-final-ten-percent
[09:21] <persia> simar, Most undoubtably :)  Can't you do something with xorg.conf to work around that?
[09:22] <simar> persia, It works in karmic but does not work in lucid may be due to nouveau..
[09:23] <persia> Probably needs a slightly different xorg.conf
[09:24] <simar> persia, Also if I install nvidia drivers in karmic for 3d, still i have blank display. But yes I can fix that using a EDID information exported from windows but then I can't switch my VT using Ctrl+alt+f2..
[09:25] <simar> persia, I have to configure to use the exported EDID in xorg.conf
[09:29] <simar> persia, also I can't change my display brightness in ubuntu. I can see the indicator moving but nothing happens
[09:30] <persia> Sure.  It's a bug.    I'd probably try to upgrade anyway, and deal with the brightness issue.  You have to decide whether it's more important to have limited X or to have newer tools.
[09:36] <simar> persia, I too would like to upgrade but have no idea where this EDID information comes from and what to explore but I hope i can learn that, I have been working in input subsystem(touchpad in general) so I know somewhat about debugging X.. and kernel.)
[09:36] <simar> persia, I have also written some documentation work like https://wiki.ubuntu.com/DebuggingTouchpadDetection
[09:37] <simar> persia, I hope you can give me a start like telling me the package name
[09:37] <persia> I don't know enough about it to help you with that.
[09:39] <simar> persia, ok.. :((
[09:56] <simar> persia, I will work myself, on this first. So that I can upgrade to Maverick, using pen drive live installations
[09:57] <simar> persia, Is using pen drive live installation a good idea to test this problem or there is a better idea??
[09:58] <simar> persia, I mean display going completely off at boot time... I don't to spoil my current installation..
[11:42] <ara> Once I proposed a merge on a new upstream upload (I am waiting for sponsorship), shall I mark this as Fix Committed? bug 662583
[11:46] <tumbleweed> ara: no, sponsors tend to look at bugs marked New or Confirmed. https://wiki.ubuntu.com/Bugs/Status Although in this case it's a bzr merge proposal, so sponsors won't even see the bug.
[11:49] <ara> tumbleweed, but they will see the merge proposal, won't they?
[11:52] <tumbleweed> ara: it should show up here on the next update: http://reports.qa.ubuntu.com/reports/sponsoring/
[11:53] <ara> tumbleweed, OK, thanks
[13:38] <micahg> ara: no, Confirmed is the correct status for Merge requests
[14:11] <micahg> are we supposed to accept the deb src 3.0 patch name and headers or make an appropriate patch name and add/delete dep-3 headers as appropriate?
[14:40] <ScottK> micahg: It's better to do the latter.
[14:40] <Rhonda> The later, the former is just an effort to offer something useful, more a template.
[14:41] <Rhonda> And I guess you edit the template debhelper files in debian/ after dh_make too, right? ;)
[16:03] <till_> anyone have time to answer a short maintainer q? (debhelper related)
[16:07] <ximion_> till_: Just ask :P (maybe I can answer it)
[16:07] <Rhonda> Noone can answer your question if you don't ask it.
[16:08] <till_> :D
[16:08] <till_> ok, so basically, i'm using override_dh_auto_configure in my debian/rules
[16:08] <till_> when i do, "dh_auto_configure -- --my-opts"
[16:08] <till_> it doesn't really override, but append
[16:09] <till_> is the only solution to do, ./configure --my-opts there?
[16:15] <ximion_> till_: What do you want to archive?
[16:15] <ximion_> never call ./configure directly in debian/rules, it just causes pain.
[16:16] <ximion_> if you call dh_auto_configure -- <flags> the flags get appendet to the ./configure call - why do you want to leave out the default options?
[16:19] <till_> ximion: well, they don't make sense for me
[16:19] <ximion> till_: why?
[16:19] <till_> e.g., it assumes a prefix i don't want
[16:19] <till_> i could probably override prefix
[16:19] <till_> let me check this
[16:21] <ximion> till_: You mean prefi=/usr ? This is a necessary option to make make install install all files to currect destinations
[16:21] <till_> i want /usr/local though
[16:21] <ximion> also all libexec and other prefixes are set automagically to follow the packaging guidelines
[16:21] <till_> don't seem to be able to change that
[16:22] <ximion> till_: Why do you want this strange, policy-incompliant behavior?
[16:22] <till_> ximion: a lot of other related resides in /usr/local etc.
[16:22] <till_> i wanted to keep it close
[16:23] <till_> besides, i didn't want my package to conflict with the regular package
[16:23] <Rhonda> till_: Debian packages though don't install to /usr/local, so if you override that the package clearly won't be included in Ubuntu or Debian.
[16:24] <ximion> till_: Prefix always should be /usr, otherwise it won't be included into any distro
[16:24] <till_> that's not a problem
[16:24] <ximion> yep ^^
[16:24] <ScottK> If you aren't working on a package intended for Ubuntu, #ubuntu-packaging is a better channel.
[16:24] <till_> i'm just trying to create a custom .deb
[16:24] <ximion> If you want to avoid conflicts with existing software, install into /opt
[16:24] <till_> how do i set the prefix to /opt ?
[16:24] <Rhonda> And for installint to /usr/local you maybe want to do it without packaging, or use something like checkinstall or stash.
[16:25] <till_> tried checkinstall already
[16:25] <till_> i wanted something that can track dependencies ;)
[16:25] <Rhonda> This channel though is like ScottK pointed out for packaging work that is meant to go into the distribution.
[16:25] <ScottK> It's off topic for this channel in any case.
[16:26] <ximion> till_: Okay. You will need to run ./configure manually then.
[16:26] <till_> ximion: thanks :)
[16:26] <till_> appreciate the help, none the less
[16:27] <ximion> apropos packages which go into distributions ^^
[16:28] <ximion> (now I have a question)
[16:30] <ximion> I packaged "packagekit" for Debian, the package was reviewed three times and considered as really good, but no DD had enough time to sponsor it... As Ubuntu/Kubuntu uses PK, it would be nice for Ubuntu to have this in Debian too.
[16:30] <ximion> Is anyone interested in sponsoring this package for Debian?
[16:30] <ximion> and if not, can I merge the Ubuntu changes into my package and suggest it for Natty?
[16:31] <Rhonda> You might want to ask in #debian-ubuntu on OFTC network. :)
[16:32] <ximion> Rhonda: Thanks, I'll try :)
[19:00] <RoAkSoAx> jcastro: ping
[19:41] <xteejx> Hi all, what's the procedure for fixing FTBFS packages?
[19:41] <xteejx> I'm relatively new to it and trying apparmor
[19:48] <ScottK> xteejx: That's probably not a good one to start with.  It actually needs a kernel fix.
[19:49] <ScottK> xteejx: I'd recommend starting with Universe packages since that's what we tend to focus on here.
[19:49] <ScottK> http://qa.ubuntuwire.com/ftbfs/#universe
[19:49] <xteejx> Oops hehe thougth I was on universe :)
[19:59] <xteejx> I've seen this in a couple of ftbfs build logs: "collect2: ld returned 1 exit status"
[19:59] <xteejx> Is there a known problem or workaround?
[19:59] <azeem_> it's a summary, the error is earlier
[19:59] <azeem_> it means linking failed
[19:59] <xteejx> the new gcc?
[20:00] <azeem_> hrm?
[20:01] <xteejx> It's the ftbfs of zvbi I'm looking at
[20:01] <azeem_> so what is the error?
[20:02] <xteejx> It could be the second line "sh: gcc: not found" and then it reverts to native compile
[20:02] <azeem_> sounds possible
[20:03] <xteejx> Anyone able to walk me through this one so I can learn?
[20:03] <xteejx> please :)
[20:05] <ScottK> xteejx: What package is it?
[20:05] <ScottK> Ah.  zvbi
[20:05] <xteejx> yeah scott :)
[20:06] <ScottK> ../src/.libs/libzvbi.so: undefined reference to `S_ISCHR' is the actual error.
[20:07] <xteejx> I see it, in proxyd.c
[20:07] <ScottK> So the trick is to figure out what library provides that symbol and add it to build-depends if it's missing or add it to the linker flags if it's already present, but not found.
[20:07] <azeem_> looks like a macro to me
[20:08] <ScottK> OK.
[20:08] <ScottK> azeem_: I'm about 98% sure you understand this one better than me.
[20:08] <azeem_> hrm
[20:08] <azeem_> I'm not :)
[20:08] <ScottK> Please carry on ...
[20:08] <xteejx> i'm 100% that everyone here undertsnads it ALL better than me :P
[20:10] <azeem_> it's a V4L thing
[20:10] <xteejx> vlc came up a lot on google
[20:10] <ScottK> http://launchpadlibrarian.net/57799542/buildlog_ubuntu-natty-i386.tiled-qt_0.5.1-1_FAILEDTOBUILD.txt.gz is an example of missing LDFLAGS.
[20:11] <xteejx> /usr/bin/ld ... undefined reference ?
[20:12] <azeem_> xteejx: S_ISCHR i used in the source code (and referenced in one of the included header files), but none of the libraries which get linked in provide it
[20:12] <azeem_> -> undefined referenced
[20:12] <azeem_> reference*
[20:15] <xteejx> azeem_: I don't understand
[20:15] <xteejx> I'm kinda new to this kinda stuff
[20:24] <xteejx> Ok, it looks like sys/stat.h is missing but not quite sure where that should go
[20:54] <xteejyx> How do you go about fixing linker errors? i.e. undefined reference to symbol XXXX?
[20:54] <xteejyx> It's a FTBFS package
[20:55] <azeem_> I don't think there's a recipe
[20:55] <xteejyx> the build log says "try adding it to the linker command line" but I'm not quite sure what that means can someone explain it?
[20:56] <azeem_> are you still looking at zvbi?
[20:56] <xteejyx> No I gave up on it, now on wwwoffle
[20:56] <xteejyx> It seems more understandable to me
[20:56] <azeem_> ok
[20:57] <azeem_> then figure out which library package ships the XXXX symbol
[20:57] <azeem_> sometimes it's enough to just add it to the Build-Depends
[20:57] <xteejyx> it's libgcrypt11, but it's alredy in the build-deps
[20:57] <xteejyx> well -dev
[20:58] <tumbleweed> azeem_: this looks like a binutils-gold issue, so it'll need -lgcrypt (or something like that)
[20:58] <azeem_> ok
[20:58] <xteejyx> Is that added to the debian/control file? is it control
[20:59] <xteejyx> rules even
[20:59] <xteejyx> sorry, half asleep here :)
[21:00] <geser> xteejyx: upstream Makefile
[21:00] <xteejyx> geser: Thanks :)
[21:01] <tumbleweed> xteejyx: looks like that'll do the trick. Don't forget to forward the patch upstream :)
[21:02] <xteejyx> So add -lgcrypt to the end to make "install : compile -lgcrypt" ?
[21:02] <xteejyx> in Makefile.in
[21:02] <azeem_> no, to the linker line
[21:02] <azeem_> usually the variable i called LDFLAGS
[21:02] <azeem_> or LIBS
[21:03] <xteejyx> there isn't any :S
[21:03] <xteejyx> But I'v learnt what LDFLAGS is now at least, makes a lot of sense
[21:04] <xteejyx> There is "LIBS="$LIBS $ETR_SOCKET_LIBS"" in line 48 of configure.in ... ?
[21:05] <azeem_> it's hard to say where the correct place for the addition is without looking at the source
[21:05] <azeem_> does it use automake?
[21:06] <xteejyx> azeem_: it does
[21:07] <geser> xteejyx: you might need to check how the software checks for other libs and see if you can adapt it for the missing library too
[21:07] <xteejyx> I'm looking around for those strings $LIBS, maybe in an include somewhere
[21:09] <geser> it might not be necessarily $LIBS in the Makefile.am
[21:09] <xteejyx> I'm looking at configure.in
[21:09] <tumbleweed> xteejyx: as gcrypt is a dependancy of gnutls, how about getting it to add it to th elibs it links with for gnutls?
[21:10] <xteejyx> That means absolutely nothing to me, sorry :(
[21:10] <tumbleweed> also, doesn't look like this package regenerates configure from configure.in
[21:10] <xteejyx> I thought that, since it's already there, but...
[21:11] <tumbleweed> you'll see what I mean when you find the bit I'm talking about
[21:11] <xteejyx> I found ac_subst_vars=<insert loads of stuff here> - it include those strings
[21:12] <xteejyx> s/include/includes
[21:12] <tumbleweed> xteejyx: hint, look for -lgnutls
[21:13] <tumbleweed> alternatively, you can probably provide it to configure in debian/rules (which is a smaller change, but less upstreamable)
[21:14] <xteejyx> I see line 4525 in configure
[21:14] <xteejyx> Looks like a place I could slot a -command in
[21:14] <xteejyx> I *think*
[21:14] <xteejyx> -option even
[21:15] <xteejyx> tumbleweed: Would that work? ^^
[21:16] <tumbleweed> xteejyx: I was thinking more like 4493, but didn't test that
[21:16] <tumbleweed> xteejyx: you asking me? How about a test build :P
[21:16] <xteejyx> I'm tired..that's my excuse and I'm sticking to it ;)
[21:17] <xteejyx> -lgcrypt is it?
[21:21] <xteejyx> what's the debuild option I forgot
[21:21] <alkisg> Hi, how can I tell `debuild -S -sa` to exclude by .bzr directory? `DH_ALWAYS_EXCLUDE=.bzr debuild -S -sa` doesn't exclude it from the .tar.gz file..
[21:22] <alkisg> (so I end up uploading 2.5 Mb to launchpad instead of some Kb)
[21:22] <micahg> alkisg: try using bzr-builddeb
[21:22] <xteejyx> tumbleweed: ok I did debuild -S I'm really stumped now..brain freeze
[21:22] <alkisg> micahg: ty, trying...
[21:23] <xteejyx> micahg: How do I build? I've done debuild -S forgot what the next one was
[21:23] <azeem_> debuild -S builds a source package
[21:24] <azeem_> check the debuild documentation or --help output
[21:24] <tumbleweed> xteejyx: now you feed the .dsc to a natty pbuilder / sbuild (but maybe I was leading you down the wrong path here, my test failed)
[21:24] <micahg> xteejyx: that makes a source package, you can then use that in pbuilder
[21:24] <xteejyx> pbuilder with .dsc that sit
[21:24] <xteejyx> thanks micahg
[21:24] <micahg> xteejyx: tumbleweed beat me by a second :)
[21:25] <xteejyx> thanks tumbleweed as well I just saw your message, but no point building it lol
[21:25] <tumbleweed> err I made a typo
[21:26] <xteejyx> tumbleweed: How so?
[21:27] <tumbleweed> xteejyx: in my test. Keep working on it, and I'll see what I did wrong
[21:27] <xteejyx> It is -lgcrypt isn't it?
[21:31] <tumbleweed> xteejyx: yes
[21:32] <xteejyx> ok :)
[21:32] <xteejyx> just create pbuilder and then build dsc
[21:34] <xteejyx> *creating
[21:36] <alkisg> I didn't manage to exclude the .bzr directory from the tar.gz file by using bzr-buildpackage, any other hints welcome :)
[21:37] <micahg> alkisg: bzr bd --builder 'debuild -S -sa'
[21:37]  * tumbleweed does bzr bd -S -- -sa
[21:38] <micahg> ah, that's probably the shorthand :)
[21:39] <alkisg> Thank you guys, that worked fine :)
[21:41] <micahg> tumbleweed: you have time to sponsor something?
[21:46] <tumbleweed> micahg: yeah
[21:52] <micahg> tumbleweed: bug 634798, thanks
[22:00] <tumbleweed> micahg: still going to sort out those gjs SRUs?
[22:02] <micahg> tumbleweed: yeah, I should do that tonight
[22:02] <tumbleweed> :)
[22:21] <xteejyx> In natty I tried to run "sudo pbuilder create" and I got this at the end "W: Failure trying to run: chroot /var/cache/pbuilder/build/16738/. dpkg --force-overwrite --force-confold --skip-same-version --install" - it downloaded installed and configured and then done that
[22:27] <tumbleweed> xteejyx: sorry no idea. (you don't need a natty host to pbuild with natty)
[22:28] <xteejyx> tumbleweed: I'm in vbox with natty installed, is there something other than pbuilder to use for now?
[22:28] <tumbleweed> yeah if you have a natty box, just build it in there
[22:29] <tumbleweed> there's also PPAs
[22:29] <xteejyx> that's where I'm having the pbuilder problem
[22:29] <xteejyx> sudo pbuilder create is right isn't it? no extra options needed?
[22:29] <tumbleweed> no I mean just build outside the pbuilder
[22:30] <xteejyx> how?
[22:31] <tumbleweed> xteejyx: debuild -uc -us ?
[22:31] <xteejyx> Ahh ok :)
[22:32] <xteejyx> So many commands it's hard to remember all of them
[22:34] <ari-tczew> pbuilder-dist ?
[22:34] <xteejyx> I'll try that in a minute, for now normal debuild -us -uc is working
[22:37] <xteejyx> ftbfs wwwoffle - I tried adding -lgcrypt, didn't work, -libgcrypt appears to and actually gets past certificates.*, but new problem comes up:
[22:37] <xteejyx> wwwoffle-checkcert.c:48:33: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘LoadPrivateKey’
[22:37] <xteejyx> I think I'm gonna give up on this one as well lol
[22:40] <tumbleweed> xteejyx: did you use quotes like this?: GNUTLS_LIB="-lgnutls -lgcrypt"
[22:43] <xteejyx> tumbleweed: I actually put it in line 4525 to make LIBS="-lgnutls -libgcrypt $GNUTLS_LIB $LIBS"
[22:43] <xteejyx> and lgcrypt I tried
[22:43] <xteejyx> neither worked
[22:44] <xteejyx> but that should still have worked
[22:45] <tumbleweed> xteejyx: worked-for-me: http://pastebin.com/Lih6MrhF
[22:46] <xteejyx> thats where I've messed up then. How come it couldn't go where I put it?
[22:48] <tumbleweed> xteejyx: what does the line before that one do?
[22:49] <xteejyx> ac_check_lib_save_LIBS=$LIBS  checks libraries?  Any problems with me leaving this one if you've done it?
[22:52] <tumbleweed> xteejyx: you're welcome to it. Please pass the bug upstream
[22:53] <xteejyx> tumbleweed: Ok :) Thank you for all the help, and the nudges to get me to learn myself - much prefer that to just answers
[22:53] <tumbleweed> xteejyx: yeah, I learn more by diving in the deep end and working out what's going on, but it can be hard :)
[22:54] <xteejyx> tumbleweed: Much the same with me, learn the hard way, but it gets results...eventually :)
[23:20] <xteejyx> bug 662986 does this look ok?
[23:20] <xteejyx> tumbleweed: ? ^^
[23:21] <tumbleweed> xteejyx: we use debdiffs for sponsorship, not complete source packages
[23:21] <xteejyx> oops :) ill fix it in a bit
[23:22] <tumbleweed> xteejyx: the changelog entry isn't very descriptive
[23:23] <xteejyx> ?
[23:23] <tumbleweed> xteejyx: it doesn't say what was changed, just that an FTBFS was fixed
[23:23] <tumbleweed> it doesn't even say why it FTBFSed
[23:24] <xteejyx> linker wit gcrypt?
[23:25] <tumbleweed> xteejyx: I would say "Explicitly linked with gcrypt for binutils-gold"
[23:25] <xteejyx> binutils-gold?
[23:26] <tumbleweed> https://lists.ubuntu.com/archives/ubuntu-devel-announce/2010-October/000772.html
[23:27] <xteejyx> why that name though?
[23:27] <tumbleweed> xteejyx: read http://wiki.debian.org/ToolChain/DSOLinking
[23:28] <xteejyx> ok thankyou :)
[23:52] <xteejyx> did my last message go through I got disconnected?
[23:55] <xteejyx> anyone able to help?


[06:53] <dholbach> good morning
[14:22] <jono> pleia2, ping?
[14:24] <jono> any other Fridge editors around?
[14:24]  * smartboyhw is not a Fridge person but would like to see what the news is:)
[14:26] <pleia2> jono: pong
[14:26] <jono> pleia2, hey, so for the news we discussed that is being announced today, can I throw you a pastebin link soon and have you post it?
[14:26] <pleia2> jono: yep :)
[14:26] <jono> thanks pleia2 :-)
[14:27]  * pleia2 is on the east coast today, not 7:30AM here! ;)
[14:27] <smartboyhw> pleia2, \o/
[14:29] <jono> pleia2, lucky you :-)
[14:29] <jono> you are in NY?
[14:30] <pleia2> jono: yeah
[14:30] <jono> pleia2, awesome :-)
[14:30] <pleia2> openstack infrastructure bootcamp :)
[14:30] <pleia2> we will teach people all the infrastructure things \o/
[14:30] <smartboyhw> pleia2, \o/
[14:43] <jono> pleia2, http://pastebin.ubuntu.com/5804894/
[14:43] <jono> :-)
[14:43] <jono> thanks!
[14:44] <smartboyhw> Oh Mir...
[14:45] <pleia2> jono: http://fridge.ubuntu.com/2013/06/27/mir-plans-in-13-10/
[14:46] <jono> thanks pleia2
[14:47] <pleia2> hm, I think we need to fix the size of the video
[14:49] <pleia2> that's better
[16:43] <jono> pleia2, hey, is it possible to make the Mir post appear on planet?
[16:43] <jono> I think it is a category or something
[16:48] <jono> pleia2, also, looks like I gave you the wrong sized video embed, can you change it to: <iframe width="640" height="360" src="//www.youtube.com/embed/8h0m-ZjPxe8" frameborder="0" allowfullscreen></iframe>
[16:48] <jono> thanks!
[16:49] <pleia2> jono: I had to change the iframe because it was way too big and wouldn't fit on the page
[16:50] <pleia2> and you'll have to ping IS to get it to update to planet, it's a caching thing
[16:50] <pleia2> (it's been properly tagged all along)
[16:50] <jono> pleia2, thanks!
[16:50] <pleia2> it'll get to planet eventually, it's just slow due to caching
[16:50] <jono> np
[16:50] <jono> thanks again :-)
[16:50] <pleia2> sure
[16:54] <pleia2> I made the video 600x338, but any bigger than that and it gets covered by the sidebar


[00:31] <CIA-33> usb-creator: evand * r238 trunk/ (debian/changelog gui/usbcreator-gtk.ui):
[00:31] <CIA-33> usb-creator: Set the install window as translatable. Thanks Milo Casagrande (LP:
[00:31] <CIA-33> usb-creator: #414742).
[00:34] <CIA-33> usb-creator: evand * r239 trunk/ (debian/changelog usbcreator/frontends/winui/main_dialog.py): Fix a typo in the Windows frontend (LP: #454926).
[01:24] <CIA-33> usb-creator: evand * r240 trunk/ (debian/changelog gui/usbcreator-gtk.ui):
[01:24] <CIA-33> usb-creator: Use a close button instead of a quit button in the GTK+ frontend
[01:24] <CIA-33> usb-creator: (LP: #285916).
[01:38] <Nivex> crap.  root is found now, but it hangs on "Starting iSCSI initiator service iscsid" during boot
[01:39] <Nivex> not sure if at this point it's outside of the installer's realm
[01:40] <CIA-33> usb-creator: evand * r241 trunk/ (12 files in 8 dirs):
[01:40] <CIA-33> usb-creator: * Change the program title (not the program name) to "Startup Disk
[01:40] <CIA-33> usb-creator:  Creator" as usb-creator writes to more than just USB disks these days.
[01:46] <CIA-33> usb-creator: evand * r242 trunk/debian/changelog: Add an LP bug reference for the previous commit.
[01:54] <Nivex> bug 457767
[02:22] <CIA-33> usb-creator: evand * r243 trunk/ (debian/changelog usbcreator/frontends/gtk/frontend.py):
[02:22] <CIA-33> usb-creator: In the GTK+ frontend, scan the download directory on startup and add
[02:22] <CIA-33> usb-creator: all the CD and disk images (LP: #441104).
[02:57] <xivulon> cjwatson, evand, re UNR, it doesn't look like lupin-casper is installed
[05:46] <CIA-33> ubiquity: superm1 * r3547 ubiquity/debian/ (changelog ubiquity.ubiquity.upstart):
[05:46] <CIA-33> ubiquity: Pass the debug parameters to ubiquity even if running in noninteractive
[05:46] <CIA-33> ubiquity: mode.
[05:54] <CIA-33> ubiquity: superm1 * r3548 ubiquity/debian/ (5 files):
[05:54] <CIA-33> ubiquity: * Don't provide the old init scripts, even under a temporary name anymore.
[05:54] <CIA-33> ubiquity:  - It appears that there is a race condition that can exist between when
[05:54] <CIA-33> ubiquity:  the upstart'ified version and the initscript version start that may cause
[05:54] <CIA-33> ubiquity:  only-ubiquity and automatic-ubiquity to (poorly) fail. (LP: #457858)
[05:54] <CIA-33> ubiquity:  - All login managers in use (gdm and kdm) have converted to upstart now.
[09:18] <CIA-33> usb-creator: evand * r244 trunk/gui/ (usbcreator-gtk.ui usbcreator-kde.ui): Typo.
[10:34] <AnAnt> LP 425704
[10:35] <AnAnt> LP #425704: Capslock don't turn on LED , are you guys aware of this bug ?
[11:19] <xivulon> evand for #457246 can you please check that lupin-casper is installed?
[11:20] <davmor2> xivulon: I can check later today for you if evand can't.   Only a few tests left now
[11:48] <CIA-33> casper: evand * r722 casper/ (2 files in 2 dirs):
[11:48] <CIA-33> casper: Fix broken /cdrom writable test in 43disable_initramfs
[11:48] <CIA-33> casper: (LP: #450259).
[11:52] <CIA-33> casper: evand * r723 casper/debian/changelog: releasing version 1.206
[13:04] <Ng> if I was daft enough to boot into the installer-only mode of a karmic CD (beta I think) and the installer almost imemdiately refuses to resize an ntfs partition, saying an error occurrec while writing the changes, what would I do to get useful information about what went wrong?
[13:06] <evand> Ng: /var/log/syslog, /var/log/partman, /var/log/installer/debug
[13:06] <Ng> evand: not having any desktop around the installer, and with Ctrl-Alt-Fn seemingly not doing anything, I'm not sure how I'm going to get those
[13:07] <evand> hrm, you should be able to switch to a VT
[13:07] <Ng> but I suppose I can reboot into the "Try Ubuntu" version and probably get the same error
[13:07] <evand> perhaps this was alpha 6?
[13:07] <Ng> evand: yeah I was quite surprised by that
[13:07] <Ng> I'll check, I didn't make the USB key being used
[13:07] <evand> they were definitely broken then
[13:07] <evand> okay
[13:07] <evand> cool, thanks
[13:50] <Ng> evand: it's beta, so the VT switch is a bit weird, but a quick read of syslog showed that the reason it was refusing to resize the ntfs was that the resize program was claiming there was an inconsistency and that I should reboot into windows and run chkdsk /f and reboot twice
[13:50] <Ng> doing those things seems to have made it happy again
[13:50] <Ng> possibly a remnant of a previous resize?
[14:25] <davmor2> evand: any chance you could come over to #u-testing for a second guy has reported a bug that got closed but he is using usb/sd converter and not a usb stick for trying unr
[17:29] <bdmurray> is the ubiquity task in bug 268808 necessary with the fix in e2fsprogs?
[19:32] <Nivex> Since installing to root on iSCSI is mentioned so prominently in the Release Notes, is that considered a blocker?
[22:30] <CIA-33> ubiquity: evand * r3549 ubiquity/ (debian/changelog scripts/check-kernels): Calculate the amount of available memory in check-kernels (LP: #413135).


[19:07] <in8> hello all!  I'm here because I was directed here to ask about a cloak.
[19:08] <k1l> in8: link your launchpad account please
[19:08] <in8> sure. https://launchpad.net/~n8berry
[19:09] <Unit193> Generic cloak
[19:09] <IdleOne> !membership
[19:10] <IdleOne> for a "generic" or unaffiliated cloak please ask in #freenode
[19:11] <in8> Thanks.  I was unaware of membership requirements beyond an account.
[21:22] <GTRsdk> is there a channel with Ubuntu members?
[21:22] <elky> there's no dedicated channel, no
[21:23] <elky> what would you need from such a channel?
[21:23] <GTRsdk> I would like to talk to some Ubuntu Members to find out a way to become an Ubuntu Member
[21:23] <k1l> the support and the offtopic channels give you a good chance to meet some members :)
[21:24] <elky> !members
[21:24] <elky> !member
[21:24] <Unit193> Ubuntu Members are normal people too, not much different
[21:25] <elky> GTRsdk, read the information ubottu said, and also https://wiki.ubuntu.com/Membership/Guidelines
[21:26] <GTRsdk> I think it might be somewhat offtopic here, but how would someone do packaging to become an Ubuntu member?
[21:27] <GTRsdk> would that be to a PPA or official repositories?
[21:29] <IdleOne> #ubuntu-packaging might be able to point you in the right direction
[21:30] <IdleOne> with packaging questions but becoming a member isn't all about code
[21:30] <IdleOne> I don't do any coding
[21:30]  * k1l cant code anything
[21:32] <k1l> GTRsdk: it is about showing the membership board, that you contribute to the community. why dont you take a look at users who attend to become a member or visit a membership board meeting in #ubuntu-meeting
[23:13] <GTRsdk> err... I didn't mean to have that get sent here
[23:19] <m4v> you are doing it wrong if you're going to contribute so you can become a member.
[23:23] <IdleOne> +1
[23:23] <ubot4> Factoid '1' not found
[23:46]  * genii-around kicks ubot4
[23:47] <Unit193> Wrong syntax, it's /kick ubot4 Bad bot! ;)
[23:47] <Unit193> Or /abr ubot4 Badie


[00:21] <jrwren> i was about to paste and link and ask "cmaloney, did you see this" but then I look and you retooted it. lul.
[00:44] <cmaloney> heh
[05:13] <llua> https://boards.greenhouse.io/canonical/jobs/5318759?gh_src=692dd0c31us
[05:13] <llua> gonna apply for the lulz
[05:15] <llua> https://old.reddit.com/r/recruitinghell/comments/15kj845/canonical_the_recruitment_process_really_is_that/
[06:45] <Scary_Guy> lol do it
[13:30] <cmaloney> heh
[15:20] <greg-g> I don't want to share my high school grades nor do an IQ test, personally.
[15:21] <greg-g> (ftr, I got 1 B my entire first through twelfth grade, otherwise straight As, not bragging, just really good at test taking)
[15:31]  * dzho nods
[15:31] <dzho> Similar. I didn't do quite so thoroughly well, but good enough that my dad used to tease my typing teacher in social situations for ruining my high school run of straight A's with one B.
[15:41] <greg-g> dzho: nice
[15:43] <greg-g> ironically my 1 B was sophomore year math, which is ironic because I was one of our two people who were selected to go to regional/state math competitions :) (the teacher hated that I never paid attention in her class, I think) (ok, this is bragging a little bit)
[19:29] <jrwren> I don't think i'd ever have gotten hired had rick_h not asked for me. Then I think he regretted it :)
[19:29] <cmaloney> heh
[19:34] <jrwren> LOL, the follow up!!!
[19:34] <jrwren> https://old.reddit.com/r/recruitinghell/comments/15kj845/canonical_the_recruitment_process_really_is_that/jvhubst/
[22:03] <cmaloney> Yeah, defintely has the feel of "you don't understand me because I am so big brained."


[05:04] <InHisName> anyone awake at this time ?
[05:06] <InHisName> I connected up a phone with card slot. Try to use as card reader/writer.
[05:06] <InHisName> dd bs=1M if=moebius-1.1.1.img of=mtp://[usb:002,006]/131074
[05:06] <InHisName> dd: opening ‘mtp://[usb:002,006]/131074’: No such file or directory
[05:08] <InHisName> Properties of 'card' show as mtp://[usb:002,006]/131074     where most mounts show as /dev/bla/bla
[05:16] <InHisName> I tried doing a 'sudo find / -name card'  but it did not find it
[05:16] <InHisName> I have found  mtp=media transfer protocol
[11:47] <jedijf> InHisName: use raspbian - many guides - ip via nmap or router - ssh in
[12:59] <InHisName> My multi card reader wont read 4GB or larger micro SD.   Trying to use a phone as a card reader/writer ??
[13:00] <InHisName> I have three 2GB ones but not finding where they are plugged into, yet.
[13:10] <SamuraiAlba> Good morning, all!
[21:39] <InHisName> bye samurai alba


[11:20] <apachelogger> so
[11:20] <apachelogger> question of the day
[11:20] <apachelogger> should apachelogger upgrade to one-eye-rick?
[11:22] <apachelogger> oh, we are oversized again
[11:30] <bulldog98_> apachelogger: yes
[11:30] <apachelogger> what if it breaks?
[11:30] <bulldog98_> apachelogger: fix it :P
[11:30]  * apachelogger is too stupid
[11:32] <bulldog98_> apachelogger: you don’t seem to be stupid
[11:33]  * apachelogger almost toasted his router yesterday with openwrt :S
[11:34] <bulldog98_> apachelogger: we are more stable than openwrt :)
[11:34] <apachelogger> yeah
[11:35] <bulldog98_> at least I hope so
[11:35] <apachelogger> until ubuntu-x starts uploading stuff again
[11:36] <bulldog98_> apachelogger: do apt-pinning for x :)
[11:38] <bulldog98_> apachelogger: and who cares about x use wayland instead :P
[11:38] <apachelogger> G
[11:57] <bulldog98_> apachelogger: can the icecc in the pbuilder access a scheduler running on the computer running the pbuilder?
[11:57] <apachelogger> sure it can
[11:57] <tsimpson> it communicates over the network, so sure
[12:04] <bulldog98_> apachelogger: then why is says my pbuilder icecc that it’s gone build local?
[12:05] <apachelogger> cause you aint using the hook properly
[12:06] <bulldog98_> apachelogger: so what is needed? the ICECC_VERSION and my PATH are set
[12:06] <apachelogger> read the readme
[12:08] <bulldog98_> apachelogger: I did all the stuff that’s in the README (the first two steps, the others aren’t possible anymore)
[12:29] <bulldog98_> how do I change the shell for root in a pbuilder?
[13:11] <apachelogger> JontheEchidna: pingpinpingping
[13:11] <apachelogger> JontheEchidna: the muon needs to grow dist upgrade functionality
[13:37] <bulldog98_> !search /etc/console-setup/cached.kmap
[13:38] <bulldog98_> !help
[13:38] <bulldog98_> !help search
[13:38] <bulldog98_> !
[13:38] <bulldog98_> ~search
[13:38] <kubotu> incorrect usage, ask for help using 'kubotu: help search'
[13:38] <bulldog98_> kubotu: help search
[13:38] <kubotu> search <string> (or: google <string>) => search google for <string> | wp <string> => search for <string> on Wikipedia | unpedia <string> => search for <string> on Uncyclopedia
[13:38] <bulldog98_> kubotu: help
[13:38] <kubotu> help topics: 10 core modules: auth, basics, config, filters, httputil, irclog, remote, unicode, userdata, wordlist; 56 plugins: alias, autoop, autorejoin, bans, bar, botsnack, chanserv, debug, dns, eightball, excuse, factoids, googlefight, greet, hangman, host, identica, insult, iplookup, karma, keywords, lart, lastfm, map, markov, modes, nickrecover, nickserv, note, poll, q, quote, reaction, remind, ri, roshambo, rot, rss, salut,
[13:38] <kubotu> script, search, sed, seen, shiritori, spotify, time, topic, translator, tumblr, twitter, uno, urban, usermodes, wheeloffortune, wserver, youtube; 31 plugins ignored: use help ignored plugins to see why; 1 plugin failed to load: use help failed plugins to see why (help <topic> for more info)
[15:03] <JontheEchidna> apachelogger: as in, upgrade from one version of Kubuntu to another?
[15:03] <apachelogger> yus
[15:03] <apachelogger> well
[15:03] <apachelogger> detecing the presence
[15:04] <apachelogger> and invoke od-release-upgrade
[15:04] <apachelogger> s/od/do
[15:04] <JontheEchidna> kded/distupgradeedvent
[15:04] <JontheEchidna> the muon-notifier kded module checks for this already
[15:04] <apachelogger> ah cool
[15:05] <apachelogger> now if only the update-manager wasn't complete rubbish and could actually check for devel series
[15:08] <JontheEchidna> the impending hurricane has cancelled the first day of class tomorrow
[15:10] <JontheEchidna> probably because they don't want all the residents moving in today during a hurricane ^^
[15:55] <shadeslayer> ScottK: soprano 2.7.0+dfsg.1-0ubuntu2 does not fix kalzium as well
[16:26]  * Quintasan is back
[16:26] <Quintasan> apachelogger: ping
[16:26] <Quintasan> yofel: ping
[16:27] <yofel> pong, somewhat
[16:27] <Quintasan> yofel: Did you try Riddell's proposed fix to runtime?
[16:27] <yofel> nope (he proposed one?)
[16:29] <Quintasan> Yes he did, but now that I'm back I will try it in a second
[16:46] <apachelogger> well then
[16:46] <apachelogger> this update only screwed me over mostly
[16:46] <apachelogger> also it managed to do it worse than any before
[16:46] <apachelogger> hooray
[16:47] <yofel> really? what's broken now?
[16:47] <apachelogger> fglrx results in black screen
[16:47] <apachelogger> with ati driver no plymouth is shown and of course nice and cosy graphics artifacts are to be enjoyed
[16:48] <apachelogger> of course the xrandr stuff is still royally broken so my dual screen layout is all fckd up
[16:49] <apachelogger> oh
[16:49] <apachelogger> and there is this flash install thing
[16:49] <apachelogger> that now installs all of x86
[16:49] <apachelogger> thanks to qapt not being able to handle multi arch
[16:51] <apachelogger> RuntimeError: the PyQt4.QtCore module is version 1 but the PyKDE4.kdecore module requires version -1
[16:52] <apachelogger> http://i.imgur.com/cZCXq.png
[16:52] <apachelogger> truth be told, I expected an icon there
[16:53] <Quintasan> Grrrr
[16:53] <Quintasan> Now we need rebuild of kdelibs and runtime and it will most likely work
[16:55] <apachelogger> uhhh
[16:55] <apachelogger> rekonq
[16:55] <apachelogger> not wanting me google cookies
[16:55] <apachelogger> that is cool
[17:03] <apachelogger> chop chop make[2]: *** No rule to make target `/usr/lib/libQtTest.so', needed by `phonon/libphonon.so.4.5.56'.  Stop.
[17:04] <apachelogger> row row row your boat gently down the stream
[17:05]  * apachelogger kisses rekonq goodbye as it decided to hang itself
[17:09] <apachelogger> ok
[17:09] <apachelogger> someone explain that error to me
[17:10] <Quintasan> apachelogger: multiarch
[17:10] <apachelogger> that is not an explainatin of the error
[17:10] <apachelogger> actually
[17:10] <apachelogger> on second thought
[17:10] <apachelogger> I dont give a rats ass why the error is there
[17:10] <apachelogger> I want it gone
[17:10] <apachelogger> like now
[17:10]  * bulldog98 suggest apachelogger not to use flash at all :)
[17:10] <yofel> apachelogger: rebuild of phonon should fix it I guess
[17:10] <Quintasan> apachelogger: Fix it yourself if you know how
[17:11] <apachelogger> yofel: if that was not what I was doing
[17:11] <yofel> apachelogger: ah, then that's probably qtzeitgeist still not being rebuilt
[17:13] <apachelogger> ah
[17:13] <apachelogger> the madness
[17:17] <apachelogger> ahhh
[17:17] <apachelogger> broken opengl
[17:17] <apachelogger> what more does a man need
[17:18] <Quintasan> bber?
[17:18] <Quintasan> beer even
[17:41] <shadeslayer> apachelogger: ever written code in Objective C?
[17:42] <apachelogger> read
[17:42] <apachelogger> I do not write code that only makes sense on proprietary patent supporting vendor locked in systems
[17:43] <shadeslayer> hehe, just asking :P
[17:43] <shadeslayer> i
[17:43] <apachelogger> also I need to reboot
[17:43]  * shadeslayer hits his keyboard
[17:43]  * apachelogger sighs about the crap state of oneiric
[17:43] <shadeslayer> apachelogger: yeah, quite broken it is
[17:43]  * shadeslayer blames shadeslayer
[17:44] <shadeslayer> no sound again it seems
[18:07] <apachelogger> hm
[18:07] <apachelogger> shadeslayer, Quintasan: you know, I absolutely fail to get telepathy-kde to do anything useful
[18:10] <shadeslayer> apachelogger: depends on what you're trying to do
[18:10] <apachelogger> show my contacts
[18:10] <shadeslayer> and also depends on how you installed
[18:10] <apachelogger> or have the kcm remember my accounts for starters ^^
[18:10] <apachelogger> shadeslayer: ppa
[18:10] <shadeslayer> apachelogger: you need gnome-keyring for saving accounts iirc
[18:10] <shadeslayer> Quintasan: ^^ did you add that to depends?
[18:11] <shadeslayer> apachelogger: telepathy can't store passwords in kwallet yet
[18:11]  * apachelogger giggles
[18:11] <shadeslayer> they're working on integration for ksecretservice as of now
[18:11] <apachelogger> epic
[18:11] <shadeslayer> yup
[18:12] <apachelogger> I suppose that also explains all the rubbish it installed
[18:12]  * apachelogger autoremoves
[18:12] <shadeslayer> apachelogger: http://community.kde.org/Real-Time_Communication_and_Collaboration/Troubleshooting#TroubleShooting
[18:12] <Quintasan> absolutely fabulous
[18:12] <apachelogger> now
[18:12] <apachelogger> you know
[18:12] <shadeslayer> apachelogger: what else? :)
[18:12] <apachelogger> another famous piece of KDE 4 technology has a troubleshooting wiki
[18:12] <Quintasan> I can install nvidia-glx but it doesnt work
[18:12] <Quintasan> !#$%=&*(
[18:13] <apachelogger> also another closely related one
[18:13] <apachelogger> they are called akonadi and nepomuk
[18:13] <apachelogger> if you google them you will come to understand why I find it a bit worrying when software needs a troubleshooting documentation
[18:14] <apachelogger> Quintasan: define does not work
[18:14] <Quintasan> apachelogger: no screens found,  fails to load module and tells me to look into logs but nothing there
[18:14] <apachelogger> I have the funniest stuff with fglrx here
[18:15] <apachelogger> if I do a normal boot up it will kernel panic at X start or something
[18:15] <apachelogger> if I boot in failsafe and fire up kdm manually everything works as expected
[18:15] <apachelogger> also... is it just me or does oneiric boot take insanely long?
[18:16] <Quintasan> EE failed to load module "nvidia" (module-specific error, 0)
[18:16] <Quintasan> sup
[18:17]  * apachelogger must remember to not listen to bulldog98
[18:17] <bulldog98> apachelogger: sorry for me everything works fine
[18:18]  * apachelogger thinks bulldog98 should do bug triage
[18:18] <bulldog98> Quintasan: you have to blacklist nouveau
[18:18] <Quintasan> shadeslayer: also, who on earth made KDE Telepathy using gnome-keyring?
[18:19] <shadeslayer> Quintasan: they use telepathy as the backend
[18:19] <shadeslayer> which uses gnome-keyring to store stuff
[18:19] <shadeslayer> apachelogger: yep, takes *alot* of time here
[18:19] <Quintasan> shadeslayer: Uhm, I lol'd here
[18:20] <apachelogger> Quintasan: it is gnome people writing a technology, kde people coming along, adopting the technology and willingly take all the shit from aforementioned gnome people
[18:21]  * Quintasan also can't get his second monitor to work
[18:21] <Quintasan> ffs
[18:21] <shadeslayer> they're working on a ksecretservice backend
[18:21] <apachelogger> let's install opensuse
[18:21] <shadeslayer> so, there's some progress there
[18:21] <Quintasan> apachelogger: I really don't understand why start telepathy-kde when still depending on gnomeshit
[18:21] <apachelogger> I have friends there
[18:21] <shadeslayer> sure
[18:21] <apachelogger> we surely woud be most welcome
[18:22] <apachelogger> Quintasan: that is the beauty of it ... KDE people bowing to the superior might of GNOME
[18:22] <apachelogger> shadeslayer: there is no need for a backend
[18:22] <Quintasan> >superior
[18:23] <Quintasan> >GNOME
[18:23] <apachelogger> kss implements the secret storage spec
[18:23] <apachelogger> which gnome-keyring implements too
[18:23] <apachelogger> one can use both with one implementation
[18:23] <apachelogger> that is the entire point
[18:23] <apachelogger> BUT
[18:23] <Quintasan> I think Sput said that seeing GTK code makes him want to poke his eyes out with a rusty fork
[18:23] <apachelogger> kss has been in development for forever and 3 weeks
[18:23] <bambee> evening
[18:23] <apachelogger> and I am not entirely sure it will land in 4.8 either
[18:23] <apachelogger> AND
[18:23] <apachelogger> AFAIK the spec is still in draft stage
[18:24] <JontheEchidna> lost power for 20 minutes there...
[18:24] <apachelogger> JontheEchidna: hows the weather?
[18:25] <JontheEchidna> ironically, the power went out right as the hurricane past us :<
[18:25]  * apachelogger wonders if his comment on kde bug 267319 was too provocative
[18:25] <JontheEchidna> it never got too bad. It was a bit windy and there was  a lot of rain
[18:25] <yofel> Quintasan: oh, that error, boot with nomodeset then nvidia will work
[18:25] <Sput> Quintasan: and I still stand by that utterance
[18:25] <JontheEchidna> now there's a nice breeze, and less rain
[18:26] <apachelogger> JontheEchidna: ah, not much of a hurricane then, that is good :)
[18:26] <JontheEchidna> yeah, it was downgraded to a tropical storm by the time it got to me
[18:26] <apachelogger> Sput: surely your new employer will have some gtk stuff to do :P
[18:26]  * apachelogger only has good memories of gtk and glib
[18:27] <Sput> apachelogger: surely I wasn't hired for that :)
[18:27] <JontheEchidna> apachelogger: that guy is an ass :(
[18:27] <apachelogger> Sput: difficult times my friend :P
[18:27] <Sput> mmmh. gnome keyring seems to be optional in telepathy-mission-control
[18:27] <apachelogger> JontheEchidna: yus, always has been
[18:28] <Sput> not sure if they can also use kwallet somehow
[18:28] <apachelogger> Sput: or maybe it is just badly engineered :P
[18:28] <Sput> my telepathy-mission-control is built without gnome keyring support, and KDE manages to remember my passwords
[18:29] <apachelogger> unencrypted storage in gconf then
[18:29] <apachelogger> which would probably make sense
[18:31] <Sput> yeah looks like it, at least my kwallet doesn't seem to be storing account pws
[18:33]  * apachelogger really cannot manage to find the energy to read JontheEchidna's mail on multiarch
[18:33] <JontheEchidna> lol
[18:33] <apachelogger> actually I wonder what is with the tiredness these days
[18:33] <apachelogger> must be side effect from being sober
[18:33]  * bulldog98 has already done that
[18:33] <apachelogger> rather horrible
[18:33] <apachelogger> bulldog98: yet you did not give input :P
[18:33] <bulldog98> apachelogger: I was the guy reporting the problem, so that’s input :P
[18:35] <apachelogger> true
[18:36] <bulldog98> apachelogger: I would have given a mail, but kmail is broken (doesn’t send mails atm)
[18:37] <bulldog98> and it seems like I can blame ScottK or yofel for that
[18:38]  * bulldog98 is in favor of option 3 cause we keep binary compitabilty
[18:38]  * bambee wonders if kmail works sometimes
[18:39] <bulldog98> bambee: it will with release 42
[18:42] <bambee> Will it work as well as other releases ? :P (no, I am kidding)
[18:42] <bulldog98> normaly kmail works quite well
[18:53] <sheytan> apachelogger: ping ping
[18:53] <sheytan> can I have the kdepase page again?
[18:53] <sheytan> I couldn't compile phonon last time, some errors
[19:20] <apachelogger> sheytan: it is gone
[19:20] <apachelogger> check your shel history
[19:20] <apachelogger> shell even
[19:20] <apachelogger> or maybe it was shellll
[19:20] <apachelogger> sheeel
[19:21] <apachelogger> something like that anywayz
[19:23] <sheytan> i did, it's gone ;/
[19:23] <sheytan> if you could, mail me it
[20:28] <apachelogger>     KIO::Integration::AccessManager::putReplyOnHold(reply);
[20:28] <apachelogger> either that thing is broken or rekonq is using it wrong
[20:28] <apachelogger> it causes quite the hang
[20:28] <apachelogger> when downloading a file
[20:28] <apachelogger> (or trying to)
[20:28] <apachelogger> what I find best about it is how that can block the UI
[20:29] <apachelogger> *thumbs up*
[20:29] <bulldog98> apachelogger: thread support is planed, but nobody steped up for that
[20:59] <CIA-1> [kubuntu-default-settings] Harald Sitter<EMAIL_ADDRESS>*<EMAIL_ADDRESS>* (debian/changelog share/config/kdeglobals) Set rekonq as explicit browser application in kdeglobals. Otherwise konqueror will be used as default when both are installed.
[21:01] <apachelogger> perhaps we should chop kde-workspace's history
[21:01] <apachelogger> it has become rather fat
[21:04] <apachelogger> yofel: ping
[21:06] <yofel> ?
[21:07] <apachelogger> yofel: why for the love of kent beck does the install default wallpapers buttons install the wallpapers from workspace and artwork?
[21:07] <apachelogger> I find this the ultimate overkill
[21:07] <apachelogger> plus
[21:07] <apachelogger> JontheEchidna: qapt aint asking me whether I want to install that rubbish
[21:08] <apachelogger> it just asks for auth and I have no idea what for
[21:08] <JontheEchidna> the wallpapers?
[21:08] <apachelogger> yus
[21:08] <yofel> well, what do you want to install then? Formery the button was installing stuff from artwork, then one of the artwork folks complained that we install the artwork stuff without installing the workspace wallpapers first
[21:09] <JontheEchidna> you did click the "install wallpapes" button, so presumably you wanted to
[21:09] <yofel> adding 2 buttons is nonsense, and adding a dialog that asks you which to install isn't something I know how to do
[21:09] <apachelogger> JontheEchidna: yeah but right now that drags in 10003482^50 trazillion TiB
[21:10] <apachelogger> it would be jolly nice to tell me before hand, because I have 56k and could rather not effort to wait that long
[21:10] <apachelogger> yofel: no, it installed the workspace one
[21:11] <yofel> apachelogger: well, _now_ it installs both
[21:11]  * apachelogger files the bukx
[21:11] <yofel> before it installed the one from artwork
[21:11] <apachelogger> because you broke it all
[21:11] <yofel> huh?
[21:11] <apachelogger> at the time the feature was introduced there were no wallpapers in artwork
[21:11] <yofel> I never wrote that patch
[21:11] <yofel> ah
[21:12] <yofel> well, what's that button *supposed* to do then?
[21:12] <yofel> and how is lord user supposed to know how to install the wallpapers that are shipped with kde?
[21:12] <yofel> even in artwork
[21:13] <apachelogger> package manag0r
[21:13] <apachelogger> the wallies in workspace are the latest  hot ones, so we want those
[21:13] <apachelogger> not the bazillion wallies before the current ones
[21:13] <yofel> yeah, like a kde user will look in the package manager to add wallpapers...
[21:14] <yofel> that's why that button is there in the first place
[21:22] <apachelogger> yofel: yes, to give the default
[21:22] <apachelogger> not every wallpaper ever
[21:24] <apachelogger> bug 836276
[21:25] <apachelogger> yofel: so what do we do with the button?
[21:26] <yofel> hm, I agree with the descriptions. We somewhat decided to leave the renaming of the package to the debian folks though
[21:26] <yofel> as for the button...
[21:27] <yofel> I didn't want to break the behaviour the button had before, so I just added it. If you think installing the artwork wallpapers isn't worth the download size then drop it
[21:27] <apachelogger> roger
[21:28] <apachelogger> who wants to bring in a new snapshot of qtwebkit?
[21:28] <apachelogger> the current one is utter rubbish
[21:28] <apachelogger> or maybe rekonq is
[21:28] <apachelogger> on that note
[21:28] <apachelogger> we need a newer snapshot of rekonq
[21:29] <apachelogger> oh right
[21:29] <apachelogger> kde-wallpapers is now a seperate source package, no?
[21:29] <yofel> yep
[21:30] <apachelogger> you shoudl change the bug then :P
[21:30]  * apachelogger installs qtwebkit-dbg before rekonq goes down again
[21:30] <apachelogger> funniest thing
[21:30] <apachelogger> if rekonq went down once, it will again when restoring
[21:30] <apachelogger> so I think this is a qtwebkit issue really
[21:32] <yofel> bah, didn't pay enough attention to the packages
[21:33] <apachelogger> man
[21:33] <apachelogger> webkit is terrible
[21:33] <apachelogger> 189 mib of dbg symbols
[21:33] <apachelogger> that is just insane
[21:34] <apachelogger> do we not lzma them, or something?
[21:34] <apachelogger> --with pkgkde_symbolshelper,lzma
[21:34] <apachelogger> should
[21:34] <apachelogger> :S
[21:34] <apachelogger> imagine how big that is without lzma!!!!
[21:38] <apachelogger> #6  primarySimpleFontData (f=0x7f3d7ecabe68, this=0x0) at platform/graphics/FontFallbackList.h:61
[21:38] <apachelogger> mhhh
[21:38] <apachelogger> "this be null, go away"
[21:58] <apachelogger> JontheEchidna: ping
[21:58] <JontheEchidna> pong
[21:58] <apachelogger> JontheEchidna: cant you get the architecture without the name from apt?
[21:58] <apachelogger> or is it literally appended to the name?
[21:59] <apachelogger> in the binary cache
[22:00] <JontheEchidna> the arch is not part of the name in the binary cache, I don't think
[22:01] <JontheEchidna> which is why apt's fullname function has to append it + return an std::string
[22:01] <JontheEchidna> it can't simply point at the name in the binary cache
[22:01] <apachelogger> right
[22:01] <apachelogger> BUT
[22:01] <apachelogger> why is there no explicit interface to query the arch?
[22:02] <JontheEchidna> hmm
[22:02] <apachelogger> neither of the approaches you presented seems very object oriented... the arch would just be a property of a package, not of the package's name
[22:03] <apachelogger> if a consumer were to require a fullname they could still concat themselfs
[22:03] <apachelogger> which IMHO makes loads more sense than forcing users to go the other way around and split the fullname
[22:05] <apachelogger> because for muon you'd not want the names to be displayed with arch anyway, but perhaps a dropbox where the user can select the arch of the package to install (or inform the user that only a x86 version of this package is availabe and that all deps will thus be fullfilled using x86 blah blah)
[22:05] <apachelogger> (in the muon UI anyway)
[22:05] <JontheEchidna> apachelogger: would it be possible for you to install a foreign-arch package with dpkg or apt-get, and then paste the output of apt-cache show foo?
[22:05] <apachelogger> for the software center you'd only need it for dep resolving anyway
[22:05] <JontheEchidna> it might help me, since I'm not on a 64-bit system
[22:07] <apachelogger> JontheEchidna: http://paste.ubuntu.com/676845/
[22:07] <JontheEchidna> hmm, apt-cache show says Architecture: amd64 :s
[22:07] <JontheEchidna> oh, but when you specify :i386 it says i386
[22:08] <apachelogger> that is because it will prefer the x64 version of course
[22:08] <apachelogger> flash might make more sense
[22:08] <apachelogger> sec
[22:09] <apachelogger> JontheEchidna: http://paste.ubuntu.com/676846/
[22:09] <apachelogger> -installer has a x64 version
[22:09] <apachelogger> BUT
[22:09] <apachelogger> -downloader only can do x86, so it shows the only available arch by default
[22:09] <apachelogger> which is i386
[22:10] <JontheEchidna> ok, that's good
[22:10] <JontheEchidna> it would be trivial to add an arch() function to Package
[22:11] <apachelogger> right, then you just need to look at the host arch I suppose and prefer that whenever possible
[22:11] <JontheEchidna> hmm, I think my lappy is 64-bit capable, actually. I should just reinstall w/ 64bit
[22:12] <apachelogger> for 11.10 simply filtering duplicated entries based on best match for host arch should be sufficient
[22:12] <apachelogger> later you can have a gui integration in muon to install/remove one specific arch
[22:12] <apachelogger> which will probalby be a bit tricky
[22:12] <apachelogger> UIwise
[22:12] <JontheEchidna> yeah, since it's tricky to know which packages can be multiarch'd
[22:13] <JontheEchidna> oh, actually there is the MultiArch: field
[22:13] <apachelogger> well, name occurs more than once -> add checkbox with foreach entry, arch()
[22:13] <apachelogger> uh
[22:13] <apachelogger> even better
[22:14] <apachelogger> anyhow, I think doing the actual UI is the really tricky part there ^^
[22:14] <JontheEchidna> yeah
[22:14]  * JontheEchidna downloads 64-bit iso
[22:15] <JontheEchidna> blast, we're oversized. I'll have to use a dvd :/
[22:15] <apachelogger> no usb stick?
[22:16] <JontheEchidna> not big enough, no
[22:16] <apachelogger> uff, I should send you some :P
[22:16] <JontheEchidna> all I has is this 128 MB one I use for school papers, etc
[22:16] <apachelogger> Quintasan: not only do I have devices coming out my ears, I also have usb sticks coming out my nouse :P
[22:16] <JontheEchidna> lol
[22:17] <apachelogger> The custom templates folder for identity "Ubuntu" does not exist (anymore); therefore, the default templates folder will be used.
[22:17] <apachelogger> way to go kmail
[22:17] <JontheEchidna> I can't use kmail. It's not able to show my kubuntu-devel folder anymore
[22:17] <apachelogger> tooo big
[22:17] <apachelogger> cleanup :P
[22:17] <JontheEchidna> only 8k mails in thar
[22:18] <JontheEchidna> plus it has this habit of duplicating mails
[22:19] <JontheEchidna> apachelogger: while I'm downloading, could you search for libc6 in synaptic and tell me if it has duplicate entries? (It's using solution 1 in my mail)
[22:20] <apachelogger> awww
[22:20] <apachelogger> I only ripped that piece of fluff out earlier today :(
[22:20] <JontheEchidna> lol
[22:20] <apachelogger> oh
[22:20] <apachelogger> and my vbox is broken
[22:20] <apachelogger> darn it
[22:21] <JontheEchidna> if there's more than one it means that apt has two PkgIterators for both the native and multiarch versions
[22:21] <JontheEchidna> and QApt::Package is a OO class wrapping a PkgIterator
[22:22] <JontheEchidna> well, it has to look at several other apt classes to get all the info you'd want from a package, but that's because libapt is an un-OO piece of crap
[22:22] <apachelogger> lol
[22:23] <apachelogger> JontheEchidna: well, IMHO that is how it is supposed to be
[22:23] <apachelogger> they are 2 different packages after all
[22:24] <JontheEchidna> initially I think it'll be ok to show both
[22:24] <apachelogger> so it is essentially up to the API consumer to implement multiarch support
[22:25] <apachelogger> i.e. the consumer would decide which to filter, or at least tell libqapt what policy to implement (return all, return only host, return only host except when no host is available, return arch xy)
[22:25] <apachelogger> or you implement policy handling right away and default to return - only host except when no host is available -
[22:26] <apachelogger> that way even without change API consumers get a sane package listing with multiarch systems
[22:29] <JontheEchidna> I'm trying to work out how I'd do this:
[22:29] <JontheEchidna> When initialized, QApt::Backend creates a Package object for every PkgIterator in the apt depcache
[22:30] <JontheEchidna> it then stores all of those in a QList
[22:30] <JontheEchidna> (a qlist of pointers)
[22:31] <JontheEchidna> The Muon Package Manager's PackageModel is populated with Backend::availablePackages() which returns a copy of that list
[22:31] <apachelogger> that will need to become more expensive
[22:31] <JontheEchidna> that's ok I think. sorting within the PackageModel is the bottleneck there anyways
[22:32] <JontheEchidna> so if I create some flags, I can make a Backend::packages(ArchTypeFlag) that will filter out archs based on ArchTypeFlag
[22:33] <JontheEchidna> and return a list of only native, only foreign, or both
[22:33] <apachelogger> you'd probably also want specific foreign
[22:33] <apachelogger> but for now I'd keep it to the bare minimum necessary for sane behavior
[22:33] <JontheEchidna> yeah
[22:34] <apachelogger> thing is, how would you implement the algorithm
[22:34] <JontheEchidna> the amount of archs dpkg/apt, et al. support is not guaranteed anyways
[22:34] <JontheEchidna> so if we suddenly add an arch we'd need a new flag
[22:34] <apachelogger> you could just have a property
[22:35] <apachelogger> QList<arches>
[22:35] <apachelogger> arches being a QString
[22:35] <apachelogger> or QBA perhaps
[22:35] <JontheEchidna> bleh, that means doing a strcmp when filtering :(
[22:35] <JontheEchidna> well, the QString equivalent, but yeah :P
[22:35] <apachelogger> you'll need strcmp anyway
[22:36] <apachelogger> or how would you implement the algorithm?
[22:36] <JontheEchidna> so mr consumer calls packages(NativePackages)
[22:36] <apachelogger> because my first thought is to have a map<ql1s, package*>
[22:36] <apachelogger> in the thing that makes the qlist
[22:37] <apachelogger> then for each iterator you check if the ql1s is already in the map
[22:37] <JontheEchidna> we go to our store of every package, go through each, and if package arch matches native arch, add to the list we return
[22:37] <apachelogger> if so you check your policy
[22:38] <JontheEchidna> with the map we only incur the cost of checking the arch once
[22:38] <JontheEchidna> right?
[22:39] <JontheEchidna> at the cost of storing a qmap with 35,000 nodes :P
[22:39] <apachelogger> you throw the map away afterwards
[22:39] <apachelogger> once built you only need the resulting qlist
[22:40] <apachelogger> also it might be a map with 35,000*a nodes :P
[22:40] <apachelogger> oh
[22:40] <apachelogger> actually
[22:40] <apachelogger> if policy is return all -> use existing algorithm
[22:40] <apachelogger> otherwise use the qmap
[22:40] <apachelogger> phew
[22:40] <apachelogger> now that just saved our cpu from setting on fire \o/
[22:41] <JontheEchidna> so you'd go through each package in the canonical list, map package to arch, then make a qlist from the packages with the correct arch?
[22:41] <apachelogger> nope
[22:41] <apachelogger> way too expensive
[22:41] <apachelogger> so
[22:41] <apachelogger> you iter over packages in libapt
[22:42] <apachelogger> foreach iter:
[22:42] <apachelogger> if policy is showmeall -> add to final qlist
[22:42] <apachelogger> else -> invoke map based algorithm
[22:42] <apachelogger> looks like this:
[22:42] <JontheEchidna> oh, I should add that the iterating over libqapt iterators is only done once when Backend::init() is called
[22:42] <apachelogger> get latin1name
[22:42] <apachelogger> check if latin1name is already in map
[22:42] <apachelogger> if not -> add
[22:43] <apachelogger> else -> invoke policy check
[22:43] <apachelogger> looks like this:
[22:43] <JontheEchidna> ::init() populates a QList<Package *>, and this list doesn't change
[22:43] <apachelogger> uha
[22:43] <apachelogger> uhaaaa
[22:43] <apachelogger> JontheEchidna: then you need your own container structure
[22:43] <apachelogger> similar to a map
[22:44] <apachelogger> struct {QLatin1String string, Package *pkg}; where pkg is in the master list
[22:44] <JontheEchidna> or
[22:45] <JontheEchidna> hmm, nvm
[22:45] <apachelogger> well, you need a more complicated container, as you need to store the whole list and then build a filtered list
[22:45] <apachelogger> and I still did not finish explaining my approach to the filtering :P
[22:46] <apachelogger> so, if there is already a package with the same name in the container, then you invoke a policy check
[22:46] <apachelogger> which basically goes: does current Package*->arch() match policy better than Package* in the container
[22:47] <apachelogger> e.g. in the container we have an i386 Package, but host is amd64 -> overwrite the entry with our new Package * when amd64 is preferred
[22:48] <apachelogger> if the policy is listAllForeign you'd skip the amd64 package
[22:49] <apachelogger> if you want poth you simply add it to the container (so now you have two Package* with the same latin1name in your container)
[22:49] <apachelogger> so a lot of strcmp but still relatively cheap
[22:50] <apachelogger> (as a matter of fact it might just make more sense to trade the QL1S instance for the pointer dereference)
[22:50] <apachelogger> so you'd only have a list as container
[22:51] <apachelogger> but I don't think you'd get away from the n*n iteration to filter
[22:52] <JontheEchidna> if only APT's multiarch impl. wasn't so hacky :(
[22:52] <JontheEchidna> they probably did it the way they did so they wouldn't invalidate the binary package cache format
[22:52] <apachelogger> yus yus, then again qstr stuff is probably more efficient than any std::string thing anyway ^^
[22:53] <apachelogger> so I think their stuff is just fine from a qapt POV
[22:54] <apachelogger> in fact I could not think of a much better approach for the APT impl
[22:54] <apachelogger> JontheEchidna: about your syantpic question -> no duplicates from what I can tell
[22:55] <JontheEchidna> hmm
[22:55] <apachelogger> also it does not indicate multiarch ness or anything
[22:55] <apachelogger> very useless tool :S
[22:55] <apachelogger> oh
[22:55] <apachelogger> JontheEchidna: nvm
[22:55] <JontheEchidna> it doesn't say libc6:i386 or anything?
[22:55] <apachelogger> libc6
[22:55] <apachelogger> and then there is libc6-amd64
[22:55] <apachelogger> mind me, the vbox is x86 it seems ^^
[22:56]  * apachelogger installs natively
[22:56] <JontheEchidna> my iso is half done downloading
[22:59] <apachelogger> ah yes
[22:59] <apachelogger> JontheEchidna: proper duplication
[22:59] <JontheEchidna> ok, good
[22:59] <apachelogger> libc6 and libc:i368
[22:59] <apachelogger> eh libc6:i386
[22:59] <apachelogger> also there is libc6-i386
[22:59] <apachelogger> :O
[22:59] <apachelogger> wtf
[23:00] <JontheEchidna> that's the pre-multiarch solution, I think
[23:00] <apachelogger> yeah
[23:00] <apachelogger> looks like it
[23:01] <apachelogger> JontheEchidna: so kmail will, I sent a quick summary of this as reply to your mail
[23:01] <JontheEchidna> cool, thanks
[23:47] <JontheEchidna> brb, reinstalling kubuntu
[23:56] <JontheEchidna> Default desktop doesn't look to shabby: http://i.imgur.com/Jpa6Q.png
[23:59] <apachelogger> try it at a non-widescreen resolution
[23:59] <apachelogger> the wallpaper almost made me throw up