[00:01] <SpamapS> jdstrand: still here?
[01:05] <broder> infinity: i looked into multiarching libpcsclite1, fwiw. i don't remember whether or not i concluded that its communication with pcscd was arch-independent, but i think i decided it wasn't
[01:05] <broder> (re vmware view client)
[01:08] <infinity> broder: Ahh, that would prove problematic.
[01:09] <infinity> broder: Perhaps a followup to that bug indicating such, so we don't just look "lazy" for not getting around to it? ;)
[01:09] <broder> sure
[01:09] <infinity> broder: Danke.
[03:31] <broder> infinity: oh, crap. i didn't notice you were still logged into odo, but i just kicked off a full lintian rescan for the new upstream release, which wipes out the old lab
[03:31] <broder> it, uh, should be back in about 24-48 hours or so
[03:32] <broder> i bet with more thinking, i could have done that without actually destroying the laboratory. maybe next time
[03:43] <ScottK> broder: Is something like "what packages have the file debian/pyversions and mention version 3 or higher?" something you can grep for reasonably easily?
[03:45] <infinity> broder: Oh, no big deal.  I was logged in, but idling.  I'm sure I have what I need in my ~
[03:45] <infinity> ScottK: That would be trivial had he not just wiped out the lab, yeah. :)
[03:48] <ScottK> broder: I'd appreciate it if you could generate such a list once the lab is back.  I need to remove some backwards compatibitly support code from dh_python3 before it gets to be "It's always been that way" and I suspect a MBF of some degree will be needed.
[03:48] <ScottK> debian/pyversions should never be used for python3.
[03:49] <ScottK> And XS-Python-Version: with Python 3 versions in debian control too.
[03:49] <ScottK> Soooooo much brain damage already for something so new.
[06:36] <pitti> Good morning
[06:48] <broder> ScottK: yeah, that should be easy once the lab is reassembled
[06:51] <broder> ScottK: i'd strongly encourage you to ping me about it in, say, 3-4 days because i will likely forget
[07:26] <rickspencer3> hey pitti, almost another beer this morning! silly armhf archive :)
[07:26] <pitti> well, calligra failed to build on armhf
[07:26] <pitti> and libreoffice currently doesn't build these three binaries on arm, Sweetshark was looking into bringing them back
[07:26] <rickspencer3> pitti, yeah, like I say "silly armhf" ;)
[07:27] <rickspencer3> tbh, I am pretty happy with the state of armhf all things considered
[07:32] <pitti> yeah, it doesn't actually break LibO, and the calligra FTBFS is just brand new
[07:33] <pitti> rickspencer3: we got a new release-upgrader-apt into lucid-proposed yesterday; I'm yearning to see today's auto dist-upgrade results :)
[07:33] <rickspencer3> pitti,  oh boy
[07:34] <rickspencer3> pitti, so, time to get Lucid ready for upgrades to Precise? I guess mvo has been busy?
[07:34] <pitti> lots of red on https://jenkins.qa.ubuntu.com/view/Precise/ :/
[07:34] <pitti> bootspeed and the new openstack tests mostly
[07:34] <rickspencer3> pitti, yeah, the upgrade testing has been bumming me out, but slangasek assured me that the blockers were being worked on
[07:34]  * pitti leaves those in the good hands of Daviey/jibel and goes back to untangling pygobject marshalling code
[07:35] <rickspencer3> pitti, I think the boot speed regressions were addressed by the apparmour engineers yesterday
[07:35] <rickspencer3> "pygobject marshalling code"
[07:35] <pitti> rickspencer3: yes, I reviewed all failues last week, and most of them came down to two apt bugs
[07:35] <rickspencer3> that does not sound found
[07:35] <pitti> rickspencer3: no, the boot speed tests fail apparenlty
[07:35] <rickspencer3> pitti, oh, I see, that's new then
[07:36] <pitti> some SMTP exception in the tests
[07:36] <pitti> Sending e-mails to: qa-team@lists.canonical.com
[07:36] <pitti> ERROR: Invalid Addresses
[07:36] <rickspencer3> pitti, I think your idea of unitverse upgrade testing was as stroke of genius (naturally)
[07:36] <pitti> rickspencer3: well, it certainly helped to uncover a lot of failure cases
[07:37] <pitti> rickspencer3: upgrade-lucid-universe is a real masterpiece to get right, of course; once that works, everything else is child's play :)
[07:37] <rickspencer3> let's do it!
[07:37] <rickspencer3> (easy for me to say ;) )
[07:37] <rickspencer3> pitti, but indeed, systematically ensuring those tests before the Precise end game ...
[07:38] <rickspencer3> this should contribute to a nice smooth release on April 26th
[07:43] <jibel> pitti, bootspeed test failure is caused by a network error. I'll ask Larry to look into this this afternoon, when he wakes up.
[07:44] <pitti> merci jibel
[07:44] <jibel> openstack, the address of the repository https://github.com/openstack/nova.git is wrong
[07:44] <jibel> jamespage, ^
[07:46] <pitti> it's https://github.com/openstack/nova/
[07:47] <pitti> oh, actually.. that page itself says https://github.com/openstack/nova.git
[07:47] <pitti> and that actually does work
[07:47] <pitti> $ git clone https://github.com/openstack/nova.git
[07:47] <pitti> git clone https://github.com/openstack/nova works as well, though
[07:49] <jibel> well, the error from the job is "ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job."
[07:58] <dholbach> good morning
[07:58] <ajmitch> morning dholbach
[07:59] <dholbach> hi ajmitch
[08:00] <geser> Hi dholbach and ajmitch
[08:00] <dholbach> hey geser
[08:00] <ajmitch> hi geser :)
[08:48] <jibel_> slangasek, main-all lucid amd64 didn't finish and I can't log in. it could be caused by the corruption you saw yesterday. I'll rebuilt the base image.
[09:04] <pitti> stgraber: so bug 939450 was a nice puzzle, I couldn't resist hacking on it after all :) it's working well here now
[09:12] <ScottK> broder: Thanks.
[09:40] <dpm> hi all, I've got a quick question on a particular package and I was wondering if someone could give me a hand
[09:40] <dpm> I'm working with translation templates in LP
[09:40] <dpm> and I need to know which source packages are in universe (so that they are disabled in LP) and which ones in main
[09:40] <dpm> I'm looking at this one: http://pastebin.ubuntu.com/884504/
[09:40] <dpm> the question is, why is there output for a universe line and a main line?
[09:40] <dpm> any ideas?
[09:43] <tumbleweed> dpm: source in main, binaries in universe
[09:44] <dpm> tumbleweed, does this mean it needs fixing? I.e. everything needs to be in main?
[09:46] <tumbleweed> dpm: that's not my area of expertise :) Not sure why that package is like that
[09:46] <dpm> tumbleweed, no worries, thanks :)
[09:47] <seb128> nijaba, hey
[10:50] <geser> dpm: no, there are valid use-cases where the source is in main but the binary packages in main and universe (e.g. a library in main while its utils in universe)
[10:54] <geser> dpm: in your example, the -common and the -control-center package is in main while activity-log-manager is in universe (perhaps didrocks can tell you the rationale for it)
[10:54] <dpm> ok, thanks a lot geser!
[10:55] <didrocks> geser: activity-log-manager is a standalone application
[10:56] <didrocks> geser: we don't really need, we only want the control panel plugin
[10:56]  * didrocks logout/login bbiab
[10:58] <geser> dpm: ^^ a reason for such a main/universe split
[11:21] <jmelis> Hi guys, I've sent an email requesting for help to maintain and perform a sync request of the opennebula (opennebula.org) package. I've sent it to the ubuntu-devel mailing list, but it's moderated. Should I send it elsewhere?
[11:23] <dholbach> jmelis, https://wiki.ubuntu.com/SyncRequestProcess#For_people_requiring_sponsorship explains how to do it, so it shows up in the review queue
[11:23] <dholbach> jmelis, and thanks for your offer of help!
[11:24] <jmelis> thanks dholbach! although what offer of help??
[11:25] <jmelis> me being involved in the maintaining process?
[11:25] <dholbach> you said you'd want to help maintain the package, no? :)
[11:25] <jmelis> yes :)
[11:25] <dholbach> well that's excellent :)
[11:26] <jmelis> dholbach: when I send the sync request, should the package be ready to work in UBuntu, or is it understood that there's still work to do?
[11:27] <jmelis> Damien Raude-Morvan (package maintainer) and I have built the debian package and we would like to sync that package so the development of the package is centralized...
[11:27] <dholbach> yes, it should work in Ubuntu
[11:27] <dholbach> I had a quick look and there seem to be modifications of the package in Ubuntu
[11:27] <dholbach> can they be dropped?
[11:27] <jmelis> what for instance?
[11:28] <dholbach> ah no, it was a change which was reverted again
[11:28] <dholbach> nevermind
[11:28] <jmelis> how can I check if my package is ready for a sync request?
[11:29] <dholbach> it seems to be a major version update, so adding some information as outlined in https://wiki.ubuntu.com/FreezeExceptionProcess will be useful
[11:30] <dholbach> it'd be good to see if it builds without problems and make sure it works as well - we're just between beta1 and beta2 of the release, so we're cautious about huge changes which go in now
[11:34] <jmelis> dholbach: so just to confirm what I need to do is 1) try building the package in ubuntu 2) fix compilation errors 3) submit a sync request following the guides you sent me
[11:34] <dholbach> yes
[11:34] <jmelis> and, where can I find help for 1 and 2?
[11:35] <jmelis> I don't mean to delegate all the work, but there are certain technical things that I don't have much experience with, for instance, using packages with different names in debian and ubuntu, etc...
[11:36] <jmelis> And some help would come in really handy
[11:37] <dholbach> for 1) and 2), I'd do something along these lines:       sudo apt-get install ubuntu-dev-tools; dget -u http://ftp.de.debian.org/debian/pool/main/o/opennebula/opennebula_3.2.1-1.dsc; pbuilder-dist precise create; pbuilder-dist create build opennebula_3.2.1-1.dsc
[11:37] <dholbach> this will set up a precise build chroot and run a build for you on the current debian package
[11:38] <dholbach> our general Ubuntu development guide is up at http://developer.ubuntu.com/packaging/html/
[11:38] <dholbach> but do feel free to ask more questions in here
[11:38] <jmelis> what if in the control file, the name of the package opennebula depends in have a different name under debian and ubuntu?
[11:39] <jmelis> the name of the *packages*
[11:39] <Riddell> micahg: and special magic needed by xubuntu or other flavours your involved in to the lightdm auto login working?
[11:39] <dholbach> jmelis, you could just test-install it in a chroot (if you don't run Ubuntu precise) to see if it installs and works
[11:40] <jmelis> ok, I will
[11:40] <dholbach> super
[11:41] <jmelis> one more question, since you're in between beta1 and beta2, how much time do I have before I loose a reasonable chance to get opennebula's package sync'd?
[11:42] <dholbach> it will be quite hard as it is, after Feature Freeze (https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule) we try very hard to just focus on bug fixing updates
[11:42] <dholbach> the page about the Freeze Exceptions I mentioned above should have some more details
[11:45] <jmelis> ok, I'll give it a shot asap. Is there any way to update the package once precise has been released? for instance, syncing for 12.10 and backporting? or once precise is release there's no way it can be updated?
[11:45] <dholbach> https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport will be your friend after the release :)
[11:46] <dholbach> so yeah, there will be "precise-backports" where updates can go afterwards
[11:46] <jmelis> thanks a bunch dholbach!
[11:46] <dholbach> de nada
[11:46] <jmelis> haha
[12:07] <cjwatson> dpm: FWIW you might have found 'rmadison -S activity-log-manager' a bit more informative
[12:08] <nerochiaro> hey folks, i'm on beta1 of precise and just apt-get upgraded,rebooted and now my keyboard stops working every few seconds for a second or so. is this some known issue ?
[12:12] <dpm> cjwatson, ah, cool, thanks for the tip
[12:17] <nerochiaro> i also notice i have a process watchdog/0 that every few seconds gets 60% of CPU
[12:47] <cjwatson> ah, oops, 'bzr merge lp:debian/debconf' would work better if my current directory were the Ubuntu debconf branch not the Debian one
[12:53] <stgraber> pitti: cool :)
[13:05] <ogra_> @pilot in
[13:09]  * dholbach hugs ogra_
[13:09] <ogra_> :)
[13:11] <dholbach> dendrobates, happy birthday! :)
[13:11] <dendrobates> dholbach: thanks
[13:40] <addy335> hello tell me procedure for install any software which i have in pendrive
[13:41] <addy335> please any body tell me procedure of install software offline/not connected to internet
[13:42] <directhex> ...?
[14:12] <scott-work> ubuntu studio is experiencing uninstallable images while trying to use the -lowlatency kernel as default, bug #955617
[14:12] <scott-work> luke commented in IRC yesterday, "livecd-rootfs package needs updating to use the lowlatency kernel for studio"
[14:25] <pitti> uh, do we really keep this?
[14:26] <ogra_> yes
[14:26] <pitti> is it now being maintained by the kernel team?
[14:26] <ogra_> unlike the name suggests it has all ubuntu specifics for live-build in it
[14:26] <ogra_> oh, you referred to lowlatency
[14:26] <ogra_> not to livecd-rootfs
[14:26] <ogra_> ignore me :)
[14:27] <ogra_> but yeah, i think there was a discussion about the ll kernel at UDS, as long as it stays in universe and has active maintenance its fine iirc
[14:28] <mhall119> cjwatson: ping
[14:45] <scott-work> pitti: if you are referring to the lowlatency kernel, there are a few points i would make:
[14:46] <scott-work> 1. the lowlatency kernel can at a minimum halve the latencies experienced (even on moderate hardware) for audi work.  in some cases, this is the inflection point for whether a system is usable or not
[14:46] <scott-work> 2. the kernel will be maintained by community (i.e. ubuntustudio-dev team members)
[14:46] <scott-work> 3. has been discussed quite a bit with UKT and has their blessings
[14:47] <cjwatson> mhall119: hi
[14:47] <scott-work> 4. is based on the ubuntu kernel without any invasive patches (i.e. the -rt patch)
[14:49] <mhall119> cjwatson: hi, I have a couple of FFes I'd like someone to take a look at, I posted them in #ubuntu-release
[14:50] <pitti> scott-work: it hadn't been update for quite some time, and keeping up with post-release updates won't be trivial
[14:50] <cjwatson> mhall119: I don't do very much FFe work ...
[14:52] <apw> cjwatson, so when one installs from an alternate image, is it reasonable to describe the process, using the CD as a pool to do a dbootstrap into the new disk ?
[14:52] <apw> cjwatson, and the kernel which is in the image would be installed in the normal manner, dpkg -i *.deb
[14:52] <apw> s/image/in the resulting install/
[14:54] <cjwatson> apw: debootstrap is only one part of the process
[14:55] <cjwatson> http://d-i.alioth.debian.org/doc/internals/ has some more information
[14:55] <apw> cjwatson, thanks will read ...
[14:55] <cjwatson> apw: this sounds like a second-order question.  what's the primary thing you're trying to discover? :)
[14:56] <apw> cjwatson, indeed, i am trying to work out why a module i expected to be in an image is not (i think they are saying) in the kernel as installed by the installer, but i am out of touch at the moment to get clarity on the failure
[14:56] <cjwatson> apw: can I see the original report, and then I can probably walk through it with you?
[14:57] <apw> cjwatson, oh right now i literally have 'my storage module is missing in the install' and nothing more
[14:57] <cjwatson> it is much more likely that they are talking about during installation, not after installation
[14:57] <cjwatson> in which case looking at debootstrap etc. is looking at the wrong end
[14:58] <apw> cjwatson, which actually could mean "the d-i CD boot kernel is missing X" or "the installed kernel is missing X" ... will have to wait on them getting back to me
[14:58] <cjwatson> it should be pretty clear if you look at the udebs that your kernel packaging emits
[14:58] <apw> cjwatson, well i mostly wanted to know if the kernel in the final install is really just a dpkg -i job, if so i know that is right as i can test that
[14:58] <cjwatson> debian.master/d-i/ et al
[14:58] <cjwatson> it is
[14:58] <cjwatson> nothing much fancy there
[14:58] <apw> yeah that was my expectation, so he must mean the former, which means i can check the d-i bits in preparation
[14:58] <apw> thanks :)
[15:04] <scott-work> pitti: currently, TheMuso is helping with updating the lowlatency kernel and there is a plan to document the kernel rebasing per security updates in the blueprint - https://blueprints.launchpad.net/ubuntu/+spec/other-p-lowlatency
[15:04] <scott-work> pitti: ideally we would like to have three members of the team who _can_ do the updates, but most likely two who are primarily responsible
[15:14] <robbiew> slangasek: bug 935585 is causing some pain for us regarding openstack on precise, any chance the version of upstart in https://launchpad.net/~jamesodhunt/+archive/bug-935585/ gets in?
[15:14] <cjohnston> m_3: ping
[15:14] <cjohnston> jcastro: I'll poke you as well...
[15:18] <robbiew> cjwatson: ^^^...do you know the status of bug 935585?
[15:19] <micahg> Riddell: not that I'm aware of
[15:21] <cjwatson> robbiew: best to ask jodh directly; it's not come up in team meetings or discussions I've had with him
[15:22] <cjwatson> robbiew: we'd be more comfortable if we could figure out how to test for it, I expect
[15:22] <robbiew> cjwatson: ack...jodh? how many irc nicks does he have? lol
[15:22] <cjwatson> just one new one :)
[15:23] <jodh> robbiew: I'm just finishing some tests for the next release so a new version including a fix should be available tomorrow/Monday.
[15:23] <robbiew> jodh: perfect...thanks!
[15:23] <jodh> robbiew: there is the ppa build version that includes the fix too of course: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/935585/comments/11
[15:24] <robbiew> yep and folks on the openstack list have used it ;)
[15:32] <m_3> cjohnston: pong
[15:32] <cjohnston> jcastro: ^
[15:33] <cjohnston> mornin m_3
[15:33] <jcastro> let's have this conversation on #ubuntu-community-team
[15:34] <slangasek> jibel_: so precise-upgrade-lucid-main/amd64 never returned a result yesterday :(  any idea why?
[15:39] <ogra_> psusi, after i merged your dmraid fix i was wondering why you are still no uploader ... i mean you are active in this channel since years and definitely have submitted tons of patches in that time :)
[15:40] <psusi> ogra_: hrm... well I suppose getting a PPU would be my next step...
[15:40] <ogra_> about time :)
[15:43] <blackbug> I have some fixes for a bug, but gnome-screenshot doesn't have a bazaar branch. How should i upload my changes on launchpad?
[15:48] <ogra_> blackbug, just add a diff to the bug (and feel free to point me to it)
[16:04] <micahg> Riddell: I might have misunderstood your question, Xubuntu and other derivatives use a postinst to set certain lightdm defaults
[16:07] <MacSlow> mvo, poing
[16:07] <Riddell> micahg: right that's what I wanted to know
[16:08] <Riddell> micahg: where is that?
[16:08] <micahg> Riddell: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/xubuntu-default-settings/precise/view/head:/debian/xubuntu-default-settings.postinst
[16:09] <Riddell> micahg: mmm
[16:20] <slangasek> brendand: so do I understand from your response to bug #834731 that no one took an image of the disk before wiping? :/
[16:21] <brendand> slangasek, probably not
[16:22] <brendand> slangasek, we did it to get the system working and 834731 wasn't in my mind at the time
[16:22] <slangasek> ok
[16:23] <slangasek> I'll leave it open-incomplete for now in case someone else runs into the same problem
[16:23] <brendand> slangasek, i'll check with the lab tech on the off-chance they did, but i'm not hopeful...
[16:28] <ogra_> psusi, heh, and if your changelog entry would actually have pointed tzo precise it wouldnt have been rejected :P (i fixed that though)
[16:29] <debfx> micahg: that seems like a bad idea. what happens if you have multiple *-default-settings packages installed that also change the lightdm config?
[16:30] <micahg> debfx: well, there is an alternatives system for the config, I haven't tried multiple ones personally
[16:33] <debfx> micahg: it doesn't use the alternatives system to set the default session and greeter. so it looks like it would be race on which -default-settings package was configured/upgraded last.
[16:34] <micahg> debfx: yep, I wanted a debconf prompt like *dm packages had, but it wasn't implemented that way
[16:34] <mvo> MacSlow: hello
[16:37] <debfx> micahg: it seems like a perfect use case for the alternatives system to me but I have no idea if that can be integrated with the lightdm config.
[16:39] <micahg> debfx: normally the alternatives system is a mess, but in concert with a debconf prompt, it was quite usable, I think it's too late to rework this for 12.04 though, maybe for 12.10 speak with robert_ancell about it
[16:39] <cjwatson> scott-work_: do you want linux-lowlatency or linux-lowlatency-pae by default?
[16:40] <cjwatson> scott-work_: hm, and are you sure that's related to bug 955617?  the only connection I see is that you were talking about both at around the same time on IRC :-)
[16:41]  * cjwatson will look into that one anyway ...
[16:55] <jibel> slangasek, I don't know, I can't even log in to investigate. I restarted it again with a fresh base image.
[16:55] <slangasek> jibel: heh, ok
[17:02] <ogra_> @pilot out
[17:06] <jibel> mvo, bug 946113 any idea what it is, never seen this before ?
[17:07] <mvo> jibel: I have not seen this one yet
[17:17] <mterry> @pilot in
[17:29] <seb128> mterry, hey
[17:29] <mterry> seb128, hello
[17:29] <seb128> mterry, happy piloting
[17:30] <mterry> seb128, :)  gets hard so late in the cycle, have to find things worth piloting
[17:30] <seb128> mterry, if you upload some of the unity list items waiting on the queue (would be nice) please note them in the desktop etherpad
[17:30] <seb128> mterry, we will batch an email to translator about those
[17:30] <seb128> mterry, likely tomorrow
[17:30] <seb128> mterry, we took notes there on what items got added
[17:30] <seb128> mterry, I saw there was still rb, brasero, and some others on the list
[17:31] <mterry> seb128, ah...  I thought people were holding off on the quicklist stuff?  if not, I can chew through some of those
[17:31] <seb128> mterry, no, they should go in, dunno why all other pilots ignored them, they are easy
[17:32] <seb128> mterry, what ql stuff? the new spec support landed in indicator, unity and desktop-file-utils, we have a bunch using the new format in precise
[17:32] <seb128> mterry, well anyway feel free to sponsor those and to note the ones you sponsor on the etherpad so we notify translators tomorrow with a list ;-)
[17:32] <mterry> seb128, k
[17:33] <mterry> seb128, ah, new spec.  I have to change Deja Dup to use it...
[17:33] <seb128> mterry, we still support both, but would be nice
[17:33] <mterry> yar as an upstream I mean, for other shells
[17:33] <seb128> mterry, you can drop your X-GNOME-Keywords while you are at it btw, I think deja is in the last 3 to still list those ;-)
[17:34] <mterry> seb128, I have both Keywords and X-GNOME-Keywords.  I still want trunk to work on 11.10
[17:34] <seb128> mterry, wfm
[18:02] <scott-work_> cjwatson:  you are correct about the bug/kernel lacking correlation.  i had misunderstood micahg about updating the meta files.
[18:02] <cjwatson> I've split it out to a separate bug
[18:03] <scott-work_> cjwatson:   i understand what a pae compiled kernel is intended to achieve, but i wonder if there are reasons not to choose it in this case
[18:03] <scott-work_> cjwatson:  my first thought is too keep it as simple as possible and choose linux-lowlatency
[18:04] <cjwatson> it's your call, I don't really want to be involved beyond applying it :)
[18:04] <cjwatson> (you plural I guess)
[18:04] <scott-work_> i understand, how soon do you require a definitive answer?
[18:05] <cjwatson> before beta 2 freeze, so <1 week
[18:07] <scott-work_> cjwatson: let's not muddle this more than absolutely required, please use linux-lowlatency
[18:07] <scott-work_> and thank you again for all your attention and work
[18:08] <cjwatson> 'k
[18:14] <scott-work> cjwatson:  after some other discussion, i would like to reverse my decision and use the linux-lowlatency-pae by default
[18:16] <cjwatson> scott-work: heh, ok, can you log that discussion in bug 956250 and reopen it, please?
[18:16] <scott-work> indeed i shall
[18:19] <scott-work> cjwatson: unfortunately, i cannot change the status of that bug, although i did add the conservation to the report
[18:21] <scott-work> astraljava:  don't forget about the ubiquity background/text bug too, if you can.  i would really like to get that one resolved before B2 if possible
[18:21] <scott-work> err, wrong channel
[18:21] <Riddell> sladen: does the ubuntu font have the new turkish lira symbol?
[18:22] <Riddell> sladen: http://en.wikipedia.org/wiki/Turkish_lira#Currency_sign
[18:22] <micahg> cjwatson: scott-work: bug reopened
[18:23] <scott-work> thank you
[18:38] <cjwatson> scott-work: right, done then
[18:43] <psusi> slangasek: if I understand your patch for the udev/lvm issue correctly, you have udev check to see if there are any pending events that involve the cookie, and delay exiting untill they have been processed ( thus unlocking the semaphore )
[18:43] <psusi> slangasek: isn't the problem more broad than just cookie events though?  shouldn't udev not be dropping ANY events?
[18:44] <psusi> slangasek: i.e. when told to exit, it should stop reading from the netlink socket, but complete processing of any events it already has read ( not just ones specifically involving the DM cookie )
[18:44] <tomreyn> micahg: do you think you might have the time to look into #955383 today (I've been told you were considering to take on it)?
[18:45] <tomreyn> i don't want to be pressing, this is just meant to be a friendly reminder since you surely have a lot on your list
[18:45] <tomreyn> (and we're a little worried not knowing the exact deadline)
[18:45]  * micahg wonders what he forgot to do
[18:46]  * JackyAlcine_ waits for the day that we have one million bugs reported.
[18:46] <tomreyn> i don't mean to say you forgot to do it ;)
[18:46] <micahg> tomreyn: oops, yeah, sorry, I never finished my work last night, so it spilled over into this morning
[18:47] <tomreyn> cool, as long as it's still on the list and you are aware of the deadlines involved that's perfect. and thanks for offering to take on it.
[18:52] <Q-FUNK> https://bugs.launchpad.net/xkeyboard-config/+bug/738314/
[18:52] <Q-FUNK> this was fixed at Debian ages ago but, for some reason, was never merged.
[19:09] <sladen> Riddell: need to wait for a Unicode codepoint
[19:11] <Riddell> sladen: ah turkish government a bit slower than the indian government
[19:15] <sladen> ~,
[19:47] <bmoez> I have problems with APT system. it happend to me two times errors like this place.
[19:47] <bmoez>     $ sudo apt-get ( upgrade Or install -f ..)
[19:47] <bmoez>     Lecture des listes de paquets... Erreur !
[19:47] <bmoez>     E: Encountered a section with no Package: header
[19:47] <bmoez>     E: Problem with MergeList /var/lib/apt/lists/tn.archive.ubuntu.com_ubuntu_dists_precise-updates_multiverse_binary-i386_Packages
[19:47] <bmoez>     E: Les listes de paquets ou le fichier « status » ne peuvent être analysés ou lus.
[19:47] <bmoez> synaptic (or gdebi ...) went i open it , it close with error. lubuntu and ubuntu software center don't open
[19:47] <bmoez> i don't know how to report this bug in launchpad
[19:48] <bmoez> what is the log file to post?
[19:49] <JontheEchidna> try running sudo apt-get update
[19:50] <bmoez> i tried
[19:50] <JontheEchidna> hmm, try removing that file and then re-updating
[19:55] <slangasek> psusi: it's a deliberate upstream change; the reason it's ok to drop events when exiting is that we restart udev again from the real rootfs and coldplug all the events seen up to that point, so the only events we have to worry about are those that something else in the initramfs is still waiting for.
[20:00] <kklimonda> does the fact that Kubuntu is still in main means that Canonical will support it (as in provide support to people who buy it from them)?
[20:01] <Riddell> kklimonda: ask canonical
[20:01] <kklimonda> Riddell: who can I ask that?
[20:01] <Riddell> kklimonda: contact details are on canonical.com
[20:01] <kklimonda> Riddell: I'm afraid I'll get a standard "fill this form and we'll contact you"
[20:01] <Riddell> you might be right there
[20:04] <bmoez> JontheEchidna: ok, i delete the file but i have the same error white other files, so, i delete all, and now every thing is good
[20:04] <bmoez> but for new user it 's dificult
[20:04] <JontheEchidna> cool, what happened was that somehow the files got corrupted (during download or otherwise)
[20:05] <bmoez> JontheEchidna: so, why apt dodn't correct it alone?
[20:05]  * JontheEchidna shrugs
[20:05] <jalcine> Wouldn't hurt to try it though.
[20:06] <bmoez> or in update, system ask user to remove files and re-update in easy way for new user
[20:07] <bmoez> and i think ubuntu software center don't should close directly
[20:08] <micahg> cjwatson: any chance merges.u.c can get start updating again?
[20:16] <mhall119> seb128: ping
[20:16] <seb128> mhall119, hey
[20:16] <mhall119> seb128: hey, I'm blogging again ;)
[20:16] <mhall119> this time to get SVG icons for some apps that only have low-res raster images
[20:17] <mhall119> would you mind reading it over before I publish?
[20:17] <ajmitch> because seeing those .xpm icons in the dash isn't great? :)
[20:17] <seb128> mhall119, can do
[20:17] <mhall119> ajmitch: let's call it less than ideal
[20:18] <mhall119> seb128: http://people.ubuntu.com/~mhall119/blog/icons.html
[20:18] <arand> mhall119: If there are no svg icons, are there any benefit to supplying downsized pngs for x48 if the source is, say x128?
[20:20] <mhall119> arand: possible, but alt-tab can be > 128px too
[20:21] <seb128> mhall119, no, no, no
[20:21] <seb128> mhall119, we will not distro patch icons, no way
[20:21] <arand> Yeah, well say the source is 512x512 then :) I've been trying to figure out how DEs does this and I can't really find an answer...
[20:22] <seb128> mhall119, that works has to be done upstream
[20:22] <seb128> mhall119, that blog post is another receipe for disaster
[20:26] <mhall119> seb128: why not add icons to the distro package
[20:26] <mhall119> ?
[20:26] <seb128> mhall119, random reasons I can think about
[20:27] <seb128> - most packers are not artists, I wouldn't feel qualified to judge of artwork quality for example
[20:27] <seb128> - icons patches are a pain to maintain
[20:27] <seb128> - upstream might be unhappy about us changing their brand
[20:28] <seb128> - there is no reason those changes should go downstream rather than upstream directly
[20:28] <seb128> - the work is not worth the win
[20:28] <mhall119> seb128: I specifically say to not change the branch, and coordinate new image file creation with upstream, is that not enough to soothe those points?
[20:28] <seb128> no
[20:28] <seb128> the sponsoring queue is still "spammed" with the unity list call you did
[20:28] <seb128> we are not set up to deal with that level of distro changes
[20:29] <seb128> you are just flooding dholbach_, and others with sponsoring requests we have an hard time to deal with
[20:29] <seb128> it's not helping, it's making our job harder
[20:31] <mhall119> ok, so what would you like me to do, direct people to just work with upstream to get these fixed for 12.10?
[20:34] <seb128> mhall119, yes, it's out of 12.04 scope in any case, recommend them opening bugs upstream and a tagged bug in launchpad
[20:34] <seb128> so we can track those and help getting them upstreamed
[20:34] <seb128> but please no sponsoring requests
[20:34] <mhall119> seb128: ok, I'll re-work this to focus on upstream coordination
[20:35] <seb128> mhall119, thanks
[21:12] <dobey> arand: fwiw, the standard sizes for icons per tango style guidelines is 16, 22 (24), 32, 48, and 256. these are the sizes upstream gnome provides
[21:13] <arand> dobey: Yeah, but I think that is based heavily on that the smaller sizes are actually different source images, for clarity.
[21:14] <arand> In that case it's an obvious choice.
[21:16] <dobey> arand: they aren't, actually
[21:16] <dobey> arand: well, they are drawn in the same SVG, and extracted to separate PNG images from there
[21:16] <chrisccoulson> is there any point in providing nice, big, crisp icons when we make them all blurry in the dash anyway?
[21:17] <arand> Ah, well, I'm going from the point of the source being a raster (oftentimes the case)
[21:17] <dobey> chrisccoulson: we can draw them pre-blurred in the exact opposite way that the dash blurs them!
[21:17] <chrisccoulson> heh
[21:17] <mdeslaur> lol
[21:17] <arand> If I have a x256 source image which I could either install two versions of, one reisized down to x48. Or just install as x256 and let the DE do the resizing, which would I choose?
[21:18] <arand> (and the source is a png)
[21:18] <dobey> arand: let the system do the scaling
[21:18] <dobey> arand: or draw the smaller sizes which you should have done anyway
[21:19] <arand> dobey: I'm a mere packager, not an artist ;)
[21:22] <arand> dobey: That's good to know though, less packaging work :3
[21:56] <mterry> @pilot out
[22:24] <seb128> could somebody reject https://code.launchpad.net/~dereknance-413/ubuntu/oneiric/klogshow/fix-for-678153/+merge/96059 ?