[00:01] <RAOF> @pilot in
[03:21] <TheMuso> has anybody updated recently and found their system unable to boot? I get a message "mountall: Disconnected from plymouth" and the system stops there. Am able to change VTs/reboot, but don't hae a login prompt.
[03:22] <TheMuso> have
[03:24] <TheMuso> I should clarify that this is oneiric.
[03:56] <RAOF> TheMuso: I did get that recently when the root filesystem wasn't being passed to the kernel correctly.  Maybe your grub configuration is broken?
[03:58] <TheMuso> RAOF: Ah ok, just booting into a live CD and settings things up to chroot in, thanks for the pointer.
[04:30] <RAOF> @pilot out
[05:21] <didrocks> good morning
[06:59] <dholbach> good morning
[07:28] <jamespage> good morning
[07:29] <jamespage> please could an archive admin accept the NEW binary packages for felix-shell and jasypt in oneiric
[07:32] <didrocks> jamespage: done
[07:33] <jamespage> didrocks: thankyou!
[07:33] <didrocks> yw :)
[08:16] <smb> @pilot-in
[08:16] <udevbot> Error: "pilot-in" is not a valid command.
[08:16] <smb> @pilot in
[09:44]  * smb is looking at https://launchpad.net/ubuntu/+source/xen/4.1.1-1ubuntu1/+build/2639667
[09:45] <smb> It seems to depwait on ipxe (universe). Though that should be there and not having changed recently...
[09:45] <StevenK> smb: xen is in main.
[09:45] <StevenK> smb: It can not build against anything in universe.
[09:46] <smb> StevenK, Hm, has zul moved that? Need to check, cause it built before
[09:47] <Laney> looks like it was moved to main indeed
[09:47] <Laney> https://launchpad.net/ubuntu/+source/xen/+publishinghistory
[09:47] <StevenK> xen 4.1.0-3ubuntu4 was promoted from universe to main 3 days ago
[09:47] <smb> Ok, it seemed to have moved to main with 4.1.0-4
[09:48] <smb> Ah and was not in main when it built
[09:48] <StevenK> Right
[09:48] <smb> StevenK, Ok thanks. Guess I have to talk to zul then
[09:49] <Laney> find the MIR and spank appropriately
[09:49] <StevenK> Indeed
[09:49] <StevenK> https://bugs.launchpad.net/ubuntu/+source/xen/+bug/790854~
[09:50] <StevenK> Which is not right, zul needs a spank
[09:51] <smb> Not sure about delivering any spank, but I'll bring it to notice
[09:54] <StevenK> smb: Coward :-P
[09:55] <smb> StevenK, Nah, it's called "wise"... ;)
[10:04] <Daviey> smb: I thought there was a MIR for ipxe
[10:05] <smb> Daviey, Can't say for sure. I am just the guy wondering... :-P
[10:05] <Daviey> bah, maybe not.. zul was asked to raise one, i'm sure it's on his todo
[10:05] <Daviey> (it shows on components-mismatch aswell)
[10:06] <Daviey> smb: is it blocking you?
[10:07] <smb> Daviey, Just wanted to see how much of the issues remain on oneiric dom0 running hvm with the latest build
[10:07] <smb> And then wondering why I still cannot see it after it being uploaded for a while now
[10:08] <Laney> Launchpad doesn't email about dependency wait, does it?
[10:08] <Daviey> :(.. i'm sure zul will follow up on it today.
[10:10] <smb> Daviey, I am sure we sort it out. Just happened to stumble over it
[10:10] <Daviey> smb: thanks.
[10:13] <mvo> smoser: I had terrible network problems yesterday, I'm happy to talk about the squid-deb-proxy defaults again today
[10:13] <mvo> smoser: I'm not religious about it, if everything else things the default is wrong I'm fine changing it
[10:20] <Daviey> mvo: Providing it's not an open proxy and only supports deb archives, i think it can be more relaxed.  Ideally, support debconf offical-ubuntu-archives-only & ppa-archives-allowed.. oh, and can i have a pony?
[10:21] <mvo> Daviey: only a small one ;)
[10:22]  * mvo will look at it after lunch
[10:23] <Daviey> :)
[10:59] <juliank> Whoever marcus.haslam@canonical.com is, I just got 7 emails from Launchpad on a bug report (Bug #769874) with an automatic reply that he is out of office. And now more on other bug reports. If someone has the power to stop this, please do so.
[11:07] <sladen> juliank: Marcus is the Brand Lead, and is on holiday.  He was using a local hacked-up autoresponder.  Marcus was contacted by somebody from IS very speedily, but still a few hundred made it out of the queue
[11:09] <StevenK> sladen: If you give me a list of the bugs and comment numbers, I can get them hidden for you
[11:09] <sladen> StevenK: awesome
[11:10] <juliank> sladen: With local hacked-up autoresponder, you mean the "X-Mailer: Apple Mail (2.936)"?
[11:11] <juliank> Not only away messages, but also Apple client.
[11:12] <sladen> juliank: aye.
[11:16] <juliank> sladen: And what's IS?
[11:18] <sladen> juliank: Information Systems.  The sysadmins employed by Canonical who looks after the Ubuntu and Canonical servers
[11:18] <sladen> juliank: (eg. the people who answer RT (Request Tracker) mails when there is an issue)
[11:18] <juliank> sladen: OK, thanks for the explanation.
[11:22] <sladen> StevenK: do you need the comment numbers (those are going to take longer for me to get, especially as LP is 303'ing my wget requests to grep them
[11:23] <sladen> StevenK: or can you run a query for  WHERE .comment STARTSWITH "I'm out of the office until 1st August."
[11:25] <StevenK> sladen: I can't run a query, no.
[11:25] <chrisccoulson> will an alternate dependency hold a NBS binary in the archive?
[11:26] <chrisccoulson> ie, listen depends on python-webkit | python-gtkmozembed, with the latter being NBS
[11:26] <chrisccoulson> and we want the latter to go away
[11:26] <seb128> chrisccoulson, it should not
[11:27] <chrisccoulson> seb128, what about if a package recommends a NBS binary?
[11:28] <seb128> don't do that ;-) not sure but archive admin can clean binaries that are still being used if they want
[11:29] <seb128> chrisccoulson, the nbs cleaning is not automatic anyway
[11:29] <seb128> so if the nbs list is an alternative depends and a recommend just ask for the binary to be cleaned anyway
[11:30] <chrisccoulson> seb128, oh, i didn't realize it wasn't automatic
[11:32] <seb128> chrisccoulson, the NBS with no rdepends are semi-automatically cleaned, i.e archive admin have a script they run to clean those
[11:32] <seb128> chrisccoulson, the one with rdepends will need manually cleaning
[11:34] <chrisccoulson> g'ah, this keeps python-gtkmozembed in the archive - https://launchpad.net/ubuntu/+source/indiv-screenlets
[11:35] <chrisccoulson> not sure why that wasn't on my radar before
[11:37] <sladen> StevenK: is there anyone else who can run such a query (this would be faster)
[11:38] <sladen> StevenK: wget and screen-scraping is fairly low-tech solution
[11:38] <chrisccoulson> and https://launchpad.net/ubuntu/+source/freespeak
[11:38] <chrisccoulson> grrrr
[11:38] <chrisccoulson> and there was me hoping that we would finally get rid of xulrunner from the archive this afternoon
[11:48] <chrisccoulson> seb128, bug 816377 ;)
[11:48] <chrisccoulson> (although, i still need to fix 2 packages to stop pulling in python-gtkmozembed)
[11:48] <seb128> chrisccoulson, ok
[11:50] <StevenK> sladen: Yes, a LOSA can, but I'm not certain enough of the data model.
[11:51] <sladen> StevenK: I'm writting some LPAPI code to get them
[11:54] <sladen> StevenK: okay, I have a script.  what format do you want these in?  (since I can have the script print them in any format you want)
[11:55] <StevenK> sladen: A shell for loop? :-)
[11:55] <StevenK> Hm, that won't work
[11:55] <StevenK> sladen: <bug> <comment 1> <comment 2> ....
[11:55] <sladen> stevenk: what command are you going to run?  Is it something I can run my self anyway?
[11:56] <StevenK> sladen: I'm going to run my own API script -- and no, you don't have access to the particular knob
[12:15] <jamespage> please could an archive admin accept the felix-bundlerepository binary packages waiting in NEW into oneiric - ta
[13:04] <lool> cjwatson: Hey, I had some "vmlinuz-foo" kernels in /boot which were picked up by grub in the past; now they still get picked up, but there's a dpkg warning: dpkg: error: mauvaise syntaxe de la version «%off%»%: version number does not start with a digit
[13:04] <lool> dpkg: error: mauvaise syntaxe de la version «%on%»%: version number does not start with a digit
[13:05] <lool> cjwatson: I think it's because update-grub calls dpkg --compare-version on /boot/vmlinuz-on and -off (local kernels of mine)
[13:05] <lool> cjwatson: this is not causing me any issue, but I wanted to share this with you in case it could create trouble to specific setups
[13:13] <ogasawara> @pilot in
[13:14] <cjwatson> lool: ok, please file a bug since I'm at DebConf right now
[13:21] <ahasenack> hi guys, is someone from the sru team here? I would like to check on the status of the upload to lucid-proposed of https://bugs.launchpad.net/bugs/813477
[13:22] <Daviey> If an AA wants to tackle bug #816408, it would be post appreciated.  Thanks.
[13:22] <Daviey> s/post/most/
[13:25] <lool> cjwatson: bug filed as LP #816411 for the error messages during upgrade
[13:29] <slangasek> Daviey: we don't normally have bug reports for demotions, we auto-demote based on things being unseeded; if eucalyptus needs to be removed from the seed, that's core-dev, not AA
[13:34] <Daviey> slangasek: Yes, it is now unseeded - the bug is maninly for tracking as it's quite complex.
[13:35] <Daviey> (shows in component-mismatches, but it's not clear to an AA driving by - so the list hopefully helps)
[13:36] <slangasek> hmm, well, I think component-mismatches is probably clear - it's also authoritative, so please make sure there's nothing listed on components-mismatches that you *don't* want unseeded ;)
[13:37] <Daviey> slangasek: Oh, ok - was trying to make AA's life easier.  Guess we failed.
[13:38] <slangasek> Daviey: sorry - hope you didn't spend too much time on the bug
[13:38] <Daviey> well it was jamespage i should apologise to.
[13:39] <jamespage> Daviey, slangasek: only ~10 minutes :-)
[13:50] <apw> cjwatson, i believe i am correct is saying that grub2 takes the MTRRs from the BIOS in the normal case
[14:02] <cjwatson> apw: http://lists.gnu.org/archive/html/grub-devel/2010-06/msg00129.html
[14:03] <cjwatson> apw: basically yes it currently trusts the BIOS to set things up correctly (as the architecture manual says it should :-P)
[14:04] <apw> cjwatson, yeah, thought that was the case, seems that an acer here with 2gb of ram gets a bad overlapping mtrr combination which results in UC for all ram
[14:04] <apw> cjwatson, totally a bios bug, but of course windows and F15 fix it as they boot and are not affected
[14:07] <apw> cjwatson, and indeed our liveCD isn't affected, so i assume syslinux does something
[14:07] <cjwatson> syslinux probably isn't trying to do the same things with video - I expect it's only using INT 10 for video
[14:07] <cjwatson> whereas grub is writing to video memory directly
[14:07] <cjwatson> I imagine that if you disable gfxterm it'll wowrk
[14:07] <cjwatson> *work
[14:08] <apw> cjwatson, yes its better, but also the kernle is slow, and that doesn't happen with liveCD (syslinux) which is interesting
[14:09] <cjwatson> I don't see anything in syslinux that fiddles with MTRRs (aside from showing them)
[14:09] <Quintasan> Humm, anyone has any idea why jobserver is not available in my pbuilder? I wanted to do -j12 but make throws  warning: jobserver unavailable: using -j1.   out
[14:09] <apw> cjwatson, now that is odd
[14:09] <cjwatson> I would have expected the kernel to fix things up either way
[14:10] <apw> cjwatson, nope, it assumes that the bios is right by default
[14:10] <apw> one can ask for it to fix them
[14:11] <apw> it is possible that F15 has this enabled by default, i'll try and find out
[14:25] <evfool> mvo: now that natty and later won't have a notification area, what will happen with update-notifier?
[14:27] <mvo> evfool: the original goal was to use a upstart session script
[14:27] <mvo> evfool: but it does not quite support everyhitng needed :/ it needs file watching and time (cron) like events
[14:31] <seb128> jdstrand, hi
[14:31] <seb128> jdstrand, could we maintain those apparmor profiles out of the corresponding sources? like telepathy-missing-control
[14:32] <seb128> jdstrand, it's annoying to stop being in sync with debian on the telepathy stack when we have no real maintainer on our side for that stack just because of apparmor profiles
[14:34] <jdstrand> seb128: well, it has been our policy on the security team to ship enforcing profiles in the software that they confine. this actually helps with maintenance of the profile. The best course would be to get this upstreamed in debian, like we do with cups, et al
[14:34] <jdstrand> seb128: I figured I would try to pursue that once the profile bugs are shaken out
[14:34] <seb128> jdstrand, do you plan to send those to the bts? ;-)
[14:34] <seb128> jdstrand, ok thanks
[14:35] <seb128> jdstrand, I'm just trying to make sure the telepathy stack doesn't start being outdated because we stop syncing and nobody is looking at updating those for Ubuntu
[14:35] <seb128> jdstrand, I guess I will add them to the desktop watch list
[14:36] <jdstrand> seb128: I get that, but I'd like to point out that this is an important security benefit for users, since telepathy processes untrusted input over the network
[14:36] <jdstrand> seb128: but like I said, I was going to try to get it into Debian, since they have an apparmor userspace now
[14:37] <jdstrand> seb128: but I wanted to iterate on the profile a bit
[14:37] <seb128> jdstrand, yeah, I was not suggesting dropping the profile, just was wondering if those could be maintained in an ubuntu specific source
[14:37] <seb128> jdstrand, ok, that works too
[14:37] <seb128> jdstrand, thanks ;-)
[14:37] <jdstrand> sure thing :)
[14:39] <hrw> hi
[14:39] <hrw> does someone know does doko went for DebConf?
[14:40] <lucas> he is there, yes
[14:41] <hrw> thx
[14:41] <hrw> so I can skip this week when it comes to cross toolchain hacking
[14:42] <hrw> armel/armhf multilib stuff made ma argh ;D
[14:45] <smoser> is there a debian developer here who could help me out ?
[14:46] <smoser> i'm interested in getting an mbox archive of july debian-devel. it seems those are only available to DD.
[14:46] <smoser> i'd like to respond to the thread http://marc.info/?l=debian-devel&w=2&r=1&s=virtualisation+images+of+Debian&q=b
[14:47] <Daviey> smoser: seriosuly?
[14:48] <smoser> well, yes and no
[14:48] <smoser> :)
[15:01] <Laney> cjwatson: I meant bzr-cvsps-import instead of bzr-cvsimport in my mail, which is why you couldn't find it
[15:01] <ahasenack> hi guys, is someone from the sru team here? I would like to check on the status of the upload to lucid-proposed of https://bugs.launchpad.net/bugs/813477
[15:02]  * Laney added it to the set, but you'll have to remove it from the PPU
[15:08] <infinity> @pilot in
[15:09] <cjwatson> Laney: ah, ok - done
[15:10] <Laney> thanks
[15:15] <jml> fwiw, I upgraded to oneiric today and my laptop now kernel panics on boot
[15:15] <infinity> jml: We stopped supporting your specific model out of spite.
[15:15] <jml> "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)"
[15:15] <jml> is this a thing I should file a bug about?
[15:15]  * jml is downloading a 64 bit natty iso to recover.
[15:16] <infinity> jml: Oh.  Or your root filesystem isn't being found by the initramfs.  And yes, bugs.
[15:16] <jml> infinity: where should I file it?
[15:16] <infinity> jml: Anything fancy about your rootfs?  RAID, dm-raid, dm-crypt, etc, etc?
[15:17] <jml> not really. before I upgraded sometimes grub would look for it and not find it, and I'd have to wait a while before it could find it
[15:17] <jml> forget the exact message, I'm afraid.
[15:19] <infinity> That sounds like the very definition of a "fancy" rootfs.  There's usually not much waiting around for, say, /dev/sda2
[15:19] <jml> well, it's just a plain old magnetic hard drive in a thinkpad
[15:19] <jml> and I don't think I had encrypted the drive or anything like that
[15:20] <jml> the hardware is... unsound. I dropped the laptop once.
[15:20] <infinity> jml: Curious.  Then the bug probably belongs to the kernel, or possibly the hardware, if controllers are timing out.
[15:21] <jml> well, I pulled it sharply by the power cable from a kitchen bench on to a hard floor...
[15:21] <infinity> That tends to be frowned upon in the owner's manual.
[15:23] <jml> yeah
[16:13] <smb> @pilot out
[16:53] <chrisccoulson> directhex, would you be able to help out with bug 798941?
[16:53] <chrisccoulson> ingore the title, there's actually a patch attached for that already
[16:53] <chrisccoulson> but i get a different issue ;)
[16:53] <chrisccoulson> i'm pretty stuck here :)
[17:18] <ahasenack> hi guys, is someone from the sru team here? I would like to check on the status of the upload to lucid-proposed of https://bugs.launchpad.net/bugs/813477
[17:20] <micahg> ahasenack: the SRU team reviews in queue, you just need to get someone to upload (unless you don't think it'll be accepted for some reason)
[17:21] <ahasenack> micahg: zul uploaded it already, monday morning
[17:21] <micahg> ah
[17:44] <dupondje> [ 2682.603886] type=1400 audit(1311702264.071:19): apparmor="DENIED" operation="open" parent=2096 profile="/usr/lib/telepathy/telepathy-*" name="/usr/include/python2.7/pyconfig.h" pid=2097 comm="telepathy-butte" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[17:44] <dupondje> something changed in telepathy ?
[17:45] <jdstrand> dupondje: yes. an apparmor profile was added. that denial was fixed in ubuntu2
[17:45] <dupondje> oh ok thx
[17:45] <jdstrand> bug #816429
[17:46] <dupondje> Ok upgraded and it works :D
[17:46] <jdstrand> \o/
[17:46] <jdstrand> :)
[17:46] <dupondje> up to the next issue :(
[17:47] <dupondje> I want my caps lock to act like a shift-lock
[17:47] <dupondje> Changed it in the regional settings, but doesn't change ..
[17:47] <dupondje> weird
[17:48] <altice> question for all, who is in charge of what gets put into the Repos?
[17:49] <infinity> jdstrand: Not to nitpick, but why would/should tp-butterfly need to read /usr/include at runtime at all?
[17:50] <jdstrand> infinity: yeah, that is weird, but I have noticed it in several python applications
[17:50] <altice> did my post not show in the channel, anyone want to comment?
[17:50] <infinity> altice: The people who upload things.
[17:51] <infinity> altice: (With ~ubuntu-archive vetting new uploads to make sure they're legally sane)
[17:51] <jdstrand> we might consider adding that to the abstraction
[17:51] <altice> ah so it did, okay thanks. So if I wanted a program to be available to the repo I'd have to figure out where/how to upload it?
[17:51] <infinity> jdstrand: Python misfeature, I suppose?
[17:52] <jdstrand> *shrug*
[17:52] <infinity> altice: Depends on your goals.  Do you want to be the person building the packages and uploading them, or do you want to have someone else dealing with those things?
[17:52] <altice> infinity: I ask because I've continually run into issues with compiling a TACACS+ (networking auth server) and would rather fix my problem and others at the same time
[17:52] <jdstrand> the actual access is pretty harmless so I just allow it
[17:52] <infinity> jdstrand: Well, yes, I don't see it as a huge problem from the apparmor POV, just curious if it's actually intended behaviour.
[17:53] <altice> infinity: well honestly, my lack of knowledge on how the process works.....would lead me to want to let someone else take the reigns. However, I wouldn't be opposed to doing it myself, just not sure how to get started
[17:53] <jdstrand> no idea tbh. all I can say is that it isn't the first time I've seen it
[17:53] <jdstrand> right, my totem profile has it, for example
[17:53] <infinity> altice: Well, there are any number of ways to go.  If you're not particularly interested in doing the packaging and ongoing maintenance, I'd start with filing an RFP (request for packaging) bug with Debian, and see if anyone nibbles there.
[17:53] <jdstrand> ah, might be because of C bindings?
[17:54] <jdstrand> *wild guess*
[17:54] <infinity> altice: (Well, first go over http://bugs.debian.org/src:wnpp and see if there's a bug for it)
[17:54] <altice> okay
[17:55] <infinity> altice: There are other avenues, such as packaging a first-cut and trying to find sponsors either in Debian or Ubuntu, or even taking up maintenance yourself, and working to become a Debian Maintainer or an Ubuntu MOTU.
[17:55] <infinity> altice: Each presents more potential work and learning curve for you.  But checking Debian's WNPP and archives is a good start.
[17:55] <infinity> altice: (Heck, what you want may already be in Debian and we just haven't synced it, in which case, such a request could be made to Ubuntu's archive admins)
[17:56] <altice> infinity: you are certainly a wealth of knowledge :) I'm working on looking through the bugs now. I'm saving the suggestions your making so I can go through each avenue
[17:59] <infinity> altice: If you decide to go the "package it yourself" route, both Debian and Ubuntu have fairly good resources for helping making that happen.
[18:00] <infinity> altice: https://wiki.ubuntu.com/MOTU/Packages/REVU and http://mentors.debian.net/cgi-bin/welcome respectively, are used to help review and mentor new packagers and get their packages in good enough shape for inclusion.
[18:00] <altice> infinity: looks like this is the only hit I found: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588172
[18:01] <altice> oh thats neat
[18:01] <altice> anyone else see that?
[18:01] <infinity> Why does that sound familiar...
[18:02] <altice> anyways, I believe the PAM module is an offshoot of the original TACACS server; Should I file a seperate request for simply that?
[18:02] <infinity> Oh, because I know the upstream author.
[18:02] <altice> very cool!
[18:03] <altice> I must say.....since I've gotten into linux I've seen a lot of good community spirit
[18:03] <altice> I like that
[18:03] <infinity> Yeah, I maintain some of Pavel's other software in Debian.  He seems to have fallen off the face of the planet lately. :/
[18:03] <altice> well let's hope it's not for any serious reasons
[18:03] <infinity> Anyhow.  If what you're looking for is a daemon or something rather than the pam library, an RFP for that would be good, yes.
[18:04] <altice> alright
[18:04] <infinity> Nah, he's a tinfoil-hat security nut, I assume he's just hiding in a hole, covered with leaves.
[18:04] <infinity> He'll pop up eventually.  Pun intended.
[18:04] <altice> bwahahaha!
[18:04] <altice> in comes the guy from futurama who can 'hear peoples thoughts'
[18:27] <dupondje> If changing Caps lock into a shift-lock doesn't do anything. Where to report a bug ?
[18:27] <dupondje> Don't know what packages should take care of that
[19:08] <ahasenack> micahg: about that landscape-client package, do you know where it is?
[19:10] <micahg> ahasenack: SRUs for the last day haven't been processed yet
[19:11] <micahg> ahasenack: it's here: https://launchpad.net/ubuntu/lucid/+queue?queue_state=1&queue_text=
[19:12] <ahasenack> micahg: thanks
[20:26] <ogasawara> @pilot out
[20:36] <barry> uh oh.  i just updated gconf in my vm and now boot hangs
[20:47] <seb128> re
[20:47] <seb128> barry, what lightdm version do you have in your vm?
[21:15] <barry> seb128: 0.9.2-0ubuntu1
[21:15] <seb128> barry, do you have lightdm-greeter-gtk?
[21:16] <seb128> ups
[21:16] <seb128> lightdm-gtk-greeter
[21:17] <barry> seb128: apparently not (i'm looking at the installed package list through landscape since obviously the machine doesn't boot)
[21:17] <seb128> barry, it probably boots but has no dm greeter, switching to a vt should work?
[21:17] <seb128> barry, well install that
[21:17] <barry> seb128: interestingly, i apparently have lightdm-greeter-example-gtk
[21:17] <barry> seb128: let's see if i can do that
[21:18] <seb128> barry, you probably upgraded before I fixed the package to properly recommends
[21:18] <barry> ouch ;)
[21:18] <seb128> barry, that package doesn't exist with 0.9.2
[21:18] <seb128> barry, it should have got removed since it depends on a library which is conflicting with the update
[21:18] <seb128> barry, lightdm-greeter-example-gtk I mean
[21:19] <dupondje> had same issue here :) but lightdm-gtk-greeter fixed it :)
[21:19] <barry> seb128: huh.  i did get a vt.  let me install lightdm-gtk-greeter then...
[21:19] <seb128> did somebody didn't upgrade yet and can tell me if an update && update install it?
[21:21] <dupondje> Its not yet published it seems
[21:21] <dupondje> so :)
[21:22]  * barry reboots
[21:22] <barry> lightdm-greeter-gtk installed
[21:22] <barry> seb128: beauty, that fixed it!  and it's nice to see i can actually click on my name and log in again :)
[21:23] <barry> seb128: thanks!
[21:23] <seb128> barry, yw ;-)
[21:24] <micahg> I'm waiting for ubuntu2 to hit the mirror, ubuntu1 definitely doesn't upgrade the greeter
[21:24] <seb128> micahg, thanks
[21:33] <seb128> kirkland, hey
[21:33] <kirkland> seb128: howdy!
[21:34] <seb128> kirkland, just as fyi GNOME3 has a new user account dialog
[21:34] <seb128> new technologies as well
[21:34] <seb128> it's in gnome-control-center and uses accountsservice dbus service
[21:34] <kirkland> seb128: hmm, okay;  some ecryptfs work needed?
[21:34] <seb128> kirkland, that doesn't know about ecryptfs, I noticed yesterday
[21:35] <seb128> kirkland, well if you want oneiric to have an ui to create ecryptfs users I guess so
[21:35] <kirkland> seb128: ah, okay;  can't say i'm surprised
[21:35] <seb128> kirkland, sorry for the late notice, I didn't think about it earlier
[21:35] <seb128> well "late" in the cycle
[21:35] <kirkland> seb128: right
[21:35] <seb128> rodrigo from the desktop team is upstream gnome-control-center comaintainer
[21:35] <seb128> he can probably help you to get that done if you have question
[21:36] <seb128> but he doesn't know about ecryptfs I think
[21:36] <kirkland> seb128: so I sent robbiew and slangasek and rickspencer3 a note last week, saying that ecryptfs is pretty far outside of my job responsibility and leisure time possibilities these days, so I asked them for some help staffing someone to look after ecryptfs, if we still care about it as a distro
[21:36] <seb128> kirkland, do you think you could maybe open a bug with what g-c-c would need to do?
[21:36] <seb128> so we can probably help on getting the integration side done
[21:36] <barry> kirkland: i hope we do!
[21:37] <kirkland> seb128: sure -- i think you just need a checkbox, and add --encrypt-home to the adduser call
[21:37] <seb128> kirkland, ok that seems easy enough
[21:37] <kirkland> barry: me too;  but I need some distro help on that ;-)
[21:37]  * barry nods
[21:37] <kirkland> barry: so glad to hear you speak up
[21:37] <seb128> kirkland, well free free to reply that you have no time to help on that if you are busy
[21:37] <kirkland> sure
[21:38] <seb128> kirkland, but seems like from your description it should be easy enough
[21:38] <kirkland> seb128: is there a bug already?
[21:38] <seb128> no
[21:38] <kirkland> seb128: or do you want a new one?
[21:38] <kirkland> k
[21:38] <kirkland> seb128: g-c-c is gnome-control-center?
[21:38] <seb128> we need one, if you are to register it please do
[21:38] <seb128> yes
[21:40] <kirkland> k
[21:40] <seb128> kirkland, if you don't I will do it later this week
[21:40] <kirkland> seb128: i'm filing now
[21:40] <seb128> ok great
[21:40] <seb128> thanks
[21:42] <kirkland> seb128: presumably g-c-c calls "adduser" and not some other user creating mechanism, right?
[21:42] <seb128> kirkland, right, well it uses accountsservice which use adduser yes
[21:42] <kirkland> seb128: okay
[21:44] <kirkland> seb128: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/816669
[21:45] <seb128> kirkland, thanks!
[22:00] <dtchen> seb128: just a note: using aptitude to update and upgrade lightdm to 0.9.2-0ubuntu2, lightdm-gtk-greeter does not get installed if lightdm-greeter-example-gtk or anything else providing lightdm-greeter is already installed.
[22:00] <dtchen> (which is expected due to the alternate)
[22:01] <seb128> dtchen, isn't the example greeter getting uninstalled?
[22:01] <dtchen> seb128: no, it isn't.
[22:01] <seb128> hum
[22:01]  * micahg ♥ aptitude
[22:01] <seb128> so I misread the
[22:01] <seb128>     - lightdm conflicts with liblightdm-gobject-1 and liblightdm-qt-1 so old
[22:01] <seb128>       greeters will be removed.
[22:02] <seb128> checking...
[22:03] <micahg> seb128: missing a -0 on the libs
[22:03] <seb128> it should conflicts on liblightdm-gobject-0-0  as well I guess
[22:05] <micahg> seb128: the current conflicts don't exist, they're both missing the second -0
[22:05] <seb128> mic
[22:05] <seb128> micahg, right, fixing...
[22:07] <micahg> seb128: wouldn't it just be better to break/replace on the old greeters?
[22:07] <seb128> same difference?
[22:09] <micahg> practically, yeah
[22:13] <nemo> Say, anyone notice that the featured apps in Natty version of software centre seem to click through to different apps than what you see in the list?
[22:13] <nemo> (under What's New)
[22:13] <nemo> sometimes works, sometimes doesn't.
[23:41] <SpamapS> if I have an upstream with a debian/ dir and I want to completely ignore said dir for all 'merge-upstream' .. how can I achieve this?
[23:41] <SpamapS> seems like it just makes merge-upstream nearly impossible every time.
[23:43] <jelmer> hey sp	
[23:43] <jelmer> *Spamaps
[23:43] <SpamapS> jelmer: howdy
[23:44] <jelmer> SpamapS: does the debian/ directory in the upstream change often?
[23:44] <SpamapS> jelmer: occasionally
[23:44] <RAOF> Yeah, that's really ugly.  One more for the “please don't keep debian/ in your upstream” files :/
[23:45] <jelmer> SpamapS: so, I don't really have a good answer
[23:45] <SpamapS> I will ask again for them to remove it. :-/
[23:45] <SpamapS> By them, I mean us.. because I'm a committer.. .. but.. reviews.. procedure.. blah blah. :-P
[23:45] <SpamapS> actually I'm not even sure why its coming up as conflicting
[23:46] <jelmer> SpamapS: you'll prbably get conflicts every time the debian/ directory in upstream changes even if you remove it manually after merge-upstream
[23:46] <SpamapS> other than that they have different ancestors
[23:46] <jelmer> if they have different ancestors then it would cause a conflict
[23:46] <SpamapS> I was hoping maybe --forget-merges would help but it doesn't seem to.
[23:47] <jelmer> since bzr keeps track of the identity of the various files, rather than assuming that files with the same path are the same file - this is what makes the renames work
[23:47] <RAOF> Could you branch upstream, delete the debian dir, and then merge from that?
[23:47] <SpamapS> they did at one very early point come from the same place
[23:47] <jelmer> SpamapS: it should be fairly easy to deal with the conflict after a merge though
[23:47] <jelmer> bzr merge-upstream && bzr resolved --take-this
[23:47] <SpamapS> No its really painful
[23:48] <SpamapS> its renaming debian to debian.moved
[23:48] <SpamapS> and putting some files in there and leaving some.. its really confusing
[23:49] <poolie> we should really merge that better
[23:49] <micahg> jelmer: I think this bug is a blocker for general UDD adoption since source format 3 DTRT
[23:49] <poolie> yes, there's a bug that's on our udd-affecting list
[23:50] <SpamapS> I may just be showing some impatience..
[23:50] <SpamapS> Anyway, I've slogged through it again.. will poke the bug.
[23:51] <jelmer> micahg: agreed
[23:52] <hallyn> i assume oneiric-amd64-alternate not booting is a known current issue?
[23:52] <micahg> jelmer: is it at least stored in the upstream branch with pristine-tar right now?
[23:53] <jelmer> micahg: the original debian/ directory? YTes
[23:53] <micahg> jelmer: k, that would've been a much bigger bug :)
[23:55] <jelmer> it's mainly the handling during merges that's broken at the moment
[23:55] <jelmer> (with quilt patches too)