=== beuno-afk is now known as beuno === mattw_ is now known as mattw === rickspencer3 is now known as rickspencer3-afk === Cuddles is now known as Richie [03:25] Hmm, it seems like wine1.2-gecko was deleted from the archive [03:26] or maybe it never built in the first place... [03:30] /c/c [04:26] #ubuntu-programming [05:02] Hello there! The new 2.6.31-7-generic kernel gets stuck (i.e. just sists there, won't boot up) on my lenovo T61 after unlocking an encrypted physical volume. What's the best way to debug this? [05:03] al-maisan: Does it work if you boot -6? [05:04] StevenK: yes, that's what I fell back to .. [05:04] i.e. that's the kernel I am running presently [05:12] al-maisan: Someone reported that the 7 kernel breaks encrypted lvm in here yesterday, I think it was dtchen, who is not currently around atm. [05:12] TheMuso: ah, I see, so it's a known issues. That's good. Thanks for letting me know! [05:13] Whether a bug has been filed, I don't know. [05:13] I'd say there has been. [05:13] OK. I'll search for it. === johe__ is now known as johe [05:30] TheMuso: Bug #418514 [05:30] Launchpad bug 418514 in linux "linux-image-2.6.31-7.27-generic fails to boot lvm" [Medium,Confirmed] https://launchpad.net/bugs/418514 [05:37] al-maisan: good to hear that there is one. [05:37] * TheMuso notes that he is not affected by this. [05:37] Yeah .. just wanted to make sure it's a known issue. [05:51] Hrm so its not just encrypted LVM, but LVM as well. Hrm maybe I'll have to avoid that kernel as well, since I use LVM not encrypted here... [05:52] yep. === thumper is now known as thumper-cooking === thumper-cooking is now known as thumper === thumper is now known as thumper-cooking [06:12] good morning [06:14] evening! [06:20] good morning dholbach :) [06:20] hey al-maisan! [06:22] Good morning [06:23] pitti: Morning! [06:23] hey StevenK [06:23] pitti: It seems all of libcupscgi1 libcupsdriver1 libcupsmime1 libcupsppdc1 cups-ppdc ended up in universe, I promoted them about 15 minutes ago [06:23] StevenK: ah, thanks [06:26] pitti: When you have a sec, could you look at bug 419029 ? [06:26] Launchpad bug 419029 in humanity-icon-theme "Please promote humanity-icon-theme" [Undecided,New] https://launchpad.net/bugs/419029 [06:28] StevenK: approved, bug updated [06:29] no-brainer [06:34] pitti: Thanks, I'll promote it [06:41] can we all try to unsubscribe the sponsors teams from requests that are very old and waiting for input? [06:41] the list is HUGE [06:42] vorian: what about bug 386428? [06:42] Launchpad bug 386428 in xom "Please merge xom_1.2.1-1 (universe) from debian unstable" [Wishlist,In progress] https://launchpad.net/bugs/386428 [06:46] ArneGoetje: what about bug 407649? [06:46] Launchpad bug 407649 in scim-anthy "Sync scim-anthy 1.2.7-1 (main) from Debian unstable (main)." [Undecided,New] https://launchpad.net/bugs/407649 [06:49] ogra: can you take a look at bug 385850? [06:49] Launchpad bug 385850 in hundredpapercuts "Ship fewer screensavers by default" [Low,Confirmed] https://launchpad.net/bugs/385850 [06:59] * nixternal hugs dholbach [07:00] * dholbach hugs nixternal back [07:21] dholbach: pitti will take care of the sync today [07:21] already done [07:21] oh, I didn't know that you filed new sync bugs, please close them [07:22] I thought the requests in the MIR bug were enough [07:22] dholbach, ArneGoetje ^ [07:22] pitti: oh, sorry, that one is scim-anthy [07:23] oops, indeed, sorry [07:23] yep [07:23] I synced ibus [07:23] nevermind me then [07:23] if scim-anthy should go to universe, we should be able to sync it [07:23] and not promote a new recommends to main [07:26] dholbach: well, I will change the language-support-input-* dependencies today to pull ibus instead of scim. So, I think it's safe to put it into universe [07:27] pitti: looks good to you? [07:27] sure, but it shouldn't be done before it actually gets demoted [07:27] ok [07:27] I'll leave it like that then [07:28] so, change the seeds and language-support- stuff first? [07:28] yes [07:37] if anybody could double-check bug 414298 I'd appreciate it [07:37] Launchpad bug 414298 in devscripts "Please merge devscripts_2.10.53 from Debian unstable" [Undecided,Confirmed] https://launchpad.net/bugs/414298 [07:42] mvo: any issues with that xapian-core patch? [07:44] ojwb: no, its seems to be working just fine. no open bugs or crashreports since I uploaded it [07:45] thanks again for the patch! [07:46] cool, I'm just preparing a new upstream release [07:48] I guess the "machine does not power down on shutdown" bug is already known? IIRC it happens since the -7 kernel [07:52] dholbach: I have it here too [07:58] * pitti too [08:00] * TheMuso is not yet on 7 due to the lvm bug. === thumper-cooking is now known as thumper === tkamppeter_ is now known as tkamppeter [08:59] pitti: would it be possible to seed ibus-m17n with its dependencies onto the LiveCD? [08:59] ArneGoetje: I didn't compare sizes yet; how much space does scim and the default tables take? [09:00] pitti: how do I find out? [09:00] apt-cache show packagename | grep ^Size [09:00] for all the scim related packages we ship by default [09:01] you can use the .manifest files on cdimage.u.c. daily-live/current to see the list of packages which we ship by default [09:01] thanks, that would help alot [09:02] an easier method might be to have a clean chroot, and then do "apt-get install " and see how much stuff apt needs to download [09:02] with "all packages" being either all seeded scim or all to-be-seeded ibus packages [09:02] that's quick for comparing, since it also considers all library dependencies [09:03] sudo apt-get install ibus ibus-m17n on my system -> 3370kB [09:03] (I think you needed some more, right?) [09:05] Hi,is it possible to collect data for an existing bug ? I mean that ubuntu-bug collect data for a package or a PID but not for an existing bug. [09:05] kagou: yes; man apport-collect [09:06] oh [09:06] damned ! thanks pitti [09:06] :) [09:07] may be ubuntu-bu should be enhanced to report to bug too ? [09:07] pitti: I'll make a list [09:07] kagou: yes, it could be made clever enough for that [09:16] oh, seriously, -7 breaks lvm? that's going to be amusing for the installer work I need to get done TODAY [09:17] how exactly does it break lvm? the bug is not very clear, and the one clear symptom (padlock_sha failing to load) wouldn't affect ordinary lvm [09:17] so I wonder if some bug conflation is going on [09:19] pitti, I'v open a bug for that #419093 === WelshDragon is now known as Richie [09:36] Hi, with latest pulseaudio in karmic, I have very low volume for songs etc. Is this expected? [09:38] slytherin: No, this is not expected. [09:39] Ok. I will log a bug when I go home. [09:41] slytherin: Is this on your ibook? [09:42] TheMuso: No. My PC. I never had to turn the speaker volume to full before (in jaunty). [09:43] slytherin: ok then, please file a bug when you get the chance. [09:44] I will tonight. [09:44] <\sh> I wonder how do I get sound from flashplayer on karmic 64bit again..the app doesn't show up in pulse mixer somehow...so I don't know where pulseaudio is routing the audio stream to [09:45] mumble, no glazor === mpt__ is now known as mpt [10:08] pitti: are you sure I need to gret for ^Size: and not for ^Installed-Size? [10:08] grep [10:09] TheMuso: not sure if you noticed, but python-louis is in universe [10:10] dholbach: an MIR has been written for it and it has been approved. [10:10] dholbach: I would not have done that otherwise. [10:10] ah ok [10:17] ArneGoetje: yes; we are interested in the compressed size (.debs) === dholbach_ is now known as dholbach [10:17] pitti: ok... [10:19] any way for ubuntu-bug to just create the report e.g"test.report" which then could be sent via ssh to other machine and reported that way? [10:19] taavikko: unfortunately not with ubuntu-bug; it's meant to be a parameter-less easy interface [10:20] taavikko: you can use apport-cli -f -p and save the report, see manpage [10:20] taavikko: or, if it's a crash (not a bug report), just don't send it and scp /var/crash/... file [10:21] thanks pitti :) seems ubuntu-bug works in xterm session so no nee [10:26] taavikko: yes, it uses apport-cli if there's no $DISPLAY [10:26] <\sh> if any archive admin of the day can look at bug #419099 that would be great...we would like to get this solved before FF [10:26] Launchpad bug 419099 in fai "Please remove fai source package and all resulting binary packages from karmic" [Undecided,New] https://launchpad.net/bugs/419099 [10:27] thanks for all the work on ubuntu-bug/apport it makes it so much easier to provide better info on bugs. [10:27] *beam* :) [10:27] * pitti does the finishing touches for intercepting assertion messages in apport [10:29] * directhex calls assert() in some platform code, to make pitti feel needed [10:29] directhex: Keybuk has plenty of them apparently :) [10:30] pulse is chock full of 'em [10:33] ArneGoetje: so, ibus ibus-gtk ibus-m17n pull in 3.5 MB [10:33] pitti: http://pastebin.ubuntu.com/259752/ [10:33] ah, that's probably imprecise since I have scim installed [10:33] which might share some tables [10:34] pitti: the numbers in that list are the grep'ed Size: field [10:34] ArneGoetje: ah, nice [10:34] pitti: what apt-get gives you is the Instaled-Size, AFAIK [10:34] ArneGoetje: that's not just scim->ibus, but also font changes? or are the fonts related to ibus? [10:34] pitti: no, font changes are extra [10:34] ArneGoetje: it gives you both ("Es müssen 3459kB an Archiven heruntergeladen werden." -> deb size) [10:34] ArneGoetje: ok [10:35] pitti: I might do some more font shuffeling, so this list is not final in that regard [10:35] ArneGoetje: thanks for the analysis [10:36] ArneGoetje: the seed changes are blocked by the im-switch update, right? [10:36] pitti: yeah [10:38] pitti: can we discuss the im-switch changes somewhere? [10:38] sure, /msg? [10:39] pitti: ok [10:51] glatzor, moo [10:53] ogra, servus! [10:53] ogra, the armel failure? [10:53] glatzor, you dropped my fix from packagekit :'( [10:53] yeah [10:54] hughsie always forgets to drop -Werror from his tarballs [10:54] ogra, in the 0.5 series it is optional [10:54] * ogra had that issue a thousand times with gnome-power-manager beforte [10:54] well, it makes armel ftbfs [10:55] ogra, I will rework the patch [10:55] thanks a lot [10:55] though it would be nice if he could disable it upstream before rolling a release [10:55] i know seb128 rants about that all the time too :) [10:55] ogra, it is also always a topic on the maling list :) [10:56] ogra: what's wrong with -Werror? [10:56] ogra: I'd rather get an armel build fix upstream than to kludge around with it? [10:56] pitti, armel (sparc and ppc too) often have simple warnings ... [10:57] pitti, seb always tells me its gnome policy that there is no -Werror in the released tarballs [10:57] why does armel have lots of simple warnings? [10:57] ogra: I don't know, if that's the policy he should stick to it of course [10:58] but still, I actually like programs which don't have warnings, too [10:58] liw, feel free to fix them ... if the app works fine but a build dies because of Werror i perfer to just drop the Werror according to the upstream policy [10:58] ogra, why do the warnings happen on armel but not on x86? [10:58] that should depend on the actual warning [10:59] right [10:59] we had warnings about pointer misalignments which were real bugs [10:59] (I'm not worried, merely mildly curious) [10:59] ^ me too [10:59] liw, because certain kinds of vars are handled differemntly for example [11:00] /usr/include/gstreamer-0.10/gst/gstmessage.h: In function 'gst_message_ref': [11:00] /usr/include/gstreamer-0.10/gst/gstmessage.h:302: error: cast increases required alignment of target type [11:00] thats the current warning that makes packagekit die for example [11:00] that sounds like a real bug to me :) [11:00] (but then I'm a C standards compliance purist) [11:01] the app functions as its supposed to [11:01] sounds like a potential bug, though [11:01] even on sparc ? [11:01] :) [11:01] it wouldn't be the first time that sparc crashes because of a misaligned variable [11:01] * liw wants to sell his hardcover paper copy of the 1999 C standard, thoug [11:01] cjwatson: should juli_ be able to upload stuff (libnb-javaparser-java) already? [11:02] yes [11:02] thanks cjwatson [11:02] lifeless, well, http://qa.ubuntuwire.com/ftbfs/ ... packagekit is dep wait on sparc :) [11:03] * ogra thinks if a warning should be a bug or error it should actually spit out an error and not a warning [11:04] we have tons of packages that build with warnings in the build logs [11:04] they simply dont have Werror set :) [11:04] pitti: but sadly my asserts don't make it into apport :-( [11:05] Keybuk: they should now :) [11:05] happyaron: I'm just looking at tor. Do you know if upstream are going to give you any help with supporting old releases? [11:05] (not uploaded yet, still finishing touches) [11:05] pitti: how? I don't use assert() :p [11:05] pitti: also the kernel doesn't wait for apport to complete before panicing yet [11:05] Keybuk: ah, I thought you did, since you pushed for it in https://blueprints.edge.launchpad.net/ubuntu/+spec/security-karmic-apport-abort [11:05] Keybuk: the latter point is what I asked about in the whiteboard, that point isn't clear to me [11:06] Laney: they seems won't, but I think if update the package in repository is acceptable for us, I can do it [11:06] you mean a new upstream version? [11:06] pitti: the __assert_msg stuff? If that works, I can certainly put the message in there :-) [11:06] Keybuk: right [11:07] Laney: I can catch up with the new releases in upstream repository, and re-pack the packages for ours [11:07] pitti: I saw that someone has proposed a patch to make the kernel wait for apport to finish before making the process a zombie as well [11:07] happyaron: The SRU policy doesn't usually allow for that though [11:08] Laney: yeah, this is the key problem now [11:08] Keybuk: I thought the whiteboard said something about apport needing to defer close()ing stdin until it's fully done or so? [11:09] Laney: I've mentioned in that bug, upstream can raise version number however they like to [11:10] Keybuk: actually, apport doesn't do any special magic to close stdin [11:10] it just reads until EOF [11:11] it's a bit of a difficult issue really [11:11] pitti: doesn't work, the kernel still panics too early [11:12] happyaron: I would appreciate it if you could talk to some members of the SRU team [11:12] if you can work out some arrangement with them then we should go ahead [11:12] Laney: where can I find them? [11:12] pitti: http://lkml.org/lkml/2009/6/22/368 [11:13] pitti: we need part of that patch set [11:13] happyaron: https://launchpad.net/~motu-sru/+members [11:14] Laney: how much time do we still have from now to DIF? [11:14] FF is what you care about, and it's tomorrow [11:15] I would rather get an exception than rush though [11:15] liw: Hey, I'm reading this discussion (bug #329060) about the automatic symlinking of identical changelog files. What does this (as I have it also in my pbuilder), dpkg-buildpackage, pkgbinarymangler? [11:15] Launchpad bug 329060 in lintian "Please disable "debian-changelog-file-is-a-symlink" warning" [Undecided,Confirmed] https://launchpad.net/bugs/329060 [11:16] cody-somerville: hi [11:17] happyaron, hello [11:17] didrocks, I don't know what does the symlinking of identical changelogs [11:17] cody-somerville: I would like to ask you about some SRU issue about tor [11:17] happyaron, Okay. [11:18] liw: ok, and there is nothing written in wiki.ubuntu.com? In any case, I think i'll try to patch at least lintian [11:18] didrocks: cdbs [11:18] didrocks, patching lintian (in Ubuntu) to not warn about that would be good, yes [11:19] cody-somerville: as I want tor could reintroduce to ubuntu, we need to update it whenever upstream update the package, or upstream will be unhappy to the packages they don't support [11:19] the warning is still correct for Debian though, so that isn't upstreamable [11:19] cjwatson: I'm using debhelper 7 in the present case, so where is the common denominator? :) [11:19] if you're using debhelper 7 I'm not sure I believe you that automatic symlinking is happening :) [11:20] to the best of my knowledge dh7 doesn't do that [11:20] cody-somerville: I mean we need to keep the package up-to-date rather than keep it a specific version in our repository as other packages [11:20] try DH_VERBOSE=1 to see what's going on? [11:20] cjwatson: It's just appear on a package which uses dh7 (and I didn't notice it before) [11:20] maybe the package is doing it for itself? [11:20] cjwatson: yeah, I'm testing that now :) [11:20] as in, hand-coded stuff in debian/rules [11:20] cjwatson, didrocks: it's done by /usr/share/cdbs/1/rules/debhelper.mk [11:20] cjwatson: not from what I see [11:21] pitti: right, that's why I said "cdbs", but it's not a native debhelper thing [11:21] happyaron, Is there a particular reason why? [11:21] so all cdbs packages which include that (IOW, pretty much _all_ cdbs packages) get it [11:21] cjwatson: right, just to confirm you, it's not done in dh proper [11:22] pitti: cjwatson : ok, i didn't see but the package is using dh 7 commands, but it includes debhelper.mk. So, here is the explanation :/ [11:22] * didrocks will fix this [11:23] thanks ;) [11:23] cody-somerville: we have tor in our repository before, but once upstream filed a bug to request a deletion of it because they don't want us ship the old version of their software that they don't support any more, and if we want to reintroduce it, we need to keep it up-to-date or upstream may file another bug to do it again [11:24] happyaron, What sort of changes are made between versions? How often do they release? [11:25] didrocks: what package in particular, BTW? [11:25] didrocks: (please note that if you drop cdbs for packages which have translations, you also need to do a lot of other stuff manually, like createing POT files, adding gettext domains to desktop files, and the like) [11:26] pitti: it's upstream cairo doc package (not yet in ubuntu). They want to replace the current ubuntu package but I have to fix a lot of issues first. [11:27] didrocks: ok, doesn't sound like something that would be on the CDs then [11:27] cody-somerville: mostly security updates, and they update it not very frequently but not very regular, either [11:27] pitti: ok, so maybe, it's better to remove the debhelper 7 overrides call and change them in cdbs equivalent? [11:27] didrocks: your choice [11:27] pitti: yes, little chance it hits the CD ;) [11:28] happyaron, ever any non-security updates? ie. new features [11:28] cody-somerville: we can jump over several releases, just keep the package's version is still supported by upstream is bearable [11:28] cody-somerville: that will take nearly one year for a new one, and the old one will be dropped to unsupported [11:32] meep...i'm someone who "steals" a lot of ubuntu packages and stuff for fink/macos x [11:32] just packaging indicator-applet...i wonder what else i need to make that worthwhile ;) [11:33] libdbusmenu is done already, too [11:33] jack: I think it's best to talk to tedg or kenvandine in #ubuntu-desktop, but both of them are in USish timezone and still asleep [11:33] :) [11:34] no suggestions? any fancy apps that use libindicate or libdbusmenu? [11:34] jack: indicator-applet itself is just the base functionality, you need "plugins" to do useful stuff with it; like indicator-evolution, the pidgin plugin, or indicator-session [11:34] look at the reverse dependencies? [11:34] the ubuntu pdb unfortunately doesn't let me walk dep chains [11:34] indicator-messages, too [11:34] ojwb: sure, just what i was thinking :) [11:35] jack: ah, no ubuntu install i guess? [11:35] pitti: ok cool, will try the pidgin stuff next [11:35] ojwb: i'm still running kubuntu-feisty on my old craptop [11:35] the rest are all macs [11:35] happyaron: How does Debian get away with it? The version in Lenny hasn't been updated [11:36] Laney: they have a so-called trust chain, and the maintainer of tor in Debian is who work for upstream deb repository [11:36] does that get around the security holes? [11:36] jack: a chroot would work. on the kubuntu side konversation has support and I should upload kmail and kopete today with it [11:37] Riddell: work for what? feisty! [11:37] that's almost previous-millenium-ubuntu [11:37] a karmic chroot would work for feisty yes [11:37] jack: oh and libindicate-qt of course [11:37] but i don't have a box that would be good enough for karmic ;) [11:38] jack: so make a chroot so you can find the rdepends and do apt-cache search and whatnot [11:38] but i can't install current ubuntu pkgs without a working karmic ;) [11:39] i just harvest from packages.ubuntu.com, mainly [11:39] james_w: around ? [11:39] without ever having seen the stuff running on a current ubuntu box [11:39] hi ttx [11:39] james_w: hey :) [11:39] james_w: about the repacking notes for jetty6 [11:40] james_w: it's the orig.tar.gz from debian experimental. There is a README.source that documents it. Do you want me to +dfsg it ? [11:42] james_w: also do you know how repacking should be stated in the new debian/copyright format ? [11:42] Laney: they update it in unstable as far as I know, I didn't do research on how they solve it for stables [11:45] james_w: note sure adding non-URI stuff to the Source: line is ok. Maybe I can use Disclaimer: [11:45] ttx: I'm not sure I'm afraid [11:46] ttx: I wouldn't consider it a blocker seeing as it is already in [11:47] happyaron: That's the main issue though isn't it? [11:47] james_w: well, kees sees it as a MIR blocker. Maybe you can chime in on bug 418836 [11:47] Launchpad bug 418836 in jetty6 "MIR jetty6" [Undecided,Incomplete] https://launchpad.net/bugs/418836 [11:47] Laney: okay, I will do it right now [11:47] ie why is it OK for Debian to ship old releases but not Ubuntu [11:48] ttx: yeah, I'd use disclaimer [11:49] Laney: they update it to the version upstream support, 0.2.0.34 in lenny and etch-backports [11:49] Laney: upstream requested a deletion for our 0.1.x version's packages [11:50] so that changes things a bit [11:50] ie we don't need to update to the current release all the time [11:51] Laney: yes, I agree, keep it the version upstream support is ok, only when it's not supported any more we need to update it [11:51] right [11:51] cody-somerville: ^^^ [11:53] Are they fine with the updates going into -backports instead of -updates? [11:56] cody-somerville: for older releases is ok, but how to do it for current release if update is needed? [11:56] happyaron, You simply need to request a backport. [11:56] happyaron, If the new version is only security fixes, a security upload can also be done. [11:58] cody-somerville: but if there is a new release with new features, I think this is the most difficult thing to concern? [11:58] happyaron, If there is new features, the updated version could go into backports. [11:59] cody-somerville: I have said it's okay for older releases, but what about current release, just like Jaunty, there is no backports before Karmic is out [12:00] happyaron, AFAIK, there is. [12:01] happyaron, I just looked and there is definitely packaged in jaunty-backports [12:01] cody-somerville: oh, that's good, what I need to do is request for security updates/backports, right? [12:02] happyaron, https://help.ubuntu.com/community/UbuntuBackports#How%20to%20request%20new%20packages <-- backports process [12:02] cody-somerville: that's good [12:03] Laney: ~ [12:03] happyaron, https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures <-- Security updates process [12:03] depends if you consider backports to be first-class [12:04] Laney: I don't think so in fact [12:04] they aren't enabled by default for example [12:05] Laney: security updates can solve part of the problem, but -updates will be better than -backports I think [12:05] cody-somerville: if a new releases with features updated, how can it added to -updates? [12:05] When upstream decide to stop supporting a series, it's likely that the new one introduces new features right? [12:05] but also has security fixes and so on [12:06] happyaron, It won't, it'll go into -backports [12:06] Laney: yes, new feature and unsolved bugs [12:07] Laney: oh, I mean the old one has unsolved bugs, a typo [12:07] well the original problem is that upstream don't want us to ship their unsupported releases right? [12:08] yes [12:08] So is an update in -backports good enough for them? [12:09] Laney: debian just backport it, if we can include it to -updates, things will be better [12:10] Laney: and debian deleted the package from etch but include it again in backports, that means users can only get in in backports [12:12] pitti: Hi [12:19] hi tkamppeter [12:20] pitti, we have talked about a CUPS SRU for Hardy in DFublin, do you remember which problem we talked about? [12:20] tkamppeter: no, I'm afraid not [12:24] I have found two SRU candidates: bug 372118 and bug 307471, but what we talked about in Dublin was something else. [12:24] Launchpad bug 372118 in cups "CUPS does not work with Firefox, HTTPS bug (Hardy LTS)" [Undecided,Fix released] https://launchpad.net/bugs/372118 [12:24] Launchpad bug 307471 in cupsys "Multi bin printing broken in OpenOffice.org due to cupsys pstops filter bug" [Undecided,Fix released] https://launchpad.net/bugs/307471 [12:24] pitti: ^^ [12:24] two weeks of holiday don't help for remembering.. [12:25] anyway, lunch time, bbl [12:26] Laney: what to do next? === MacSlow is now known as MacSlow|lunch [12:53] happyaron: I don't know :( [12:56] Any thoughts? https://bugs.launchpad.net/bugs/419126 [12:56] Launchpad bug 419126 in gdm "gdm loops after logging in" [Undecided,New] [13:10] cody-somerville: What has xubuntu done regarding theming the new gdm for karmic? [13:10] TheMuso, I'm going to upload gdm-2.20 today [13:11] cody-somerville: Oh so the older GDM? Ok. [13:11] TheMuso, right [13:12] Fair enough, I can understand why you want to stick with that. [13:23] hrm, who made my laptop so unstable [13:23] o/ [13:23] * ogra just upgraded and experiences hangs [13:25] is pidgin 2.6 going to make it into karmic? [13:25] if not today, never =( [13:25] hyperair: why never? [13:25] er unless you count backports [13:25] up to the MOTU i'd guess [13:26] Afaik pidgin is still main. [13:26] yeah pidgin's still in main [13:26] given the default gets switched to telepathy anyway i would guess it goes to universe [13:26] no, there are a fair few things in main that aren't default [13:26] e.g. irssi [13:26] right [13:26] there's a diff up for sponsoring [13:26] because main devs take care for irssi [13:26] quickly sponsor it then! =O [13:27] if nobody does that for pidgin it will go to universe [13:27] telepathy depends on libpurple (pidgin) [13:27] so that lib would sty in main [13:27] *stay [13:27] can you have source in universe and binary in main? [13:28] No [13:28] thought not [13:28] You can have the other way around however. [13:28] yes [13:28] you can? [13:28] how does that work? [13:29] ah, i didnt know libpurple has no own source [13:29] isn't pool/ sorted by component/source/? [13:30] Binaries can be built from source packages in main and they go to universe due to not being needed/depended on by anything in main eg seeds etc. [13:30] right [13:30] TheMuso, while i have you here, any idea about the FTBFS of pulse on armel ? [13:30] hmm i thought you could only copy source packages, not binaries without sources [13:31] * ogra doesnt really get why pulse needs CPU assembler for volume control [13:31] heh assembler? seriously? [13:31] ogra: Nor do I, but there are CPU optimizations for arm, SSE, and mmx. I have pinged the guy who wrote the arm code about the error. [13:31] ogra: It was not Lennart who wrote it. [13:31] ah, k, but it was forwarded, thats good [13:31] The SSE/MMX code is in x86 assembler as well. [13:31] TheMuso, thanks for that [13:32] ogra: np. [13:32] No response so far. [13:32] well, i didnt know there is specific arm code, probably we just need to make sure it gets actually used, i'll take a look later [13:32] ok thanks [13:33] hyperair: Tomorrow is FF, If someone prepares detailed report for FFE for pidgin and FFE is approved it can still go on. [13:33] might be it doesnt know its actually on arm [13:33]