[00:12] <crypt-0> i wish to mount a LUKS volume *before* the root volume is mounted how would i go about this?
[01:00] <lifeless> crypt-0: is the volume for / ?
[01:00] <lifeless> if so cryptsetup has built in support for that
[01:01] <lifeless> its all part of the initramfs scripts
[01:05] <crypt-0> lifeless, no trying to get two-factor auth working
[01:05] <crypt-0> then add a wiki when im done
[01:06] <lifeless> well, you can mount a LUKS partition before /
[01:06] <crypt-0> how so?
[01:06] <lifeless> but you can't mount other volumes before /, not sanely.
[01:06] <lifeless> its built in, just make sure its listed appropriately in crypttab
[01:07] <lifeless> s/mount a LUKS partition/unlock a LUKS partition/
[01:07] <crypt-0> i was thinking of using a keyscript
[01:07] <crypt-0> that cats the keyfile
[01:08] <psusi> storing the password in a file defeats the purpose of the password in the first place
[01:08] <crypt-0> i know, the keydevice shall be a LUKS encrypted device
[01:09] <crypt-0> mounted before the root encrypted LVM
[01:10] <crypt-0> so the password will be to decrypt the keydevice, once decrypted the keyfile can be read and boot can continue
[01:10] <crypt-0> that is my goal
[01:11] <crypt-0> i was looking at a howto  to do two factor with GPG, but GPG lacks PBKDF2
[01:11] <lifeless> uhm
[01:11] <crypt-0> and user passwords tend to be entropy weak
[01:11] <lifeless> LUKS has keyfile support; put the keyfile on a USB device
[01:11] <lifeless> thats something you have
[01:12] <lifeless> I have to go, can chat later
[01:12] <crypt-0> right but i want the keyfile to be encrypted
[01:12] <psusi> and hwo are you going to mount that device?  with a weak password?
[01:13] <crypt-0> *i* am not, but others may yes
[01:13] <psusi> the keyfile IS encrypted, with the password
[01:14] <crypt-0> huh?
[01:14] <psusi> pretty sure that the keyfile contains the real encyption key, which is itself encrypted using the password... possibly multiple times if you have multiple passwords
[01:14] <crypt-0> if i make a key using /dev/random that is plaintext just because i tell LUKS to use it doesn not mean it is encrypted.
[01:15] <psusi> I'm pretty sure that normally luks stores the key in a header it places on the disk... the key is randomly generated when you set up luks.... that key is then encrypted using your password and stored there too
[01:15] <psusi> when you put in your password, it is used to decrypt the real key
[01:16] <psusi> that's why you can change the password without wiping out everything on the disk... because the encryption key is not changed, it's just encrypted using the new password and stored on the disk
[01:16] <crypt-0> if read the LUKS spec, and did mention that
[01:17] <crypt-0> LUKS uses PBKDF2 , which changes your passhprase/keyfile > final decryption key
[01:18] <crypt-0> if Mallory has the password/keyfile she can use it.
[01:18] <psusi> right.... real key gets encrypted using your password(s) and stored on the disk... so even with access to the disk, you can't read the key without the password
[01:21] <crypt-0> yes that is if you consider the disk  a factor.
[01:21] <crimsun> 2/win 39
[01:21] <psusi> huh?
[01:22] <crypt-0> if your disk is stolen and your password is too, the attacker has your data.
[01:22] <psusi> well of course
[01:22] <psusi> so don't write your password down on a sticky note pasted to the bottom of the laptop ;)
[01:23] <crypt-0> yes.... so if someone's laptop gets stolen with a weak password...it is gone
[01:24] <crypt-0> yes.... so if someone's laptop gets stolen with a weak password...but they are using two factor authentication with a USB stick its fine
[01:24] <psusi> encrypting it a second time does not help
[01:24] <psusi> keeping the key on a usb stick helps, provided that it is not also stollen
[01:24] <crypt-0> and if the attacker gets the laptop and the usb stick only the password is required
[01:25] <psusi> yep
[01:25] <crypt-0> that is what i want to set up.
[01:25] <psusi> then store the keyfile on a usb stick, that's pretty straight forward
[01:25] <crypt-0> ans wish to make a wiki so that others may use it
[01:25] <psusi> that's what lifeless ways saying
[01:26] <crypt-0> yes it is, but the keyfile requires no password
[01:26] <psusi> you can make it require one
[01:26] <crypt-0> you know the args?
[01:26] <crypt-0> for cryptsetup
[01:27] <crypt-0> the LUKS header is stored in plaintext
[01:28] <psusi> not offhand, but you should be able to put the key on a usb stick, AND have a password on it
[01:28] <crypt-0> yeah ive looked, but couldnt find a way
[01:34] <psusi> can anyone take a look at bug #534743 and see about applying the fix or at least bumping up the priority?  this NEEDS to get fixed by release and I'm worried that if it doesn't get in for beta 2, it won't get in for release
[01:41] <crypt-0> lifeless, psusi the keyscript to be run http://pastebin.com/M2AhZDVR
[01:43] <sistpoty> doko__: around? just saw that you've taken bug #534459... to my findings, that's gcc miscompiling, but I haven't managed to produce a test-case more minimal than the entire patch package yet :(
[01:44] <doko__> sistpoty: uploaded, build with -fno-stack-protector on sparc. I assume it's kees's task now ;p
[01:45] <sistpoty> doko__: ah, thanks!
[01:45] <sistpoty> doko__: I've got a patch lying around that justs adds an assert for an out of bounds check (local only, the one at the bug report is wrong), which somehow makes the build pass as well, interested?
[01:46] <sistpoty> doko__: however I have retried to build fpc with a fixed patch package, didn't work (however that was a few gcc revisions ago already)
[01:46] <sistpoty> (didn't work due to a bus error later, iirc)
[01:47] <doko__> sistpoty: enotime, sorry. please ask kees. the fpc build on sparc is still running
[01:47] <sistpoty> doko__: kk, kees?
[01:47] <crypt-0> is there a way to enable SMART probing, an update disabled it?
[02:38] <sistpoty> kees: attached the patch to the bug report in question (however in reverted form :()
[03:21] <psusi> cjwatson, ping
[03:39] <psusi> cjwatson, updated OEMRescue wiki page with thoughts for you to read when you're back
[05:25] <un214> apt-get remove plymouth wants to remove e2fsprogs !
[05:26] <ScottK> un214: Don't do that.
[05:27] <un214> plymouth results in a brick
[05:27] <ScottK> Removing it is just a longer path to tears.
[05:27] <ScottK> File bugs and help get it fixed.
[05:27] <un214> ?
[05:28] <ScottK> plymouth isn't just a pretty splash screen.
[05:28] <un214> I was better off when ubuntu didn't try to recognize my video card
[05:28] <ScottK> It also does some important things with system I/O (I don't recall what)
[05:28] <ScottK> So removing it is likely to have side effects eventually.
[05:29] <ScottK> Considering you're using a development release and having problems with the most aggressive area of development in this development cycle, it's not stunning it's problematic for some.
[05:29] <ScottK> Is it really a brick or just on a different vt?
[05:30] <un214> last time I tried it, no display usable (bad driver)
[05:30] <ScottK> How long ago was that?
[05:30] <un214> about a month
[05:31] <un214> usplash had the same problem
[05:31] <ScottK> A lot has been done since then.
[05:32] <un214> well we'll sure find out
[05:36] <un214> well what do you know it actually came up this time
[05:40] <un214> part of the problem is every so often I get a nouveau driver so bad I have to revert to using vgaconsole and VESA. I may end up having to do that anyway (potentially bad hardware).
[05:40] <un214> ^bad nouveau driver
[05:51] <lifeless> persia: hai
[06:30] <persia> lifeless: Hey.
[06:36] <lifeless> persia: hey
[06:36] <lifeless> so
[06:36] <lifeless> we're getting a test machine for lmirror in the dc
[06:36] <lifeless> need some folk with the bandwidth & disk space to test mirroring from it
[06:36] <persia> I'm happy to help with that.
[06:36] <lifeless> \o/
[06:37] <persia> I've about 250-280ms latency, but can saturate the TCP/ACK window, and have plenty of available mirror space.
[06:37] <lifeless> cool
[06:37] <lifeless> whats your actual pipe size?
[06:39] <persia> Technically, 1Gbps, but my fiber is a bit dirty, so I only get ~600Mbps, but my router is old and sad, so I only get ~40Mbps, but the DC is >250ms away, so I really only get ~25.6Mbps
[06:39] <lifeless> hah lol
[06:40] <lifeless> lmirror should saturate your tcp session
[06:40] <lifeless> can you open your tcp buffers more ?
[06:40] <lifeless> tcp profiling is likely to be a significant aspect of tuning it
[06:40] <persia> Probably not usefully, because of my old, sad router.
[06:41] <lifeless> isn't that endpoint determined ?
[06:41] <persia> I'm happy to tweak endpoint stuff, but I'll lead guidance.
[06:41] <persia> s/lead/need/
[06:41] <lifeless> sure
[06:42] <lifeless> to start with, grab lmirror from bzr or a release tarball
[06:42] <persia> Is it in the archives?
[06:42] <lifeless> haha no
[06:42] <persia> k
[06:42] <lifeless> all the deps are, except testrepository which is only in debian atm
[06:42] <lifeless> I did request a sync, but it hasn't been done.
[06:43] <persia> OK.  Source downloaded.
[06:44] <lifeless> apt-get install bzr python-paste python-testresources python-testtools python-testscenarios
[06:45] <lifeless> python -m testtools.run l_mirror.tests.test_suite
[06:45] <persia> Hrm.  Seems I need to fiddle, as some of this isn't in karmic :)
[06:45] <lifeless> will then check that tests pass on your machine
[06:45] <lifeless> oh heh :)
[06:47] <persia> Failed to fetch http://ports.ubuntu.com/ubuntu-ports/pool/universe/p/python-openid/python-openid_2.2.4-1_all.deb  404  Not Found :(
[06:48] <lifeless> wow, what dragged that in?
[06:48] <persia> Dunno.
[06:48] <persia> I had it on my local mirror of archive.u.c, but it's a bug that it's not on ports.
[06:49] <persia> /usr/bin/python: No module named testtools.run
[06:50] <persia> (yes, python-testtools is installed)
[06:51] <lifeless>  what version ?
[06:51] <persia> 0.1~r16-0ubuntu1
[06:51] <lifeless> too old
[06:52] <lifeless> 0.9.2 should be ok
[06:52] <lifeless> [lucid]
[06:52] <lifeless> or you can add the subunit release ppa, which has backports of a few of this sort of thing for karmic etc
[06:53] <persia> lucid version installed fine
[06:53]  * persia plans to upgrade this server soon anyway
[06:53] <persia> What does http://paste.ubuntu.com/409365/ imply I need to upgrade?
[06:54] <lifeless> something
[06:54] <lifeless> add -v to the command
[06:54] <lifeless> you'll get a backtrace in the log, that actually has the problem import
[06:56]  * persia is looking at http://paste.ubuntu.com/409368/
[06:56] <persia> That would indicate that apport is the culprit?
[06:56] <lifeless> ugh
[06:56] <lifeless> no
[06:56] <lifeless> try
[06:57] <lifeless> python -c 'import l_mirror.tests'
[06:57] <persia> ImportError: No module named testresources
[06:57] <lifeless> did you install python-testresources?
[06:57] <persia> I did.
[06:57]  * persia tries again
[06:58] <lifeless> python -c 'import testresources'
[06:58] <lifeless> dpkg -L python-testresources if that fails
[06:59] <persia> Apparently I remembered incorrectly.  Installing python-testresources results in "ImportError: cannot import name memory_transport_stat"
[06:59] <lifeless> thats included in the lmirror source
[06:59] <lifeless> did you grab a tarball or bzr ?
[06:59] <persia> tarball
[07:00] <lifeless> may be a bong tarball :>
[07:00] <lifeless> :<
[07:00]  * lifeless hates on distutils some
[07:00]  * persia mumbles about release management and testing and pulls bzr (slowly)
[07:00] <maco> persia: intentionally?
[07:01] <persia> maco: No, but bzr doesn't seem to kjnow how to get much meyond 20KB/s for me.
[07:01] <lifeless> persia: you've done bzr lp-login ?
[07:02] <persia> lifeless: Yes.  Anyway, with lp:lmirror, `python -c 'import l_mirror.tests'` succeeds cleanly.
[07:03] <lifeless> ok
[07:03] <lifeless> I'll fix
[07:05] <persia> Running `python -m testtools.run l_mirror.tests.test_suite` now gets me "AttributeError: 'module' object has no attribute 'test_logging_resource'".  Do I need -v again, or does this mean something to you?
[07:06] <lifeless> try -v
[07:07] <persia> traceback is still when trying to import apport.  Shall I upgrade that?
[07:07] <lifeless> no
[07:07] <lifeless> its not apport
[07:07] <lifeless> uhm
[07:07] <lifeless> python -c 'import l_mirror.tests.logging_resource'
[07:08] <persia> ImportError: cannot import name TestResourceManager
[07:08] <lifeless> old testresources :<
[07:08] <lifeless> uhm
[07:08] <lifeless> edit that file
[07:08] <lifeless> change TestResourceManager to TestResource
[07:08] <persia> Um, why?  Is there a good reason not to just upgrade?
[07:09] <lifeless> grep for TestResourceManager through tests/*.py
[07:09] <lifeless> l_mirror/tests/*.py
[07:09] <lifeless> persia: may not be packaged; I don't want to yak shave right now.
[07:09] <lifeless> though lucid has 0.2.4 which is what I'm using
[07:10] <lifeless> so it should be packaged just fine
[07:11] <persia> python -c 'import l_mirror.tests.logging_resource' works great with python-testresources (0.2.4-1)
[07:11] <lifeless> ok
[07:11] <lifeless> pop()
[07:12] <persia> AttributeError: 'module' object has no attribute 'test_server'
[07:12] <persia> Err, let me just make sure I have the lucid versions of the list of stuff you asked me to install :)
[07:13] <lifeless> python -c 'import l_mirror.server'
[07:17] <persia> OK.  By installing the lucid versions of everything you asked in the beginning (except bzr), `python -m testtools.run l_mirror.tests.test_suite` runs, but I fail 35 tests.
[07:17] <lifeless> heh
[07:17] <lifeless> what tests fail ?
[07:17] <lifeless> or rather
[07:17] <lifeless> name a couple
[07:17] <persia> python -c 'import l_mirror.server' runs cleanly
[07:18] <persia>  l_mirror.tests.commands.test_mirror.TestCommandCommands.test_mirrors_new l_mirror.tests.commands.test_mirror.TestCommandCommands.test_mirrors_incremental l_mirror.tests.commands.test_mirror.TestCommandCommands.test_error_no_source
[07:19] <persia> The failures all seem to be "AttributeError: 'MemoryServer' object has no attribute 'start_server'" fromself.transport_factory.start_server() atl_mirror/tests/__init__.py:48
[07:20] <lifeless> newer bzr needed
[07:20] <lifeless> but I don't really care if you run the tests or not
[07:20] <lifeless> you should have enough to run it ;)
[07:21] <persia> Good, because bzr gets compiled, and would need a real backport :)
[07:21] <lifeless> err
[07:21] <lifeless> the bzr ppa
[07:21] <lifeless> already has it
[07:22] <persia> 2.1.1-1~bazaar2~karmic ?
[07:22] <lifeless> yes
[07:23] <persia> Doesn't have it for my architecture.
[07:24] <lifeless> oh
[07:24] <lifeless> what arch?
[07:24] <lifeless> sparc?
[07:24] <persia> ppc
[07:24] <lifeless> heh
[07:24] <lifeless> well, you could grab source and respon
[07:24] <lifeless> but frankly, just skip the tests.
[07:24] <persia> So I don't need to backport bzr to do the test you wanted?  Cool.
[07:24] <persia> What do I need to do?
[07:25] <lifeless> symlink lmirror into /usr/local/bin
[07:26] <persia> done
[07:26] <lifeless> cd to a dir somewhere, such as pool/main/libm
[07:26] <lifeless> run lmirror init test
[07:27] <lifeless> and lmirror mirror test /tmp/test
[07:27] <lifeless> if those commands work
[07:27] <lifeless> lmirror serve test
[07:27] <persia> Should pool/main/libm be a current mirror?
[07:27] <lifeless> open a new window
[07:27] <lifeless> persia: doesn't matter; it won't write to the mirror files; it will make a .lmirror directory we'll delete shortly
[07:27] <lifeless> and do lmirror mirror http://127.0.0.1:8080/test /tmp/test2
[07:28] <lifeless> if that works, then we can be pretty sure we're prepped to do some tests with jpds when his test archive server is up and running
[07:31] <lifeless> persia: how did that go ?
[07:32] <lifeless> you can check ~/.cache/lmirror/log to see what went on/is happening
[07:32] <lifeless> or add -v (or -vv etc) to the command line
[07:32] <persia> Just waiting for the result of lmirror mirror http://127.0.0.1:8080/test /tmp/test2
[07:33] <crypt-0> lifeless, if while in initrd you mount a volume before mounting / and unmount it before mounting / is that safe?
[07:33] <persia> ArneGoetje: When you're around, I'd like to chat about search engines and language-pack-ja
[07:33] <lifeless> crypt-0: probably
[07:33] <persia> lifeless: How long should it take for this last command to return?
[07:35] <lifeless> persia: it should have taken no longer than the local disk mirror
[07:35] <lifeless> can you du -sh /tmp/test ?
[07:35] <persia> 24K
[07:35] <lifeless> not test2
[07:35] <lifeless> /tmp/test
[07:35] <lifeless> the one that worked
[07:36] <persia> Both are the same.
[07:36] <lifeless> interesting
[07:36] <lifeless> does /tmp/test contain the libm content ?
[07:37] <persia> It contains nothing at all.
[07:37] <persia> But the directory in which I ran the tests also contained nothing.
[07:37] <lifeless> oh
[07:37] <lifeless> heh
[07:37] <lifeless> well that would make it fast :P
[07:37] <lifeless> so, it seems to be hung yeah ?
[07:37] <persia> Indeed.
[07:38] <lifeless> can you strace the client ?
[07:38] <persia> I don't know how to do that interactively.  I can kill it, and run again under strace.  Would that output interest you?
[07:39] <lifeless> use ps to find the process
[07:39] <lifeless> then strace -p PID
[07:40] <persia> spinning on "recv(4, "", 23, 0)                      = 0"
[07:40] <lifeless> ok
[07:40] <lifeless> its expecting more content, but not seeing it
[07:40] <lifeless> which is interesting
[07:40] <lifeless> I can probably reproduce this
[07:41] <lifeless> could you add a file to your source dir
[07:41] <lifeless> if its not a live mirror
[07:41] <lifeless> and run lmirror start-change
[07:41] <lifeless> and run lmirror start-change test
[07:41] <lifeless> and then run lmirror finish-change test
[07:42] <lifeless> and then repeat the lmirror mirror http://127.0.0.1:8080/test /tmp/test2
[07:42] <lifeless> I want to be sure its an empty-mirror bug, not a platform networking bug
[07:45] <lifeless> persia: same symptoms ?
[07:46] <persia> Yep.
[07:47] <lifeless> has it written the new file to disk ?
[07:47] <persia> I do get a .lmirrortemp file though, so it's trying to do soemthing.
[07:47] <lifeless> ok
[07:47] <persia> The .lmirrortempfile is 0-byte
[07:47] <lifeless> is the new file you made 0-byte ?
[07:47] <persia> the source is 15 byte
[07:47] <lifeless> and strace shows it spinnnig on recv ?
[07:48] <persia> Yes.
[07:48] <persia> "recv(4, "", 15, 0)                      = 0"
[07:48] <lifeless> any error on the server terminal ?
[07:49] <lifeless> or in ~/.cache/lmirror/log ?
[07:49] <persia> None
[07:49] <persia> ~/.cache/lmirror/log has "2010-04-05 06:45:07Z: Writing file 'mirror.this'"
[07:49] <persia> (which is the name of the test file)
[07:51] <lifeless> ok
[07:51] <lifeless> I have to do some stuff here
[07:51] <lifeless> if you're up for it, might try to debug this more later
[07:51] <lifeless> e.g. get a tcpdump trace of the request
[07:52] <lifeless> btw do you have a http proxy configured ?
[07:52] <persia> I'm happy to run stuff as you need.  I don't use a proxy for that server
[07:52] <lifeless> for now, you can delete the test file, the .lmirror dir in your test area, and /tmp/test and /tmp/test2
[07:52] <persia> (it has mirrors of Ubuntu and Debian, and any sane proxy would be useless most of the time)
[07:52] <lifeless> persia: does it have http_proxy or similar configured ?
[07:53] <persia> Not intentionally.  Is there something I should check?
[07:54] <persia> by "test file" do you mean some file named "test", or my "mirror.this" file used for testing?
[07:54] <lifeless> mirror.this
[07:56] <persia> OK.  All deleted.  I likely still have the "test" mirror configured in lmirror, but that can just sit there until it works.
[07:58] <lifeless> nope, you've deleted the config if you deleted the things I said you could ;)
[09:18] <ArneGoetje> persia: I'm only only for a short time now... public holiday here today... what's up?
[09:19] <persia> ArneGoetje: based on bug #526411 , we have the impression that we need to set the search providers for firefox in the langpacks, and if you have a pointer to a HOWTO or similar, we'd like to use that.
[09:20] <persia> ArneGoetje: Any guideance would be input to discussion with yahoo.jp and mozilla.jp, as the en-US default is currently mostly useless.
[09:21] <ArneGoetje> persia: hum... I'm not sure about the sort ordering... but the localized searh engines are handled in langpack-o-matic, i.e. they are static there.
[09:21] <persia> ArneGoetje: So what would be the best way to send a suggested order for the ubuntu-ja team?  Just a bug, and subscribe you, or something more complicated?
[09:22] <ArneGoetje> persia: need to talk with asac first. I'm not sure what's the procedure for the localized entries.
[09:23] <persia> I hear he won't be around until Wednesday or so.  Does it have to be him, or will any member of the mozillateam work?
[09:23] <ArneGoetje> persia: can ask other members of the mozillateam... though I don't know if they know the answer...
[09:24] <persia> ArneGoetje: Just to make sure I understand: you need information on how it is supposed to work, and then we'd file a bug subscribing you to make it work that way?
[09:24] <ArneGoetje> persia: yup
[09:25] <persia> ArneGoetje: Thanks!  I'll go hunt up an answer.
[09:25] <ArneGoetje> persia: thanks a lot! Please file the bug against the langpack-o-matic project.
[09:26] <persia> Will do.
[12:22] <intick> hi all (english is the official language here right ) ?
[12:22] <mdke> intick:
[12:22] <mdke> intick: yes
[12:23] <mdke> is it acceptable practice during the freeze to upload packages which are not essential for the beta on the basis that they will be processed after the freeze ends?
[12:23] <intick> ok, first sorry for my poor english, i would like to know where can i share my bug experience with developpers of nautilus ? i have some comments to do
[12:25] <nailora> could someone un-private this bug (of course only if applicable) https://bugs.launchpad.net/bugs/549655
[12:27] <nailora> ^^ is that ubottus way of saying this report is private?
[12:28] <mdke> intick: this is probably the place to start: http://live.gnome.org/Nautilus
[12:29] <intick> thx mate that's what i'm looking for
[12:29] <intick> cu
[12:31] <nigelb> mdke, we are encouraged not to upload nonessential stuff during beta freeze
[12:31] <persia> Um, it's more complicated that that, actually.
[12:32] <persia> If a package appears in no images, it's fairly safe to upload.
[12:32] <nigelb> i.e. universe?
[12:32] <persia> Well, no.
[12:32] <persia> Because many images draw from universe.
[12:32] <nigelb> oh like... stuff in universe for ubuntu might in images for kubuntu and the likes?
[12:33] <persia> If a package has an update and it is known in advance that there will be no need to change the package during the freeze, it's safe to upload (but will be held pending freeze lift)
[12:33] <mdke> well, my package does appear in an image, but if it isn't approved, then the upload shouldn't compromise an image, afaics
[12:33] <persia> nigelb: No.  The "universe flavours" vary by release.  For lucid, they are xubuntu and ubuntustudio.
[12:33] <mdke> it's just a question of whether it will annoy the release managers
[12:33] <mdke> (to have it pending)
[12:34] <persia> mdke: My personal suspicion is that we'll go into pre-release freeze once beta2 releases, so I would expect every upload from this point to require manual approval.
[12:34] <nigelb> it does, it does
[12:34] <nigelb> every upload needs release ack
[12:34] <mdke> persia: are you sure? That's not what the release schedule says
[12:34] <persia> The risk with having it pending is that if it happens to end up having a milestone-critical bug, it's awkward to do an update that isn't the non-milestone targeted update.
[12:35] <persia> mdke: I'm not sure at all.  I'm just guessing.
[12:35] <mdke> hmm.
[12:36] <mdke> I'll wait until beta release and upload then I guess
[12:36] <persia> That's safer for packages in images.
[12:36] <nigelb> mdke, /me misread.  Only during last week needs ack from release for all uploads :)
[12:37] <mdke> persia, nigelb: thanks for the input
[12:43] <ScottK> persia: I don't think we're going to stay in pre-release freeze after the beta is out.
[12:43] <ScottK> It's fine to upload stuff now and if there's time to review it and it appears low risk, it'll get in.
[12:44] <persia> ScottK: Cool.  So pre-release will just be from RC-freeze?
[12:44] <ScottK> persia: AFAIK, yes.
[12:46] <persia> That makes sense.  I thought it might be more stringent because of the specialness of this cycle.
[12:54] <mdke> ScottK: you think it's ok to upload a package now even if it appears on a cd? (I'm not bothered about whether it is approved before or after beta release, but it would be convenient to me to get the upload off my plate now)
[12:54] <ScottK> mdke: Yes.
[12:55] <mdke> ok, thanks
[13:13] <carnil> Hi, we in Debian Perl Group have a FTBFS on libgk2-perl (1:1.221-5) building against libgtk2-dev 2.20.0-2. If possible, could someone of you please rebuild libgtk2-perl in lucid against the gtk2.0 version there and check if it fails too?
[13:25] <geser> carnil: FTBFS in my lucid pbuilder. It fails at some tests. (AMD64; libgtk2-perl: 1:1.221-4ubuntu1; libgtk2.0-dev: 2.20.0-0ubuntu3)
[13:34] <carnil> geser: is one of the failing test t/GtkAction.t? And thanks for testing!
[13:34] <carnil> [14:25] < geser> carnil: FTBFS in my lucid pbuilder. It fails at some tests. (AMD64; libgtk2-perl: 1:1.221-4ubuntu1; libgtk2.0-dev: 2.20.0-0ubuntu3)
[13:34] <carnil> ups, pasting to wrong channel ö
[13:38] <geser> carnil: yes, "t/GtkAction.t                    (Wstat: 768 Tests: 19 Failed: 3)", "Failed tests:  11-13", "Non-zero exit status: 3"
[13:45] <carnil> geser: okay many thanks, at least it is consistent. If we manage to fix it before lucid release, hope it will get into it too.
[14:15]  * hyperair wonders what ubuntu-iso in ubuntu-dev-toolsi s
[14:15] <hyperair> yay for manpageless binaries
[14:16] <hyperair> ah at least apt's description has it
[14:26] <persia> hyperair: Just upload a manpage for it :)
[14:27] <hyperair> persia: at this rate, i'm going to upload manpages for every single manpageless binary in ubuntu. why can't the authors of the binaries write them?
[14:27] <persia> Sheer laziness.  I know that I tend to avoid making changes that require changes to manpages to avoid doing manpages.
[14:27] <nigelb> hyperair, when they have you why should they :D
[14:28]  * hyperair throws tomatoes at nigelb 
[14:29] <nigelb> lol
[14:29] <hyperair> persia: i've mentioned this before, but i'm beginning to get the feeling that new contributors make better packages than old seasoned ubuntu developers.
[14:29] <hyperair> persia: simply because they obey every single lintian complaint
[14:30] <sebner> hyperair: rotten ones, rotten ones!
[14:30] <hyperair> sebner: haha not again
[14:30] <sebner> hyperair: you are always forgetting! :P
[14:30] <hyperair> sebner: i like fresh tomatoes. i don't want to touch rotten tomatoes =\
[14:31] <nigelb> hyperair, I tend to agree (not about the tomatoes :D)
[14:32] <sebner> hahaha
[14:32] <hyperair> nigelb: heheh i was about to ask whether you preferred rotten tomatoes instead =p
[14:32] <nigelb> hehe
[14:33] <nigelb> hyperair, I always tag patches, etc. but find very few patches tagged in packages I fix bugs
[14:34] <hyperair> nigelb: because the seasoned ol ones don't need to please anybody
[14:34] <nigelb> hyperair, there will come a day when lintian will check for patch tags ::D
[14:37]  * hyperair mumbles the code is open, you're free to patch it in...
[14:37] <hyperair> nigelb: sound familiar? ;-)
[14:37] <nigelb> hyperair, I thought about it, but its C and I'm zero there :D
[14:38] <hyperair> nigelb: eh? lintian is C?
[14:38] <nigelb> hyperair, I thought so
[14:38] <nigelb> it isnt?
[14:38] <hyperair> $ file /usr/bin/lintian
[14:38] <hyperair> /usr/bin/lintian: a /usr/bin/perl -w script text executable
[14:38] <hyperair> >_>
[14:39] <sebner> hyperair: all the same crap :P
[14:39] <hyperair> sebner: perl's a different level of crap
[14:39] <nigelb> perl? how retro
[14:39] <sebner> heh
[14:39] <hyperair> but nothing is as crappy as assembly.
[14:40] <hyperair> okay, maybe visual basic is.
[14:40] <hyperair> and maybe pascal
[14:40] <ScottK> Pascal was lovely for it's day.
[14:40] <hyperair> i'd take on assembly over visual basic any day
[14:40] <ScottK> Certainly nothing like assembly or VB.
[14:40] <nigelb> vb is fun.  I learned VB first :D
[14:41] <nigelb> hyperair, it teaches you how not to write a program :D
[14:41] <hyperair> nigelb: well said.
[15:34] <ScottK> lamont: I think it's safe to drop Postfix's (alternate) build-dep on libmysqlclient14-dev now.
[16:13] <SandGorgon> anybody know whom to ask for help in this bug - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/539086 - we are absolutely unable to even install Lucid
[16:13] <SandGorgon> the bug is assigned to ubiquity right now
[17:18] <ccheney> anyone know why openoffice.org-writer2latex in lucid is still showing up as 0.5.0.2-4ubuntu1 ?
[17:18] <ccheney> oh nm my cache is somehow weirdly stale
[17:20]  * ccheney should stop using dpkg -p, heh
[17:32] <lamont> so htf do I undo the ugliness that is my window title bar now?
[17:32] <lamont> ScottK: it's still in dapper....
[17:32] <lamont> universe, to be sure, but...
[17:33] <ScottK> lamont: So you'd need to be trying to build postfix with Main disabled....
[17:33] <lamont> jej
[17:33] <lamont> heh
[17:33] <lamont> so... glib2.0... totally going to go tweak sbuild-package to totally fail glib2.0 on sparc
[17:34] <lamont> or do an upload just to supersede the build
[17:34] <lamont> not sure which
[17:52]  * lamont watches the glib2.0 build on artigas
[17:54]  * ScottK hands lamont a fire extinguisher.
[17:55] <lamont> ScottK: go read the build log.  I. WIN.
[17:55] <ScottK> Can't.  It's not all the way dead yet.
[17:55] <lamont> is now
[17:56] <lamont> search for 'really'
[17:56] <ScottK> Nice.
[17:56] <ScottK> I see it
[18:04] <geser> hmm, since when does the openoffice splash screen the oracle logo?
[18:05] <ScottK> geser: Since Oracle bought Sun.
[18:05] <ScottK> (it had the Sun logo before)
[18:07] <geser> hmm, somehow I didn't notice the Sun logo much
[18:15] <ScottK> lucas: Now that we've removed the unbuildable binaries re the supportable binaries spec, I was wondering if we could have another rebuild to I can look for packages now missing build-deps (we've hit a few at random and I want to take a systematic look)?
[18:16] <lamont> ScottK: there's a test-rebuild of lucid that's working on starting, needs a little more love from us'ns once the UK is online in the morning
[18:16] <ScottK> lamont: Main or all of it?
[18:16] <lamont> main, I expect
[18:16] <ScottK> The stuff I need it all Universe/Multiverse
[18:17] <lamont> ah, ok.  in any case, it would be best to get the current logjam happy first
[18:17] <ScottK> Plus if he does it, I can diff the results and not have to engage in fancy scripting.
[18:17] <lamont> though as long as you don't mark it for publishing, all is OK
[18:30] <slangasek> lamont: lucas's rebuilds happen outside LP
[18:30] <lamont> slangasek: oh.  well then.
[18:30] <lamont> outside LP == outside my concern
[18:31] <ScottK> He can also do it overnight instead of over weeks.
[18:31] <lamont> ah.  many many machines, eh?
[18:32] <LaserJock> I thought he had something like 4k, but that was a long time ago so I could be wrong
[18:36] <geser> IIRC it's done on the "Grid5000" in France -> https://www.grid5000.fr/mediawiki/index.php/Special:G5KHardware
[19:04] <TrueTom> Does anyone know if 'acipd' is still used to handle events like closing/opening the lid of a notebook?
[20:21] <zyga-nc10> I'm looking for someone involved with couchdb and python
[21:35] <mdke> does anyone know where the Ubuntu icon from the top left of the menubar comes from?
[21:35] <mdke> I'm struggling to find it for some reason
[21:46] <fagan> mdke: its built into the theme
[21:49] <mdke> fagan: but the icon must be found on the system somewhere right? I can't seem to find it
[21:50] <fagan> mdke: id say best bet would be to look at the theme package itself and see if you can find it in there
[21:51] <fta> when will the unapproved queue be processed? been waiting for almost a week now :(
[21:51] <mdke> fagan: I'm browsing the various icons in the theme packages
[21:53] <mdke> ah, I think I have it
[21:54] <fagan> nice
[22:05] <james_w> fta: unapproved of what? oldest entries are 4 days old
[22:05] <james_w> is that almost a week?
[22:07] <MariachiAC> Hello everyone. i'd like to update my ubuntu system to 10.04. however the last time I tryed the system rebooted and I was unable to boot the system. i got an error message saying unable to connect to plimith. i'm a blind user using the orca screen reader and speakup.
[22:10] <fta> james_w, i submitted chromium almost 6d ago, lots of people are waiting for the ssl fix
[22:11] <james_w> launchpad says the 1st
[22:20] <arand> MariachiAC: #ubuntu+1 is the channel for 10.04 support, and likely more active.
[22:24] <MariachiAC> arand: Thank you
[22:32] <lifeless> persia: sorry for disappearing last night
[22:32] <lifeless> I'd like to resume in a few hours
[23:02] <kees> can an ubuntu-release person review bug 555967 ?  I'd like to get it uploaded earlier rather than later.  :)
[23:44] <lee_> how many developers are there?
[23:46] <lifeless> of ?
[23:48] <lee_> idk, just ubuntu developers in general
[23:49] <lee_> and the ironic thing, your nickname is liveless and yet you're the only one that responded to my question...
[23:49] <lee_> lifeless*
[23:51] <kklimonda|G1> lee_: few hundreds but i don't remember the exact number - there are around 600 ubuntu-members and not all of them are developers
[23:53] <lee_> I see
[23:56] <LaserJock> it's usually ~150-200 in the Ubuntu Developers Launchpad team
[23:57] <LaserJock> but there are also quite a lot of contributing developers one might say
[23:57] <kklimonda|G1> LaserJock: oh? only that much? /me is surprised
[23:58] <ajmitch> kklimonda|G1: that number is still far higher than those who are regularly contributing
[23:58] <LaserJock> 158 is the number of members right now
[23:58] <LaserJock> yeah, I would put the regulars at <= 100 I'd think
[23:58] <kklimonda|G1> ajmitch: i know, but i was under the impression that the number is in high 200s and not 100s :/
[23:59] <LaserJock> it's been that way for years
[23:59] <LaserJock> roughly
[23:59] <LaserJock> between 100 and 150, it seems to have hit some sort of equilibrium