[18:05] <edwalf> hola
[18:05] <edwalf> Necesito ayuda un poco urgente
[18:07] <edwalf> hola
[18:09] <edwalf> hola, alguien me puede ayudar con la instalacion de un controlador grafico?
[18:15] <robbiew> o/
[18:16] <jdstrand> o/
[18:17] <mdeslaur> hellow
[18:18] <jdstrand> hiw
[18:18] <sbeattie> hey
[18:18] <kees> \o
[18:19] <kees> okay, so, I'm on community. publishing yet-another hardy-openjdk to fix more universe regressions
[18:19] <kees> the security bug list could use some love; I took it from about 85 bugs to about 40 now, but there are some things still in there
[18:20] <kees> I'm going to try to take a few low-hanging fruit updates too. libhx looked reaaally easy
[18:20]  * jdstrand will get to them
[18:20] <kees> I'm also tracking a number of kernel issues that were reported last week
[18:21] <kees> that's it from me!
[18:21] <jdstrand> shall I go?
[18:21] <kees> yawp
[18:21] <jdstrand> so as of right...
[18:21] <jdstrand> 'now'
[18:21] <jdstrand> I uploaded 0.30 to maverick
[18:21] <jdstrand> ufw
[18:21] <kees> \o/
[18:21] <jdstrand> \o/
[18:22] <mdeslaur> yay :)
[18:22] <jdstrand> :)
[18:22] <jdstrand> anyhoo
[18:22] <jdstrand> so I know I've kept saying I was going to get libvirt out, but I think this time I mean it
[18:22] <kees> hehe
[18:23] <mdeslaur> hehe
[18:23] <jdstrand> the last kernel update and its associated regression distracted me a bit, as did a libvirt/eucalyptus bug and some other stuff
[18:23] <jdstrand> that's all done, so I'll get back to libvirt
[18:23] <jdstrand> I am on triage this week and will pick up an update as time allows
[18:23] <jdstrand> that's it from me
[18:24] <jdstrand> mdeslaur: you're up
[18:24] <mdeslaur> So, I'm preparing libwww-perl and bogofilter updates
[18:24] <mdeslaur> I checked in a bogofilter test script this morning
[18:24] <mdeslaur> and am working on a libwww-perl test script
[18:24] <mdeslaur> I'll probably be releasing them tomorrow
[18:25] <mdeslaur> and will be looking for other updates to do in the list
[18:25] <mdeslaur> that's it from me
[18:25] <mdeslaur> sbeattie: your turn
[18:25] <sbeattie> Hrm, I was on community last week, and apparently did a bad job of it if I left the new bugs queue in such a state, sorry about that.
[18:26] <jdstrand> sbeattie: new bugs is not community-- that's triage
[18:26] <sbeattie> I released an okular/kdegraphics update at the prompting of jriddell.
[18:26] <jdstrand> community is processes debdiffs and fake security syncs
[18:26] <sbeattie> jdstrand: ah, okay, I tried to hit them during my triage week.
[18:27] <kees> s'okay, we just do what we can. :)
[18:27] <sbeattie> I also added a test script for okular to qart
[18:27] <jdstrand> yes, no worries
[18:27] <sbeattie> (based on the evince script)
[18:27] <jdstrand> everyone is busy, we'll back each other up as needed
[18:28]  * ScottK just added a comment to Bug #625849 that he wanted to bring to the attention of community/triage as appropriate.
[18:28] <kees> ScottK: okay, thanks
[18:29] <sbeattie> I helped hggdh with some qart integration into checkbox, and as part of that I'm now running through a bunch of the qart tests on maverick to look for regressions, I know we've got at least some possible ones in test-built-binaries.py :-(
[18:29] <mdeslaur> ouch!
[18:29] <sbeattie> yeah.
[18:29] <kees> test-built-binaries is rather fragile
[18:29] <sbeattie> mdeslaur: I think the DNSSEC tests from bind9 are failing as well; I think you wrote those?
[18:29]  * kees has been thinking about ways to make it a little more robust
[18:29]  * jdstrand was uaware of test-built-binaries
[18:29] <jdstrand> oh, did I say that out loud?
[18:30] <sbeattie> kees: I need to triage the failures to see why, and then I'll see if there's a way we can make them more robust if its a false positive.
[18:30]  * kees runs the test
[18:30] <mdeslaur> sbeattie: hmm...yeah I wrote them...I'll take a look
[18:30] <jdstrand> there are always things we need to fix in those with each new release
[18:30] <kees> yeah
[18:30] <sbeattie> ... or I can let kees do it.
[18:31] <jdstrand> anything with an apparmor profile we ought to run around RC
[18:31] <sbeattie> jdstrand: right, I wanted to make sure if the issue was in the package rather than our tests, we should fix them now.
[18:31] <jdstrand> sbeattie: yes, that is a great idea
[18:32] <sbeattie> anyway, also for this week, I try to pick up another update.
[18:32] <sbeattie> I think that's it for me.
[18:32] <kees> alright, anything else, or questions/concerns for the security team?
[18:33] <jdstrand> sbeattie: just for info, not to poke you or anything...
[18:33] <sbeattie> heh, uh-oh
[18:33] <jdstrand> sbeattie: I was curious on the timeframe for apparmor 2.5.1
[18:33] <sbeattie> jdstrand: me too!
[18:33] <jdstrand> lol
[18:33] <sbeattie> (oops, did I say that out loud)
[18:33] <kees> sbeattie: looks like nagios-plugins is a real regression (it lost PIE)
[18:34] <jdstrand> sbeattie: really, in terms of maverick, it isn't hugely critical, cause I'll just pull what we have
[18:34] <sbeattie> jdstrand: I'm conflicted; I want it out soon because we've not been very good at doing real releases.
[18:34] <jdstrand> sbeattie: but it would be nice to have it like we talked about. if you need help, let me know
[18:34] <sbeattie> but I also keep finding bugs, etc.
[18:35] <mdeslaur> sbeattie: new bugs are for 2.5.2 :)
[18:35] <sbeattie> mdeslaur: right, I should just let it go and work on releasing 2.5.1
[18:36] <jdstrand> sbeattie: well, an important bug that I think jjohansen may have been working on is that I know at least apparmor_notify doesn't work in maverick now-- did those fixes make it into 2.5.1 already (I haven't tried, please forgive me)
[18:36] <jjohansen> well that and maverick doesn't need 2.5.1 kernel bits so just pull
[18:36] <jdstrand> hey jjohansen :)
[18:36] <jjohansen> jdstrand: no, I haven't got them in yet
[18:36] <jdstrand> ok
[18:37] <jjohansen> I have some of the patches in, but not enough to get aa_notify going
[18:37] <jdstrand> well, we don't need to upload anything this week anyway
[18:37] <jjohansen> I can get them in this week
[18:37] <sbeattie> jjohansen: what's needed?
[18:37] <jjohansen> sbeattie: more log parsing updates
[18:37] <sbeattie> jjohansen: ah, okay, we should probably coordinate.
[18:37] <jjohansen> yeah
[18:37] <sbeattie> but here/now probably not
[18:37] <sbeattie> but here/now's probably not the place/time
[18:37] <jjohansen> and the tools, need some knowledge about mapping target to name etc
[18:38] <jjohansen> yep
[18:38] <sbeattie> jdstrand: is that a sufficiently confusing status update?
[18:38] <jjohansen> :)
[18:38] <jdstrand> actually, I was just typing "well, that answer's my question anyway"
[18:38] <jdstrand> :)
[18:39] <jdstrand> answers
[18:39] <jdstrand> so "yes"
[18:39] <kees> ...
[18:39] <jdstrand> that's it from me
[18:39] <kees> how did coreutils lose stack protector?
[18:39] <kees> okay, anything else?
[18:40]  * jdstrand realizes he did know what test-built-binaries.py after all
[18:40] <jdstrand> ScottK: ack on that bug btw
[18:40] <kees> alrighty, thanks everyone!
[18:41] <jdstrand> thanks kees! :)
[18:41] <mdeslaur> thanks
[18:43] <ScottK> kees: No idea (re that bug), but I can investigate.
[18:43] <kees> ScottK: cool.
[18:49] <JohnFlux> Hi all - did I miss the meeting?
[18:51] <jjohansen> JohnFlux: if you mean the security meeting then yes
[20:58] <HaYder> me podrian ayudar a generar un misarchivos.lst
[21:01] <HaYder> desde consola
[21:02] <HaYder> ese archivo va a contener el nombre y los archivos de toda una carpeta
[21:11] <JFo> !sp
[21:35] <czajkowski> !es
[21:37] <JFo> yep, that one
[21:37] <czajkowski> :)