[01:01] <lifeless> slangasek: EUNKNOWN for now
[01:01] <lifeless> slangasek: I'll track it
[01:04] <jono> james_w, ping?
[01:04] <james_w> hey jono
[01:05] <jono> james_w, hey, is USB Creator pretty buggy right now? every time I plug my USB stick in it says the device needs to be formatted, and I have formatted it a bunch of times already
[01:05] <jono> when click the Format button it doesnt format it
[01:06] <james_w> you formatted it as fat32, or something else?
[01:06] <jono> ext3
[01:09] <renatokrause> Good night,
[01:09] <renatokrause> My name is Renato and I'm Brazilian. I'm a developer for several years I am very interested in contributing to the development of Ubuntu. I wonder if anyone can help me on that interest. It would be very useful some indication of reading. I work with forensics and notice that both in Debian and Ubuntu packages are missing some good for the forensic work.
[01:09] <renatokrause> Thank you very much.
[01:09] <slangasek> lifeless: ok; am keen to not release with such a bug, so please do and let me know :)
[01:09] <slangasek> renatokrause: you may want to have a look at https://wiki.ubuntu.com/ContributeToUbuntu as a starting point
[01:14] <renatokrause> slangasek: I'm part of the Brazilian forum of Ubuntu and perform translations for Brazilian Portuguese through Rosetta. However I would like to contribute to forensic packages for both distributions that use daily: Ubuntu and Debian.
[01:15] <renatokrause> slangasek: I could send someone to the packages that I have just managing to myself?
[01:17] <slangasek> renatokrause: that page includes pointers on getting involved with package maintenance in Ubuntu ("Maintaining Ubuntu")
[01:17] <engla> renatokrause: and for Debian perhaps this can help http://mentors.debian.net/
[01:20] <renatokrause> slangasek, engla: thank very much
[01:52] <lifeless> slangasek: I have another bug to file; a rather more severe one with graphics ;)
[01:53] <lifeless> slangasek: but I just got of a plane, I'll probably gather data and file tomorrow morning
[02:01] <slangasek> lifeless: ok
[02:14] <lifeless> slangasek: suspend resume and colours come back borked; lockups etc.
[02:22] <slangasek> lifeless: is this newly upgraded to karmic?
[02:24] <lifeless> slangasek: no
[02:24] <slangasek> huh
[02:24] <lifeless> oh, also odd flickering of the screen, like th entire image when black for a single grame
[02:24] <lifeless> *frame*
[02:24] <lifeless> slangasek: I've been tracking karmic for a few months
[02:24] <slangasek> I'm not aware of any changes to suspend/resume support recently that should affect that
[02:24] <slangasek> (unless you have a very strange race condition between your video and hdparm)
[02:24] <lifeless> slangasek: I'm assuming its the intel driver update from thursday
[02:25] <slangasek> oh, ok
[03:44] <Darxus> When I delete a package from a ppa, will it eventually let me upload that package again with the same version?
[03:44] <Darxus> Is the problem the time it takes to delete, or some version enforcement?
[03:45] <nixternal> Darxus: it should eventually...didn't think it took that long in the past
[03:45] <Darxus> nixternal: I don't know how long it takes, it never occurred to me to wait at all before.
[03:45] <Darxus> Thanks.
[03:46] <wgrant> Darxus: It will never let you upload the same version again.
[03:46] <Darxus> wgrant: Thanks.
[03:46] <Darxus> That's very unfortunate.
[03:46] <wgrant> And while you can upload an older version eventually, it is strongly discouraged.
[03:46] <wgrant> Why?
[03:46] <Darxus> I'm going to have to rebuild my patched version of the linux package just to match the version dependancies of the linux-meta package :/
[03:46] <wgrant> It's different => it's not the same version => it should have a different version number
[03:46] <Darxus> Not that unfortunate in the grand scheme of things.
[03:47] <Darxus> Yeah, I understand the logic.
[03:47] <Darxus> But I'm also confident nobody has downloaded the broken package.
[03:47] <wgrant> Why does linux-meta have such strict dependencies?
[03:47] <wgrant> Hm, it does seem to. How odd.
[03:47] <Darxus> wgrant: It's just the way the package builds, it requires kernel packages with an exactly matching version.
[03:48] <nixternal> wgrant: didn't it used to?
[03:48] <Darxus> Nah, it makes sense.  That's what it's there for - depending on current versions of related packages.
[03:48] <wgrant> Darxus: Wait, it only depends on the same ABI.
[03:48] <Darxus> Ohhh.
[03:48] <wgrant> Darxus: It doesn't depend on the same revision.
[03:48] <Darxus> Right, thanks.
[03:48] <Darxus> A lot :)
[03:48] <Darxus> I hate waiting for the kernel to rebuild.
[03:48] <wgrant> Darxus: the metapackages (linux, linux-image, linux-image-generic) depend on the precise versions of each other.
[03:49] <Darxus> Makes sense.
[03:49] <wgrant> But linux-image-generic only depends on linux-image-2.6.31-12-generic - no particular version.
[03:49] <Darxus> Right.
[03:49] <Darxus> Also makes sense.
[03:49] <wgrant> nixternal: I don't believe so.
[03:49] <nixternal> I thought it did...though I don't use PPAs much
[03:50]  * wgrant checks the code.
[03:50] <Darxus> Heh.
[03:51] <wgrant> nixternal: It doesn't look like it ever allowed that.
[03:51] <wgrant> And it certainly doesn't now.
[03:52] <Darxus> Sweet!  Dependancies resolved.
[03:52] <wgrant> Great.
[03:52] <Darxus> Hopefully the next linux source package increments the version more than two so I can match it again :/
[03:53] <Darxus> Er, at least two.
[03:53] <Darxus> I suppose I could ask.
[03:53] <wgrant> Why are you using an identical version?
[03:54] <Darxus> Because I'm just creating a patched copy of the linux source package, called linux-bfs.  Just nicer for them to match.
[03:54] <Darxus> I'm adding bfs1 to the abi, and don't mind incrementing that.
[03:54] <wgrant> Ah.
[03:55] <wgrant> As long as you have that in there somewhere.
[03:55]  * jdong wishes the scheduler were pluggable :)
[03:55] <Darxus> wgrant: Well, it's in the source and all binary package names.
[03:55] <Darxus> The renaming was a pain.
[03:55] <wgrant> There's already linux-rt, linux-ports... surely it wasn't that hard?
[03:56] <Darxus> Heh.
[03:56] <Darxus> I haven't looked at linux ports, but linux-rt is just a single image package.  linux builds a bunch.
[03:57] <Darxus> Ah, yeah... doing something with linux-ports-source would've been a lot easier, but less thorough.
[03:59] <Darxus> And I have delusions of this patch eventually getting applied to the linux source package in main :)
[04:47] <lifeless> slangasek: its reproducible
[04:47] <lifeless> slangasek: even screen-cleanup isn't running.
[04:47] <lifeless> slangasek: is there a log that will show what script is blocked? [I suspect I know... - its the full disc encryption task being a muppet]
[09:31] <slangasek> lifeless: no, early boot logging is hard; but if you can post your fstab and your crypttab, we might be able to make sense of that (and link it to one of the existing bug reports)
[10:09] <hyperair> hmm it would be nice if the /var/run/reboot-required file contained the name of the package which requested its reboot
[11:03] <dvoid> anyone here working on the new software store system ?
[11:15] <Darxus> Wow, the kernel bug list is scary:  http://qa.ubuntu.com/reports/ogasawara/kernel-buglist.html
[11:15] <Darxus> I guess that makes it easier to understand the size of the diff against upstream.
[11:18] <dvoid> im trying to find some one to contact about the appstore system?
[11:18] <wgrant> dvoid: Just ask here, and someone will answer if they know.
[11:18] <dvoid> ubuntus webpage lacks email addresses :(
[11:18] <wgrant> Personal email is very probably not a useful medium;
[11:18] <dvoid> well , does anyone know who do contact about commercial software in the appstore?
[11:19] <dvoid> im a developer and i want my software in there when its ready
[11:22] <Darxus> Is appstore any more than a rumour?
[11:24] <Nafallo> are you referring to 'ubuntu software center' by any chance?
[11:24] <dvoid> yes yes
[11:25] <dvoid> theres talk about support for commercial software in the future
[11:25] <Darxus> This is it:  https://wiki.ubuntu.com/AppCenter
[11:25] <dvoid> m
[11:25] <Darxus> It got renamed Software Center, yes.
[11:25] <dvoid> ;)
[11:25] <Darxus> "in version 3, it will offer commercial software."
[11:26] <Darxus> Version 1 starts in Karmic.
[11:26] <Darxus> dvoid: You may have a while to wait.
[11:26] <dvoid> yea
[11:27] <Darxus> dvoid: At the top of that page it says it was created by MatthewPaulThomas, which is a link.  Did you try clicking it?
[11:28] <dvoid> yea im about to send an email to him......if i cant find anyone else
[11:28] <Darxus> dvoid: What software are you selling?
[11:29] <dvoid> games
[11:29] <Darxus> Why do you want to find someone else?
[11:30] <dvoid> dont know if he's the man to talk to :)
[11:30] <dvoid> but i guess ill give him a call
[11:31] <Darxus> dvoid: "October 2010: 3. Provide the ability to purchase software from within the Center."
[11:31] <dvoid> bah..like 1year away :S
[11:31] <Darxus> - https://wiki.ubuntu.com/SoftwareCenter#October%202010
[11:32] <Darxus> 06:26AM < Darxus> dvoid: You may have a while to wait.
[11:32] <dvoid> well well, it would be nice to have everything ready the day it launches ;)
[11:34] <Darxus> dvoid: Please read more of that page before contacting anybody.
[11:35] <dvoid> Darxus, yea, doing it
[11:36] <Darxus> Integrating sales into Ubuntu sounds terrible to me.
[11:38] <Darxus> Heh, the version of software center in Karmic (the release currently in beta, being released on the 29th) is 0.5.0.
[11:38] <dvoid> biggest problem i see is...ubuntu only
[11:38] <Darxus> dvoid: What do you mean?
[11:38] <Darxus> Oh, you're only selling to ubuntu users.
[11:38] <Darxus> Yeah, I have no sympathy.
[11:39] <Darxus> dvoid: Why wait for this feature to sell your software?
[11:39] <dvoid> yea..im currently not a ubuntu user. prefer opensuse, so for me a commercial appstore for linux , that only works on ubuntu is kind of a fail
[11:40] <dvoid> Darxus, not saying im going to wait for it. im just saying i want to use it
[11:41] <Darxus> Your perspective is weird.  Nothing is preventing you from selling to users of every distro and operating system and distro right now, and ubuntu is planning to offer you an easier way to sell to their users, and you're complaining.
[11:43] <Darxus> I also honestly don't understand why anybody uses anything but Ubuntu, but variety is clearly healthy, so keep it up.
[11:43] <dvoid> lol
[12:38] <penguin42> has  a change to way non-root partitions are fsck'd and mounted happened in the last few weeks?
[12:43]  * penguin42 has just seen something where a partition wasn't mounted by the time I got to a desktop; but then mounted itself a bit later
[13:06] <taavikko> Does someone think that the following is a bug?: install adblock-plus, launch guest-session, open firefox (in guest-session) firefox opens a tab containing the filter subscriptions...
[13:09] <penguin42> taavikko: Those sound like private data to me
[13:11] <tgpraveen> bug
[13:11] <tgpraveen> file it
[13:11] <taavikko> no it isn't, since on the original user the subscriptions are already made. quest-session just shows the tab, where you could add one
[13:12] <penguin42> oh, it doesn't show the actual subscriptions?
[13:12] <taavikko> nope, just the tab, where you could add one, it's just a usability issue
[13:12] <penguin42> oh
[13:12] <taavikko> sorry, my bad explanation :)
[13:36] <blueyed> How can I log the output of mountall during boot? "exec mountall --daemon $force_fsck $fsck_fix $tmptime &> /tmp/mountall-debug" .. well,  /tmp will not exist..
[13:37] <blueyed> It's a pity that /var/log/boot does not work..
[13:38] <taavikko> tgpraveen: do you still this should be filed? and if yes, against what?
[13:41] <tgpraveen> taavikko: yeah if personal data is not revealed ie the usr's subscriptions then don't file a bug
[13:41] <taavikko> ok, thanks. still a bit of usability issue remains..
[14:05] <cjwatson> blueyed: my usual trick is to observe that /dev/.initramfs/ is writable
[14:08] <blueyed> cjwatson: thanks. do you think that my redirect mentioned above might work then, or could it break mountall altogether?
[14:19] <cjwatson> blueyed: it should work but you have a bashism
[14:19] <cjwatson> &> won't work here
[14:19] <blueyed> ah, ok, thanks!
[14:19] <cjwatson> you need >/dev/.initramfs/mountall-debug 2>&1
[14:20] <ion> also add --debug
[14:22]  * penguin42 wonders if it's mountall which was responsible for not mounting my other partition
[14:22] <blueyed> ion: That might help, yes. Thanks. Hopefully I will have logs the next time.
[14:22] <blueyed> penguin42: likely
[14:23] <penguin42> blueeyed: Is there anything that documents it ?
[14:23] <penguin42> ah yes I'm seeing this  https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/439604
[14:27] <ion> The screen is blank for 15–20 seconds between usplash disappearing and xsplash appearing on my quite new laptop. I wonder what can be done about it?
[14:28] <cjwatson> ion: yes, I commented on that in at least one bug somewhere - gdm seems to be scratching its nose for those 15-20 seconds rather than starting X
[14:29] <cjwatson> ion: either we figure out why gdm is being so inefficient (or maybe sreadahead is eating all the I/O or something?), or we move the emission of the starting-dm event to inside gdm itself rather than in its upstart job
[14:29] <penguin42> the startup scripts for the X session are quite large and complex , but 15seconds is a bit heavy
[14:29] <cjwatson> ion: at the moment there's no way to get rid of the blank screen there entirely, but we can shrink the window
[14:29] <ion> cjwatson: That happens with sreadahead disabled as well. Incidentally, disabling sreadahead makes my system boot 5.5 seconds faster.
[14:29] <cjwatson> penguin42: the X session starts after the X server
[14:30] <cjwatson> so that's not really relevant I think
[14:30] <cjwatson> there's quite a large gap here before the X server even starts
[14:31] <ion> (I mentioned the sreadahead slowdown in bug #432089.)
[17:30] <chrisccoulson> is anyone here having difficulty connecting to upload.ubuntu.com?
[17:31] <james_w> yes
[17:31] <james_w> ping is ok, but ftp not it seems
[17:31] <chrisccoulson> ah, so it's not just me then:)
[17:32] <chrisccoulson> thanks!
[17:32] <james_w> well, I tested when you asked
[17:32] <elmo> try now
[17:32] <chrisccoulson> elmo - yup, working now:)
[18:19] <Darxus> There was a bug reported today (now resolved), and I subscribed the guy who recently merged the package against which the bug was reported.  Was it appropriate of me to subscribe him to the bug?
[18:21] <crypt-0> Darxus, im filing my crypto bug
[18:22] <Darxus> crypt-0: Do I know what you're talking about?
[18:23] <crypt-0> alt nick : dave---
[18:23] <crypt-0> i want to improve the default crypto installer
[18:23] <Darxus> Oh, right.
[18:23] <Darxus> Cool.
[18:24] <Darxus> Gimme the number when it's submitted.
[18:24] <Darxus> (Just so I can subscribe.)
[18:24] <crypt-0> the old cryptsetup can only hash passwords with SHA1, which is belied to be quite insecure
[18:25] <crypt-0> the new one , will be able to hash with any hash supported by libgcrypt
[18:25] <Darxus> Cool.
[18:25] <crypt-0> such as SHA256, SHA512, and Whirlpool
[18:26] <crypt-0> it is still a release candidate, but i have tested it THOROUGHLY on Juanty
[18:26] <crypt-0> also,
[18:26] <Darxus> Right, I was going to ask to confirm you were the guy who wanted something important replaced with a release candidate :)
[18:27] <crypt-0>     * Adds luksSuspend (freeze device and wipe key) and luksResume (with provided passphrase).
[18:27] <crypt-0>     luksSuspend wipe encryption key in kernel memory and set device to suspend (blocking all IO) state. This option can be used for situations when you need temporary wipe encryption key (like suspend to RAM etc.) Please read man page for more information.
[18:28] <crypt-0> Darxus, yes, but if it is well tested by the dev team , it should be no problem
[18:29] <crypt-0> as i mentioned, if it gets "mainstreamed" into ubuntu it wont be a Release Candidate for long
[18:30] <Darxus> Hehe, yes, I remember.
[18:30] <crypt-0> So you will not include a release candidate in the repos?
[18:31] <Darxus> I have no say.  And I won't suggest that it be refused.
[18:31] <crypt-0> i think the potential bugs highly outweigh the the usage of SHA1
[18:32] <Darxus> I think that wording was poor.
[18:32] <crypt-0> What should i file it under?
[18:32] <Darxus> I'm not arguing with you on the appropriateness, just pointing out that it's a little scary.
[18:32] <Darxus> I don't know.
[18:32] <Darxus> Does it apply to more than one package?
[18:32] <crypt-0> [bugs ] as in it crashes or fails to do something non-critical
[18:33] <crypt-0> Darxus, No, just cryptsetup, unless you have cryptsetup packaged somehow into more than one package
[18:34] <crypt-0> a recent version of  libgcrypt is recommended, but i assume that has already been upgraded
[18:35] <crypt-0> (and a recent kernel, as recent (or a little older) than Juanty's kernel)
[18:35] <Darxus> libgcrypt11 1.4.4-2ubuntu2
[18:35] <crypt-0> but Jaunty, and karmic are more than recent enough, so that didnt even need to be mentioned :)
[18:35] <Darxus> Kernel 2.6.31
[18:35] <crypt-0> yes i know
[18:36] <Darxus> I suspect just filing it against the cryptsetup package would be good.
[18:37] <crypt-0> can you give me a url to it
[18:38] <crypt-0> i dont file bugs often
[18:38] <crypt-0> i usually dump the app when it segfualts and submit it
[18:38] <crypt-0> or run strace on it and gz the the results of it crashing
[18:39] <Darxus> Run: apport-cli cryptsetup
[18:39] <Darxus> Bug reporting tool.
[18:40] <crypt-0>  suspends active device (all IO operations are frozen) and wipes encryption key from kernel. Kernel  version
[18:40] <crypt-0>               2.6.19 or later is required.
[18:40] <crypt-0> thats the newest required kernel to do everything
[18:40] <crypt-0> Juanty is already past that
[18:41] <crypt-0> Darxus, in other words
[18:42] <crypt-0> people can use the suspend and hibernate options on thier encrypted laptops with no fear of cold boot, however they will need the passphrase upon wakeup
[18:43] <Darxus> Right.
[18:43] <crypt-0> Red Hat (or maybe some other distro) , I believe has already done this according to the author of dm-crypt
[18:43] <crypt-0> more than 6 months ago
[18:44] <crypt-0> even if i cant get the cryptsetup upgraded, i can at least repleace the ugly defualts
[18:45] <crypt-0> Darxus, does the karmic crypto installer have a write urandom to disk, and or a wipe option before encryptig?
[18:46] <crypt-0> (however the urandom should be done *after* encryption)
[18:46] <Darxus> No idea.
[18:46] <Darxus> I'm really not who you need to convince.
[18:50] <crypt-0> cant figure out how to file a bug
[18:50] <crypt-0> $ apport-cli cryptsetup
[18:50] <crypt-0> No pending crash reports. Try --help for more informatio
[18:51] <crypt-0> because ther are no crashes , or bugs that i have found
[18:51] <crypt-0> and ive reviewed the code'
[18:51] <jdong> ubuntu-bug cryptsetup you mean?
[18:52] <Darxus> crypt-0: Yeah, try what jdong said.
[18:52] <Darxus> jdong: Why didn't apport work?
[18:53] <jdong> Darxus: apport only works when something crashes and is caught
[18:54] <Darxus> Weird.
[18:54] <crypt-0> im filing it already
[18:54] <crypt-0> https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+filebug#form-start
[18:54] <Darxus> So there's no way to report a bug from the commandline if there wasn't a crash?
[18:54] <jdong> Darxus: no, ubuntu-bug is the command to do so
[18:55] <jdong> apport has nothing to do with reporting bugs
[18:55] <Darxus> jdong: Doesn't that require a gui?
[18:55] <jdong> Darxus: not that I'm aware of
[18:55] <Darxus> Well, ubuntu-bug is in the apport package.
[18:56] <jdong> Darxus: right, ubuntu-bug forces apport to collect info
[19:06] <mdz> ubuntu-bug is the part of apport which is used for reporting non-crash bugs
[19:13] <dutchie> anybody mind reviewing https://code.edge.launchpad.net/~jshholland/software-center/fix-manpage/+merge/13186?
[19:16] <Darxus> Huh, ubuntu-bug does work without a gui.
[19:19] <crypt-0> https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/448918
[19:25] <crypt-0> wtf
[19:25] <crypt-0> the bug isnt private
[19:25] <crypt-0> Darxus, can you get to : https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/448918
[19:25] <crypt-0> ?
[19:26] <crypt-0> stfu ubottu
[19:27] <tgpraveen> wtf is a private bug
[19:30] <crypt-0> no idea
[19:30] <crypt-0> can anyone get to it
[19:30] <crypt-0> or is the bot just lame?
[19:30] <dutchie> crypt-0: I can't see it
[19:30] <tgpraveen> crypt-0: I can't either
[19:31] <crypt-0> WTF
[19:31] <tgpraveen>                                                                     Not allowed here               Sorry, you don't have permission to access this page.           You are logged in as tgpraveen.
[19:31] <james_w> crypt-0: what are the tags on the bug?
[19:32] <crypt-0> try again
[19:32] <crypt-0> should work now
[19:33] <james_w> crypt-0: it was private as you marked it as a security vulnerability
[19:33] <Darxus> crypt-0: I can see it now, thanks.
[19:33] <crypt-0> insecure Ubuntu crypto installer defaults ( cryptsetup )
[19:33] <crypt-0> yes i know i marked it as a security vulnerability
[19:34] <crypt-0> it must have marked it private by default
[19:36] <Darxus> crypt-0: The "as" in james_w's sentence meant "because".
[19:36] <crypt-0> i dont consider hashing a 256 bit passphrase with SHA1 secure, because #1 SHA1 is broken since 2005, and #2 SHA1 is only 160 bits wich effectiveley makes 256 bit crypto worth 160 (or much less, 2,000 times less according to SHA1 break report)
[19:36] <crypt-0> Darxus, ah ok
[19:36] <Darxus> crypt-0: Nobody here is arguing with you.
[19:37] <crypt-0> yes, ive reached that conclusion
[19:37] <Darxus> Heh.
[19:37] <crypt-0> a lot is missed on IRC, like tone of voice , etc
[19:37] <crypt-0> easy to misunderstand things
[19:37] <Darxus> Yup.
[19:37] <Darxus> Good thing it keeps us out of striking range :)
[19:38] <crypt-0> "marked it as a security vulnerability" <<< assumed he was saying it shouldn't be
[19:38] <crypt-0> and made an ass of myself
[19:38] <crypt-0> brb
[19:38] <crypt-0> :)
[19:39] <Darxus> crypt-0: You might want to add more details on how easy it is to crack SHA1 to that bug.
[19:40] <james_w> I don't think that is needed
[19:42] <Darxus> "Less than six letter password is cracked within minutes"
[19:51] <crypt-0> the break of SHA1 is no secret
[19:52] <crypt-0> also the -15 will make breaking a less than 6 digit password much longer than minutes
[19:52] <crypt-0> * -i 15
[19:53] <crypt-0> the -i 15 will make it take 15 seconds to mount the volume, however it will provide better security to those with weak passwords
[19:54] <crypt-0> you can probably last a few days with -i 600 with a 6 digit pass :P
[19:54] <crypt-0> default it -i 1
[19:55] <crypt-0> it doesn't make it weak password magically "more secure"
[19:56] <crypt-0> but what it does do is increase the amount of CPU power needed to brute force it, making it theoretically "more secure"
[19:57] <crypt-0> it will slow scriptkiddes down a lot
[20:03] <dutchie> anybody mind reviewing https://code.edge.launchpad.net/~jshholland/software-center/fix-manpage/+merge/13186?
[20:04] <Darxus> crypt-0: Yeah that's cool.
[20:05] <Darxus> Although... still, a 6 digit password should take more than a few days on one computer :/
[20:22] <crypt-0> Darxus, "You might want to add more details on how easy it is to crack SHA1 to that bug."
[20:22] <slangasek> ScottK, siretart: emacs23 has now stolen the 'emacs' binary from the emacs22 source package, and made it uninstallable in main.
[20:22] <crypt-0> check it now, i did
[20:24] <Darxus> crypt-0: Cool.
[20:25] <Darxus> crypt-0: Heh, I can see that you've edited the description 8 times.
[20:28] <crypt-0> had to get the bugs out of the bug report
[20:28] <crypt-0> :)
[20:28] <crypt-0> i want to make sure it is cleaned up and proper.
[20:28] <jdong> hahaha :)
[20:31] <crypt-0> 9 now changed a . to a ,
[20:36] <Darxus> Heh.
[20:39] <crypt-0> its all correct now, notice nothing important changed, like the reference command syntax, just grammatical and punctuation errors
[20:42] <crypt-0> https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/448918
[20:47] <dtchen> surely "weak" instead of "insecure"?
[20:47] <dtchen> the latter can apply to just about any context
[20:53] <superm1> slangasek, mind glancing over bug 448981?  i'd like to get this assigned to the right package and if it's easy to fix, fixed for everyone's live media builds tomorrow. basically all of the weekend's builds (10-10 and later) are broke right now
[20:55] <crypt-0> dtchen, should be fixed now
[21:20] <Darxus> I was just going to ask what the "weak" tag was.  Where are such things documented?
[21:20] <dutchie> anybody mind reviewing https://code.edge.launchpad.net/~jshholland/software-center/fix-manpage/+merge/13186?
[21:26] <joaopinto> dutchie, +.TH SOFTWARE-STORE 1 "0.13" "October 2009" <- STORE ?
[21:26] <dutchie> ah, missed that one
[21:27] <dutchie> fixed and pushed
[21:33] <slangasek> superm1: hmm, cody-somerville reported the same yesterday on #ubuntu-release; it sounds like the directory is being taken out from underneath dbus after dbus has started
[21:33] <slangasek> superm1: mountall is probably the right package, let me see if I can pin it down
[21:33] <superm1> slangasek, cool sounds good
[21:39] <mdke> slangasek: sorry to do this *again*, but bug 444853 might require your attention
[21:39] <cjwatson> slangasek: I think that dbus needs to 'start on (local-filesystems and virtual-filesystems)'
[21:39] <cjwatson> since /var/run is the latter
[21:45] <salty-horse> hi. I'd like to file a bug for this problem, but I'm not sure what's the technical name for those terminals: http://ubuntuforums.org/showthread.php?p=8086412
[21:46] <slangasek> cjwatson: right - though I wonder if local-filesystems shouldn't imply virtual?
[21:46] <slangasek> (i.e., is it ever reasonable to send the local-filesystems signal before virtual-filesystems are all up?)
[21:51] <mdke> slangasek: actually having tested the bug in karmic, I can't reproduce it. Perhaps it is because -pl has been removed in your last change to gnome-user-docs (because there are no -pl translations upstream) - no doubt that will get reinstated when -pl translations are added from Launchpad
[21:52] <slangasek> mdke: yes, it's because the package has been removed from karmic and the user has some old repo in sources.list.  when are these translations going to be re-added from Launchpad?  (Why wasn't this done sooner?)
[21:53] <mdke> slangasek: usually, it's done somewhere between non-langpack and langpack translation deadlines
[21:54] <mdke> so that translations done after they are exported aren't lost
[21:54] <slangasek> mdke: ah.  well, the side-effect of not pulling them in earlier is that the package has to go through at least one round of NBS + new queue <shrug>
[21:54] <mdke> hmm
[21:54] <mdke> slangasek: sorry about that
[21:54] <slangasek> (plus whatever bug reports from users complaining that their language has gone missing :)
[21:55] <mdke> slangasek: for the next release I think we should talk about reverting the change whereby the packages are split out into separate languages
[21:55] <slangasek> sure
[21:56] <mdke> for this release, we'll just have to lump it :(
[21:56] <slangasek> yeah, the NBS/NEW isn't a big deal, it's just a bit inefficient - but it sounds like there are enough other reasons to do it that way around (for now)
[21:57] <mdke> what's NBS, incidentally?
[21:59] <mdke> ah, I see it
[21:59] <mdke> yeah, that's a pain
[22:14] <mdke> slangasek: do you think it might be helpful for https://wiki.ubuntu.com/ReleaseChecklist to have a column with "status" so that items can be marked as done when appropriate? For example, the ubuntu-docs ones tend to get done well before release so if you like I can mark them as "done" when that is the case.
[22:34] <cjwatson> slangasek: if virtual filesystems are all guaranteed to be mounted immediately, then I do sort of agree that it might be useful to have some kind of hierarchy, to simplify stuff further up the stack
[22:34] <cjwatson> though probably not a hierarchy any deeper than that, so I don't know how useful that would be
[22:35] <cjwatson> s/mounted/mountable/
[22:36] <lifeless> slangasek: around?