[00:01] <slangasek> kirkland: pam 1.0.1-3ubuntu3 uploaded
[00:01] <slangasek> kirkland: now supports --remove <profile>
[00:02] <kirkland> slangasek: yo
[00:02] <kirkland> slangasek: is that what I should use in the postrm?
[00:02] <slangasek> kirkland: in the prerm
[00:02] <slangasek> kirkland: I replied to your bug; getting your mail?
[00:03] <kirkland> slangasek: sifting through now
[00:03] <slangasek> k
[00:03] <kirkland> slangasek: just got back to the hotel
[00:03] <slangasek> where are you this week that involves all this hotelling? :)
[00:04] <kirkland> slangasek: london
[00:04] <slangasek> oh-ho
[00:04] <kirkland> slangasek: managers doing their thing, though i had a few work items that involved stealing cjwatson's time
[00:05] <kirkland> slangasek: seeing as the installer is tightly guarded magic ;-)
[00:05] <slangasek> heh
[00:05] <kirkland> (just kidding for anyone else out there (or reading scrollback)
[00:06] <kirkland> slangasek: okay, i'll move the call to prerm
[00:06] <kirkland> slangasek: how did you feel about my postinst logic?
[00:06] <kirkland> slangasek: changed drastically from the md5sum stuff you saw last night
[00:07] <slangasek> hmm, perhaps I need to look clos
[00:07] <slangasek> er
[00:07] <slangasek> I don't think I re-reviewed that part yet
[00:07] <kirkland> slangasek: i subscribed you to the bug
[00:07] <kirkland> slangasek: let me grab the #
[00:07]  * slangasek nods
[00:07] <slangasek> I have it
[00:08] <kirkland> slangasek: i decided that the md5sum of those files depended too much on the precise wording of the pam configs you spit out
[00:09] <kirkland> slangasek: actually, what i (selfishly) care about is whether pam_ecryptfs is in the stack or not
[00:09] <kirkland> actually, i'm in London, so "whether pam_ecryptfs is in the stack or naught"
[00:10] <slangasek> kirkland: ah.  no, I'm not happy with that as a solution.
[00:11] <kirkland> slangasek: i figured as much...
[00:11] <kirkland> slangasek: okay, so lets work this to a compromise..........
[00:11] <slangasek> kirkland: we only want to use --force when we can *verify* that the config files currently on disk are the ones output previously by auth-client-config
[00:12] <kirkland> slangasek: almost....
[00:12] <slangasek> kirkland: if they weren't output by auth-client-config, then AFAICS it's always out of scope for this package to force an overwrite of the user's config
[00:13] <kirkland> slangasek: what about when a user has modified their own pam config, said "libpam-client, leave me alone", and then installed ecryptfs-utils
[00:13] <kirkland> that's a bit harsh....
[00:13] <slangasek> then it's absolutely not the place for this package to override that
[00:13] <kirkland> agreed.
[00:13] <slangasek> because --force will overwrite the config with *no* prompting
[00:13] <kirkland> see: harsh.
[00:14] <slangasek> did you happen to see my proposed postinst from last night? http://pastebin.ubuntu.com/39257/
[00:15] <slangasek> if you can show that there's a case where this doesn't DTRT, that we can fix without clobbering users' config in some cases, then I'm happy to accept that
[00:15] <kirkland> slangasek: i did, however, this involves a lot of trust that the giant blob of comments in those files will not change
[00:16] <slangasek> but --force is only meant to be used when the calling package knows that the configs are not modified by the user
[00:16] <slangasek> er, howso?
[00:16] <kirkland> slangasek: let's say that we ship with an ecyrptfs-utils with a hardcoded md5sum
[00:17] <slangasek> we only need to use --force to handle upgrades from a version that pre-dates pam-auth-config
[00:17] <kirkland> slangasek: IIUC, that md5sum should be a default Ubuntu pam config, where a user has told libpam-client, "yes, please, manage my pam"
[00:17] <kirkland> slangasek: so i get hardcode that md5sum for each of the 3 pam configs i care about
[00:17] <slangasek> the md5sum is the md5sum for the legacy auth-client-config version
[00:18] <slangasek> we're saying "if the user has the config installed by auth-client-config, we know it's safe to overwrite it without prompting"
[00:18] <kirkland> slangasek: ah, that's where, perhaps, we're differing in approaches
[00:18] <kirkland> slangasek: i don't care that much about those individuals
[00:19] <kirkland> slangasek: if someone told libpam-client, "no, please, don't mess with my pam", and they had auth-client-config'd pam_ecryptfs, they still have what I need in the stack
[00:19] <slangasek> sorry, what's "libpam-client" here?
[00:19] <slangasek> libpam-runtime?
[00:19] <kirkland> slangasek: libpam-runtime
[00:19] <slangasek> ok
[00:19] <kirkland> slangasek: pam-client-update/pam-auth-update
[00:20] <kirkland> :-P
[00:20] <kirkland> pam-client-config
[00:20] <kirkland> asdfasdhqw[eriqwlefnsz;ldhqw;elrnaw;eohjqw;erihjqwelih
[00:20] <kirkland> sorry
[00:20] <slangasek> if the user said "no, don't mess with my pam" (which is the default) and they had auth-client-config'd pam_ecryptfs, then they have a set of files that ecryptfs-utils, but not libpam-runtime itself, can detect it's safe to overwrite
[00:20] <kirkland> bye guys
[00:21] <slangasek> if the user said "no, don't mess with my pam" and they /don't/ have pam_ecryptfs in their config, then it's not appropriate for pam_ecryptfs to force itself in there by ignoring the admin's choice
[00:22] <slangasek> if the user /didn't/ say "no, don't mess with my pam" then --force is a no-op
[00:22] <kirkland> slangasek: okay, that seems fair
[00:22] <kirkland> slangasek: what state of a file, then, should I md5sum as the "--force"able state?
[00:22] <kirkland> hello guys
[00:23] <slangasek> and, in the case that they do have a config populated by auth-client-config, we want to upgrade it to the new system so that they get the full n-way module integration going forward
[00:23] <kirkland> slangasek: i drew a flowchart on the whiteboard today, i wish i would have photographed........
[00:23] <slangasek> kirkland: if all of /etc/pam.d/common-{auth,password,session} match what auth-client-config spits out for ecryptfs by default, and /etc/pam.d/common-account matches what libpam-runtime shipped in hardy
[00:23] <kirkland> slangasek: absolutely, the user will have to upgrade libpam-runtime first
[00:24] <slangasek> that's the only case I see where we can say: yes, we know what's in these configs and the user didn't touch them, so we can overwrite without having to ask the user for permission
[00:24] <kirkland> slangasek: that user will have to tell libpam-runtime "yes", or "no"
[00:25] <slangasek> kirkland: I would encourage you to test the proposed postinst in http://pastebin.ubuntu.com/39257/ and see if you can find a case where it doesn't do what's expected :)
[00:26] <kirkland> slangasek: okay, so the case for --force is when /etc/pam.d/common-[auth|password|session] is that which was configured by auth-client-config precisely (as defined by md5sum)
[00:26]  * slangasek nods
[00:26] <kirkland> which implies that the answer to libpam-client was "NooOOOOOOO"
[00:26] <slangasek> if it doesn't match precisely, we really can't know what it is that we'd be overwriting
[00:26] <slangasek> right
[00:26] <kirkland> slangasek: okay, gimme a few to fan that out over a few kvms
[00:26] <slangasek> ok :)
[00:27] <kirkland> slangasek: you around for a few?
[00:27] <slangasek> yep
[00:27] <kirkland> slangasek: i'd love to kill this one and have a good nights sleep :-)
[00:27]  * slangasek grins
[00:27]  * kirkland makes himself busy
[00:27] <slangasek> you mean you won't be like me, sitting at your computer for hours at a time and giddily flipping the switches on pam to watch what happens?
[00:31] <NCommander> kirkland, what are you trying to kill?
[00:31] <NCommander> (I'm currently killing the ada issues in hardy, but I can take a break from it)
[00:50] <kirkland> NCommander: thanks for the offer
[00:50]  * NCommander waits for the but
[00:51] <kirkland> NCommander: i think i've convinced myself yet again that slangasek is the brilliance he expects him to be
[00:51] <kirkland> s/he/i/
[00:52] <slangasek> s/brilliance/eerie dpkg state machine/
[00:52] <NCommander> slangasek's brilliance can't be measured in rational numbers
[00:53] <slangasek> if it were really brilliance, it shouldn't have taken me 5 years to get from concept to implementation :P
[00:53] <ion_> My brilliance is entirely imaginary, too.
[00:53] <NCommander> slangasek, of what specifically?
[00:53] <slangasek> NCommander: pam-auth-update
[00:54] <NCommander> it could be worse
[00:54] <slangasek> (augh, I almost called it pam-auth-config again, I really /did/ name it wrong)
[00:54] <NCommander> You could have ended up coding something like RPM/Vista
[00:54] <kirkland> slangasek: okay, the trick now is finding a kvm of mine that hasn't been maligned yet with curse-ed intrepid updates, with which to take pristine md5sums :-)
[00:54] <slangasek> kirkland: hmm, I thought we already knew what the md5sums were/
[00:55]  * slangasek gesticulates in the direction of his pastebin url
[00:56] <kirkland> slangasek: i had them, a pastebin from last night, if that is to be trusted
[00:56] <kirkland> slangasek: i want to confirm that
[00:56] <slangasek> ok
[00:57] <kirkland> slangasek: for better or worse, i've upgraded almost everything of mine to your new magic
[00:57]  * slangasek grins
[00:57]  * NCommander roots for slangasek's new magic
[00:59] <kirkland> slangasek: ha ha....   fortunately, i have 40G of virtual machines :-)
[01:00] <NCommander> lol
[01:09] <kirkland> slangasek: okay, tell me what you think of http://pastebin.ubuntu.com/39565/
[01:12] <slangasek> kirkland: I think you should also guard against the possibility that /etc/pam.d/common-account has been modified; and I think you do need to have a version check; and I think my code was prettier ;)
[01:12] <kirkland> slangasek: indulge me.... what does the version check gain us?
[01:13] <slangasek> kirkland: but the only one of these that I think is a blocker is the version check - we should skip this md5sum checks entirely if we aren't upgrading from a known non-pam-auth-update version
[01:13] <slangasek> kirkland: it allows for the possibility that, after upgrade, a user has deliberately re-installed the old config files
[01:15] <slangasek> kirkland: I have honestly had users do this sort of thing before, and become irate that on every package update, I would overwrite their config anew :-)
[01:16] <kirkland> slangasek: fair enough.  for whatever reason, i decided to write this from scratch before just plugging and chugging with your code as pasted http://pastebin.ubuntu.com/39257/
[01:17] <slangasek> kirkland: to understand it bette? :)
[01:17] <slangasek> better
[01:20] <kirkland> wow, /me notes the similarity in at least the two comment statements
[01:22] <slangasek> well, you wrote them both, AFAIK ;)
[01:24] <kirkland> slangasek: in that case, both of me agree
[01:24] <kirkland> hehe
[01:24] <slangasek> excellent!
[01:28] <kirkland> slangasek: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/259915
[01:28] <kirkland> slangasek: i'm satisfied with the testing of that patch in my scenarios
[01:31] <slangasek> kirkland: rockin', let me roll that up
[01:31] <kirkland> slangasek: does "roll that up" mean "sponsor it"?   if so, I'd be delighted....
[01:31] <slangasek> yes
[01:31] <kirkland> slangasek: rocking
[01:57] <kirkland> slangasek: i didn't see an upload yet....   did you have a problem with the patch?  or just more pressing issues?
[01:58] <kirkland> slangasek: i was just about to call it a night
[01:58] <slangasek> kirkland: samba was ahead of it in my outbound queue; it's uploaded now
[01:58] <slangasek> \o/
[01:58] <kirkland> slangasek: nice, thx
[02:18] <slangasek> kirkland: hmm, FTBFS on lpia?
[02:21] <kirkland> slangasek: typical
[02:22] <kirkland> slangasek: have never investigated
[02:22] <slangasek> ok
[02:22] <kirkland> slangasek: ie, not a regression
[02:22] <slangasek> it appears to be a regression relative to version 50-1ubuntu1, the last one that built
[02:22] <slangasek> but not a high-priority regression, clearly :)
[04:29] <bytor4232> So, is it safe to upgrade now?  Is pam gonna bork me hard like it did last night ;)
[04:29]  * bytor4232 never even got a phone call
[04:29] <bytor4232> No flowers, no nothin
[04:29] <Hobbsee> it's never save, until it's released.
[04:29] <RAOF> And #ubuntu+1 is likely to contain answers. :)
[04:29] <bytor4232> cool
[05:36] <maco> bug #163156 can be fixed, according to upstream and System76, with new versions of libusb and libfprint.  is there any chance of that bug being closed in intrepid, or will it have to wait for jiggy jaguar to support that hardware?
[05:48] <crimsun> maco: note the proximity of feature freeze.
[05:48] <StevenK> "jiggy jaguar" Oh noes, I hope not.
[05:49] <lifeless> jivin jython?
[05:50] <maco> is a jython an animal? i thought it was just a made up name for the language
[05:50] <lifeless> it is
[05:52] <maco> crimsun: you already talked to me in person. i wanted to see if others agreed with you that it's "oh noes" or if someone who knew more about how libusb works could say if core functionality was affected or not
[05:53] <crimsun> maco: I suspect it's not a matter of "oh noes" but lack of adequate testing
[06:01] <TheMuso> crimsun: Can I help with the issue re pulse by default with a fallback to dmix for alsa-lib?
[06:01] <TheMuso> In terms of patching/implementing?
[06:06] <maco> TheMuso: crimsun says, "tell him that sjoerd's patch is in alsa-plugins 1.0.17 and newer and can be backported to the current one.  and tell him to make sure he checks that the pulseaudio patch that's in debian/patches/ is in place that checks for the environment variable"
[06:07] <TheMuso> maco: Thanks.
[06:07] <maco> ok now crimsun and i go to bed
[06:07] <maco> night night guys
[06:25] <TheMuso> Yay I love ambiguity in replies in the third person. :)
[08:01] <dholbach> good morning
[08:14] <raphink> morning dholbach
[08:14] <dholbach> hi raphink
[08:14] <raphink> ;)
[08:14] <raphink> what's up?
[08:17] <dholbach> just got through most of my mails and will dive into the sponsoring queue now!
[08:17] <dholbach> as you all should :)
[08:17] <raphink> hehe :s
[08:18] <raphink> some time soon, I might get a job with a day for Ubuntu every week
[11:04] <ion_> xserver-xorg-hardcore
[11:37] <tjaalton> ion_: surely you meant xserver-xxxorg-hardcore
[12:22] <nxvl> good morning
[13:32] <cjwatson> slangasek: any time I run pam-auth-update, it duplicates the Additional block in /etc/pam.d/common-*
[13:32] <cjwatson> slangasek: though interestingly it does not duplicate pam_unix in common-password
[13:34] <cjwatson> slangasek: this is bad because the duplicated-bits files cause PAM clients (at least gnome-screensaver and login) to segfault ...
[13:38] <cjwatson> aha
[13:38] <cjwatson> Name: libpam-runtime/profiles
[13:38] <cjwatson> Template: libpam-runtime/profiles
[13:38] <cjwatson> Value: unix, smbpasswd-migrate, ecryptfs-utils, smbpasswd-migrate, ecryptfs-utils
[14:43] <persia> Is anyone up for archive-admin stuff today?
[14:44] <nxvl> persia: i think Hobbsee is
[14:44] <persia> Hobbsee: Can you NEW stuff?
[14:44] <nxvl> but, today is pitti's turn and he is on vacation
[14:44] <persia> nxvl: Hence me not poking anyone specifically :)
[14:44] <Hobbsee> persia: yes.  not at this time of night while i'm half asleep, though...
[14:45] <Hobbsee> unless it's really simple
[14:45] <persia> Hobbsee: It's really simple.  ubuntu-mid-default-settings.  Maybe 20 lines of code, total.
[14:45] <nxvl> Hobbsee: @ .au you have the same tz as japan?
[14:46] <Hobbsee> it's 11.45pm now here
[14:46] <persia> nxvl: No, it's even later for her
[14:46] <Hobbsee> not sure what japan is
[14:46] <nxvl> yeah, one hour
[14:46]  * nxvl love's gnome clock
[14:46]  * Hobbsee looks
[14:50] <Hobbsee> persia: accepted.
[14:50]  * persia adds another 100g to the chocolate debt tally
[14:50] <Hobbsee> hmmm.  i wonder if that's a launchpad bug.
[14:50] <Hobbsee> OK: ubuntu-mid-default-settings(universe/(unchanged))
[14:52] <Hobbsee> yes, apparently it is.
[14:52] <persia> This is a new and different LP bug, or a previous one?
[14:54] <Hobbsee> apparently it's not a bug.
[14:56] <Hobbsee> persia: your binaries are served.
[14:56] <Hobbsee> well, they're still pending an archive run.  but served enough.
[14:57] <persia> Hobbsee: Thank you ever so much.  Now I can go about filing the appropriate removal requests :)
[14:57] <Hobbsee> :)
[14:57] <Hobbsee> can't do them, i'm afriad
[14:57] <persia> No worries.  I'm not blocked on removals, as this means I can ignore the crud until later.
[14:57] <Hobbsee> true
[15:02] <bazaar> hi. is it possible to do bindtextdomain() with gettext without all those subdirectories ("en_US/LC_MESSAGES/")?
[15:24] <huats> I am a bit annoyed : I am creating a new package (a python module) which is called pywebkitgtk (pythons bindings for the webkitgtk). According to my understanding of the python policy, the name of the package should fe python-modulename... which in my case will be python-webkit
[15:24] <huats> isn't it a bit problematic ?
[15:25] <huats> (I mean the loss of the gtk stuff) ?
[15:25] <ogra> python-webkitgtk would be appropriate i guess
[15:26] <ogra> like we have python-gtk2 for upstreams pygtk
[15:26] <ogra> (not sure why that still carries the 2 though)
[15:26] <huats> but the thing is in that case gtk2 is the module name I think
[15:26] <huats> and thus is respects the policy
[15:27] <ogra> i dont think upstream calls it pygtk2
[15:27] <huats> ok
[15:27] <ogra> but if your modules is called pywebkitgtk i'd call the package python-webkitgtk
[15:27] <ogra> *module
[15:28] <huats> ogra the project is called pywebkitgtk
[15:28] <huats> but the module is called webkit
[15:28] <ogra> well, but its not pywebkitqt :)
[15:28] <huats> :)
[15:28] <huats> ok
[15:29] <huats> so I name it python-webkitgtk thus
[15:29] <huats> thanks
[15:29] <dholbach> james_w: ^ do you know anything about that?
[15:30] <james_w> huats: can you give the link to the policy where you saw this?
[15:30] <huats> sure
[15:30] <james_w> I've seen pretty much all the alternatives I think
[15:30] <huats> but let me first find it again :)
[15:31] <james_w> i.e. using the upstream project name, the module name, or something else that makes more sense
[15:32] <huats> james_w:  http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html
[15:32] <huats> 2.2
[15:32] <huats> Public modules should be packaged with a name of python-foo, where foo is the name of the module
[15:32] <james_w> yeah
[15:32] <huats> (and what I explained is my understanding of that :))
[15:32] <jcristau> 'should' != 'must' though
[15:32] <huats> ok
[15:33] <james_w> it's odd they called the module just "webkit"
[15:33] <ogra> yeah
[15:33] <james_w> couldn't there be pure bindings to webkit with that name?
[15:33] <ogra> especially if thats gtk specific
[15:33] <james_w> yeah
[15:33] <huats> i'll report that upstream (I ve very good contacts with them)
[15:33] <james_w> huats: yeah, ask them
[15:34] <james_w> I'd advise going against policy if there's any chance that there will be a pure python-webkit, to save headaches later
[15:35] <ogra> and you will definately make Riddell happy in case there comes a pywebkitqt at some point
[15:36] <huats> OK
[15:36] <huats> so I change my package name to python-webkitgtk
[15:37] <huats> and I ask upstream explaining them everything
[15:37] <huats> (and pushing them toward changing the name of the module...)
[15:37] <ogra> :)
[15:40] <huats> thanks ogra, james_w and dholbach
[15:40] <dholbach> de rien
[15:40] <dholbach> have a great weekend everybody! :)
[15:40] <huats> :)
[15:48] <Riddell> ogra: there is
[15:48] <Riddell> and it uses namespaces
[15:55] <asac> kees: there?
[15:59] <mathiaz> Koon: slangasek and kirkland were working on some pam update changes
[16:00] <kirkland> mathiaz: what's up?
[16:00] <mathiaz> Koon: you may wanna ask them about how to handle pam configuration update wrt to likewise-open
[16:00] <Koon> mathiaz: yes, I suppose it's related. But dendrobates is handling the likewise-open update right now. I'm busy with tomcat6 and wbem
[16:01] <Koon> I only did a quick test on my AD test infra
[16:02] <Koon> kirkland: likewise-open can't join a domain, complains about the current PAM files layout. Apparently a change in /etc/pam.d in recent pam updates confuses it
[16:03] <kirkland> Koon: that's certainly possible...  what does it use?  auth-client-config?
[16:03] <Koon> kirkland: it uses its own let-me-whack-your-pam.d functions
[16:03] <kirkland> Koon: oh, that's about as bad as it gets then
[16:04] <kirkland> Koon: grab the source for ecryptfs-utils
[16:04] <kirkland> Koon: see the bits that involve pam-auth-update
[16:04] <kirkland> Koon: requires libpam-runtime >= something
[16:04] <kirkland> Koon: you'll need a config file for it
[16:04] <kirkland> Koon: and to conditionally run pam-auth-update
[16:05] <Koon> kirkland: might not have time to do that -- but dendrobates will be interested by the pointers
[16:10] <kees> asac: good morning :)
[16:11] <dendrobates> kees: fedora and Redhat.  hahahaha
[16:11] <asac> kees: good morning ... bb in 40min
[16:11] <asac> ;)
[16:12] <dendrobates> kees: I'm sure they had a good laugh at us.  ;)
[16:12] <emgent> dendrobates: lol
[16:13] <kees> dendrobates: to name it 'openssh-blacklist'.  it's so confusing, it's funny.  :)
[16:13] <wgrant> kees: I saw that and wondered if I'd misunderstood the vulnerability, then I realised that they just named it badly.
[16:26] <emgent> we have high confidence
[16:26] <emgent> that the intruder was not able to capture the passphrase used to secure
[16:26] <emgent> the Fedora package signing key
[16:26] <emgent> haha
[16:27] <mkrufky> LOL
[16:28] <mkrufky> if you ask me... if anybody cares about security, that key needs to be changed regardles, lol
[16:29] <jcristau> mkrufky: guess what.. that's what they're doing
[16:29] <cjwatson> slangasek: do you know what http://cdimage.ubuntu.com/stable is, apart from a Windows executable?
[17:00] <mkrufky> is intrepid safe enough to use for a developer who isnt afraid to get his hands dirty (but would prefer not)
[17:00] <mkrufky> ?
[17:01] <cody-somerville> mkrufky, the safe answer is no
[17:04] <mkrufky> hehe
[17:04] <mkrufky> ok
[17:05] <mkrufky> thanks, cody-somerville
[17:06]  * calc still isn't using intrepid either :)
[17:06] <persia> mkrufky: That said, lots of people do use it every day, just be aware that it *will* break, so you may need to fix it.
[17:06] <calc> i just build in a intrepid chroot
[17:06] <kirkland> slangasek: Riddell: cjwatson: hi arch admins...  kees pointed me to you, to "deNEW" the package update-motd from https://launchpad.net/ubuntu/intrepid/+queue
[17:07] <calc> i'll probably upgrade to intrepid on Oct 2 (Beta)
[17:07] <mkrufky> hmm, well then maybe its a better idea for me to just install hardy on this new server
[17:07] <mkrufky> (server for home use -- not for business)
[17:08] <Riddell> kirkland: looking
[17:09] <Riddell> kirkland: accepted
[17:09] <kirkland> Riddell: thank you, sir!
[17:19] <Riddell> mvo: http://www.kubuntu.org/~jriddell/tmp/update-notifier-kde_0.1_all.deb should you want to take a keek
[17:23] <ogra> kirkland, "update-motd - This package contains a generic framework for regularly running"
[17:24] <ogra> running what ?
[17:24] <Riddell> doh
[17:24] <ogra> a sports package :)
[17:25] <kirkland> ogra: whatever you put in /etc/update-motd.d/, concatenated together and written to your motd
[17:25] <kirkland> ogra: is the control file broken?
[17:25] <Riddell> kirkland: first line of description is the short description, that should be fixed
[17:25] <ogra> looks like
[17:25] <persia> Also overly wordy: doesn't fit the guideline $(packagename) is a $(short-description)
[17:25] <Riddell> long descriptin starts on the next line
[17:25] <kirkland> Riddell: that should be a one liner, then?
[17:25]  * \sh has a new toy...acer netbook, with 120GB hd...looks very neat...now it just needs ubuntu on it, and not linspire
[17:25] <Riddell> kirkland: yes
[17:26] <ogra> yeah, its trivial and not harmful
[17:26] <kirkland> Riddell: fudge, sorry, i'll fix immediately :-)
[17:26] <persia> kirkland: Also doesn't need to be a full sentence: just a predicate clause
[17:27] <kirkland> persia: ogra: Riddell: hows "Description: Modular framework for running scripts to generate the /etc/motd"
[17:27] <kirkland> <80 chars
[17:27] <Riddell> works for me
[17:27] <ogra> Modular framework for to generate the message of the day dynamically ?
[17:27] <ogra> -for
[17:28] <kirkland> ogra: that's better
[17:28] <persia> kirkland: Yes, that would be the typical pattern
[17:29] <bluefoxicy> so did anyone make the consideration that I might actually not like running f-spot?
[17:29]  * persia wonders how this got through REVU, and decides that the REVUers need training again
[17:29] <bluefoxicy> like, back in the day, GNOME was like, "Hey you just plugged in a card containing pictures.  Want to import photos?"
[17:29] <bluefoxicy> these days it just opens f-spot.
[17:30] <calc> yea, i have to constantly kill that stupid app
[17:30] <bluefoxicy> so I went to system->preferences->removable media and unchecked everything, particularly "Import digital photographs when connected" for cameras
[17:30] <bluefoxicy> it still does it.
[17:30] <persia> bluefoxicy: changelogs are the key to understanding history.
[17:30] <calc> i just want to cp -a the files over
[17:30] <bluefoxicy> so I deleted `which f-spot`
[17:30] <persia> Is there a bug for this?
[17:30] <bluefoxicy> it says it's attempting to open the card for a few seconds now, but doesn't run fspot
[17:30] <bluefoxicy> what the hell?
[17:30] <bluefoxicy> i don't know
[17:31] <calc> bluefoxicy: hmm it shouldn't be importing photos if you turn it off, i forgot to just go in and do that myself
[17:31] <calc> bluefoxicy: if it doesn't care its not checked then that would be a bug
[17:31] <bluefoxicy> calc:  can you try to reproduce?
[17:31] <calc> bluefoxicy: yea i can go get my camera card and see what it does
[17:31] <calc> istr my camera card not doing it but a friends starting f-spot
[17:31] <bluefoxicy> istr?
[17:32] <calc> i seem to recall
[17:32] <calc> ok got my card going to see what it does
[17:33]  * ogra doesnt think gnome-volume-manager is particulary useful nowadays since gvfs handles all that 
[17:33] <_MMA_> bluefoxicy: You also have to disable it through Nautilus now.
[17:33] <kirkland> ogra: patch attached to https://bugs.launchpad.net/ubuntu/+bug/260441
[17:33] <ogra> right, what _MMA_ said
[17:33] <bluefoxicy> _MMA_:  okay, wait, there's TWO places to disable the same feature?
[17:33] <kirkland> ogra: any chance I could talk you into sponsoring?
[17:33] <calc> _MMA_: so much for gnome being easy to use, lol
[17:33] <kirkland> ogra: since it was your complaint?  :-) :-)
[17:33] <bluefoxicy> and they're not linked
[17:33] <_MMA_> Edit->Prefs-> Media tab
[17:33]  * calc thinks that would be HIG non-compliant
[17:33] <bluefoxicy> I'm going to have to call that a bug
[17:33] <ogra> its a half done transition
[17:34] <ogra> between gnome-vfs and gvfs
[17:34] <bluefoxicy> lol
[17:34] <bluefoxicy> I love the options for software
[17:34] <bluefoxicy> "Ask what to do" "Open autorun prompt" (the second, I assume, asks you what to do... since it's called a "prompt")
[17:34] <\sh> ogra: are you coming to froscon?
[17:34] <ogra> \sh, froscon ?
[17:35] <\sh> ogra: free and opensource conference, st. augustin ;)
[17:35] <ogra> kirkland, looking, i will have to wait until i can grab the source pkg off the archive (i'm lazy) but will do the sponsoring then
[17:36] <kirkland> ogra: cool dude, thanks.
[17:36] <\sh> ogra: it starts tomorrow morning ;) so I wonder if you want to visit your old area ;) and have a nice o'reilly beer ,)
[17:37] <ogra> \sh, hmm i saw the blog post from lydia ... thogh i thought st. augustin is somewhere in austria :P
[17:37] <\sh> ogra: lol...between bonn and cgn yeah austria rotfl
[17:38] <soren> 7win 7
[17:38] <soren> gah...
[17:39] <calc> more fun stuff on my system
[17:40] <kirkland> soren: are you playing a slot machine?
[17:40] <calc> when i plugged my sd card in it froze my system to where sysrq couldn't even reboot it
[17:40] <calc> i had to hard reset it with power
[17:40] <soren> kirkland: It feels that way.
[17:42] <slangasek> cjwatson: hrm, looks like a wayward copy of wubi...
[17:43] <slangasek> cjwatson: duplication when running pam-auth-update> which version do you have installed?  This should be fixed in the latest
[17:43] <soren> slangasek: You never got back to me on the Nagios promotion thing in Hardy, did you?
[17:44] <soren> I sent it on the Friday where you were probably leaving for Debconf, so timing is not on my side.
[17:44] <slangasek> (unless, that is, I broke it again)
[17:45] <slangasek> soren: no, I had not; though today looks promising, if I don't find that I have another pam fire I didn't notice from yesterday
[17:47] <tseliot> mvo: is there a way to do something like markReinstall() with python-apt?
[17:47] <soren> slangasek: Cool, thanks.
[17:52] <mvo> tseliot: yes, give me a sec
[17:52] <cjwatson> slangasek: 1.0.1-3ubuntu3
[17:53] <cjwatson> slangasek: I filed a bug about it with the details
[17:53] <slangasek> cjwatson: ok; I know which commit broke it then, I'll have a fixed package away shortly
[17:53] <cjwatson> slangasek: great, thanks
[17:56] <mvo> tseliot: cache._depcache.SetReInstall(pkg._pkg)
[17:57] <tseliot> mvo: does cache stand for apt_pkg.GetCache or apt.Cache ?
[17:57] <NCommander> persia, I am posting about the key team policy, I got no more responses w.r.t. to needing changes, so I'm calling the issue closed and resolved
[18:03] <mvo> tseliot: apt.Cache
[18:03] <tseliot> mvo: ok, thanks a lot
[18:03] <mvo> cheers
[18:08] <slangasek> cjwatson: hmm, when this /first/ happened to you, what version of libpam-runtime did you have installed?  I actually can't reproduce the problem, I wonder if I've already fixed it for everything but an upgrade case that I can't pinpoint
[18:14] <tseliot> mvo: that method complains that it requires 2 arguments: self.cacheUi._depcache.SetReInstall(pkg._pkg) --> TypeError: function takes exactly 2 arguments (1 given)
[18:15] <cjwatson> slangasek: same
[18:15] <mvo> tseliot: oh, sorry. please add a "True" if you want to reinstlal it and a "false" if you don't wnat to
[18:15] <slangasek> cjwatson: hmm, ok.  still digging.
[18:15] <cjwatson> slangasek: I did upgrade pam and ecryptfs-utils at different times; there was one pam upgrade where I got the "manage me?" question and a multiselect profiles question with just pam_unix, and then upgraded ecryptfs-utils later
[18:16] <slangasek> I mean, I'm /pretty/ sure I know how to fix it, but I don't understand how to reproduce it to verify that it's fixed
[18:17] <cjwatson> did the tarball I sent not manage to reproduce it, then?
[18:17] <slangasek> oh, I should scroll down in the bug :P
[18:18] <tseliot> mvo: ah, ok, it makes sense now, thanks again
[18:19] <slangasek> kirkland: /usr/share/pam-configs/ecryptfs-utils doesn't need to be installed executable, fwiw
[18:20] <cjwatson> yeah, kirkland said that to me earlier :)
[18:20] <slangasek> heh :)
[18:21] <slangasek> aha, I have to run with --package to get it to happen
[18:21] <slangasek> because if the prompt is shown, debconf helpfully collapses the answers, right
[18:24] <slangasek> ok, will take me a little longer than I thought to fix, then
[18:26] <slangasek> ah, heh; there we go, my filter depends on being able to uniquely sort the profiles by priority :/
[18:27] <kirkland> slangasek: yeah, i'll fix that in the next upload
[18:35] <slangasek> cjwatson: fix uploaded; though I've once again failed to do the .changes generation on intrepid instead of sid, so I'll follow up to close the bug by hand
[18:37] <cjwatson> heh, ok
[18:37] <cjwatson> thanks
[18:37] <slangasek> oh; no, I also ran dput on sid; so I have another chance to get the .changes right :-P
[18:47] <kirkland> slangasek: patch available for https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/260458
[18:48] <slangasek> kirkland: 644 please, not 444
[18:48] <kirkland> slangasek: really?
[18:48] <kirkland> slangasek: why?
[18:48] <slangasek> because those are the standard perms for all files
[18:49] <kirkland> slangasek: hmm, okay.  i just couldn't see any case where that file should be rewritten
[18:49] <slangasek> only in cases of emergency, really :)
[18:51] <kirkland> slangasek: whatever you say, boss.  updated patch posted to that bug

[19:31] <asac> cody-somerville: ok you are here
[19:31]  * cody-somerville nods.
[19:31] <asac> cody-somerville: i havent used nm 0.6 for a while. but connections that dont require secrets should work before login if you dont have anything in interfaces
[19:32] <asac> cody-somerville: if that doesnt work, take the NM 0.7 from ~network-manager PPA
[19:32] <asac> (which is much cooler anyway)
[19:32] <cody-somerville> hehe
[19:32] <cody-somerville> 0.7 won't beak my vpn stuff will it? :-]
[19:32] <asac> cody-somerville: which kind of vpn?
[19:33] <cody-somerville> OpenVPN
[19:33] <asac> i got mixed feedback on openvpn
[19:33]  * cody-somerville kinda needs it to connect to the Lexington office.
[19:34] <asac> cody-somerville: you could try ;) ... just take care that you have the upgraded packages still in apt-cache so you can downgrade
[19:34]  * cody-somerville nods. :-]
[19:35] <asac> cody-somerville: ok good to know that lexington has openvpn ;) ... i have to bug them to give me a test account then i guess ;)
[19:35] <asac> (in case it doesnt work for you of course)
[19:35] <cody-somerville> asac, Sounds good! :] thanks.
[19:35] <asac> cody-somerville: let me know
[19:35]  * cody-somerville nods.
[19:57] <asac> kees: how do you bring up eth0.3 ... for me just adding your interfaces doesnt work ;)
[20:01] <kees> asac: you'll need a tagged VLAN, and the vlan tools installed.
[20:01] <slangasek> mmm, tagged flan
[20:01] <ogra> heh
[20:02] <kees> asac: /etc/network/if-pre-up.d/vlan does the parsing and setup
[20:26] <emgent> hello
[20:29] <asac> kees: and nothing of this shows up in hal?
[20:29] <asac> (before or while using?)
[20:30] <asac> kees: that script is in if-_pre_ ... does that mean its run before a particular interface comes up?
[20:30] <asac> is that interface a "normal" one?
[20:48] <hwilde> http://pastebin.com/m57dd15fe
[20:48] <hwilde> are my permissions supposed to be ?rwsrwsrwt
[20:48] <hwilde> and ownership some random user 4294967295
[20:49] <ion_> Filesystem corruption?
[20:49] <slangasek> that's not random, that's (unsigned int)(int)-1
[20:50] <slangasek> but it does look like filesystem corruption, or a kernel bug
[20:50] <hwilde> can I just chown it and um
[20:50] <hwilde> or fsck time
[20:50] <slangasek> fsck first
[20:50] <slangasek> well, depending on what you have, mount read-only and take a full copy of the fs first
[20:50] <slangasek> then fsck
[20:52] <hwilde> I have it mounted in a flashcard reader
[20:53] <hwilde> what's the best way to copy the whole fs
[20:53] <hwilde> cp -a ?
[20:55] <hwilde> cp -apR ?
[20:56] <hwilde> man.. it's just scrolling cp: `/flashcard/etc/readahead/boot' has unknown file type
[20:56] <hwilde> i'm not sure this backup is going to be worth much :)
[20:59] <hwilde> ok, full copy acquired
[20:59] <hwilde> or as much as possible
[21:01] <hwilde> won't umount tho :(
[21:02] <hwilde> fsck says it's clean
[21:03] <hwilde> won't let me change ownership or permissions tho
[21:04] <hwilde> ion_, slangasek, hosed ?
[21:12] <hwilde> Inode 67220 has compression flag set on filesystem without compression support.  Clear? yes
[21:12] <hwilde> Inode 67218 has INDEX_FL flag set but is not a directory.
[21:12] <hwilde> nasty errors
[21:12] <hwilde> yay e2fsck
[21:17] <hwilde> Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 2698259 bytes) in /home/pastebin/lib/pastebin/spamfilter.class.php on line 92
[21:17] <hwilde> lollll
[21:17] <hwilde> I guess I can't pastebin the errors for you :)
[21:19] <hwilde> hey ubuntu pastebin has more memory  http://paste.ubuntu.com/39766/
[21:20] <ion_> Or perhaps it’s just implemented more sanely. :-)
[21:42] <kees> asac: hal> correct -- these never show up because the hel enumerator for network devices requires that there is a physical id associated with it (see my reverted patch to hal during hardy when I was trying to get bridge interfaces visible to hal)
[21:42] <kees> asac: when ifupdown calls "ifup" on the interface named eth0.N, all the stuff in if-pre-up.d/* is called on it, then if-up.d/* etc etc
[21:43] <kees> asac: that's the way ifupdown is designed to work -- there are handlers for every type of interface in there.
[21:43] <kees> asac: I don't know what "normal" means :)
[22:09] <slangasek> hwilde: so in conclusion, fsck thought it was corrupt enough that it removed the three directories in question?
[22:11] <solj> anyone know where i can get some help with this bug: https://bugs.launchpad.net/ubuntu/+source/xen-meta/+bug/215558
[22:11] <solj> it's been open with no response for months
[23:38] <dragonlord222> jello somebody there
[23:38] <cody-somerville> Yes
[23:41] <dragonlord222> what are you guys doing
[23:44] <cody-somerville> I'm coding
[23:44] <dragonlord222> jeah and that is?