[18:16] <tsimonq2> Can somebody look into that person in #ubuntu-meeting?
[18:16] <tsimonq2> sylvia103<EMAIL_ADDRESS>[18:16] <tsimonq2> I have to dip out, PM with questions...
[21:15] <sylvia02> Hello
[21:15] <sylvia02> I heard there was an investigation involving me
[21:15] <sylvia02> May I know what this is about?
[21:16] <sylvia02> I was here with my boyfriend because this company does not operate weekends, so we thought this would be a good place to get privacy.
[21:17] <sylvia02> Why am I being told there is an investigation about me
[21:17] <sylvia02> Sylvia103 was my username
[21:19] <sylvia02> What is going on?
[21:19] <sylvia02> I was horsing around with meeting topics because I knew it couldnt hurt anybody since Ubuntu is closed weekends.
[21:28] <Flannel> hi sylvia02
[21:28] <sylvia02> Hi Flannel
[21:28] <sylvia02> thank you for replying
[21:28] <sylvia02> So, are you able to see all I typed before you said hi
[21:29] <Flannel> sylvia02: I did.
[21:29] <sylvia02> ok
[21:30] <sylvia02> Why is there an investigation on me?
[21:30] <Flannel> sylvia02: Who said there was an "investigation"?
[21:30] <sylvia02> Somebody told me that I was being talked about
[21:31] <Flannel> Ok.  Well, not by us.  At least, not that I can see.
[21:31] <sylvia02> My username was Sylvia103
[21:31] <Flannel> sylvia02: FYI, Ubuntu isn't "closed" on the weekends.  We're a community of volunteers, not a company.
[21:32] <sylvia02> Well, there are no meetings on weekends.
[21:32] <Flannel> sylvia02: There has been, there may not be any this weekend, I don't know.
[21:33] <sylvia02> We just felt that since the meeting channels were not necessary to the company this weekend that my boyfriend and I could use them
[21:33] <Flannel> sylvia02: Again, Ubuntu is not a company.
[21:34] <sylvia02> well, ok the channels were not necessary to Ubuntu this weekend
[21:34] <Flannel> sylvia02: Goofing around in channels isn't exactly the best idea.  You know you can just make your own channel, right?
[21:34] <sylvia02> Well, my boyfriend introduced me to all of this
[21:34] <sylvia02> so no I did not know that
[21:35] <Flannel> sylvia02: That's fine.  You're not expected to know everything right away.
[21:35] <sylvia02> He told me that he uses the meeting command for personal reasons in these types of channels on weekends and holidays when these types of channels are not normally in use
[21:35] <sylvia02> so I started following after him
[21:37] <sylvia02> I asked him if he is supposed to be doing that and he told me it is perfectly fine as long as it is a weekend, New Years Day, Memorial Day, Independence Day, LAbor Day, Thanksgiving Day, Christmas Eve, Christmas Day, or New Years Eve.
[21:37] <sylvia02> he said nobody will care those days
[21:38] <Unit193> 1. He seemingly hasn't done it in Ubuntu.  2. That's false, it's not fine so please don't.
[21:38] <sylvia02> ok. I apologize for my part.
[21:38] <Flannel> sylvia02: Alright.  Well, I think that's not actually the case.  The meetings get logged automatically, so even if no one is around using the channel, the meeting still "happens"
[21:39] <Flannel> sylvia02: Are you looking for a "private" channel with just people you know?  Or are you looking for other people to chat with? or what?
[21:39] <sylvia02> Like I said, my boyfriend came up with the idea of going to #ubuntu-meeting to chat
[21:39] <Unit193> sylvia02: Thanks, as long as you guys don't keep it up, no harm.  Also, if you're interested, you can actually set up a clone of it using the 'meetingology' plugin and limnoria/supybot.
[21:40] <Flannel> sylvia02: Right.  I understand that.  I'm trying to help you have a place to chat in the future that isn't #ubuntu-meeting
[21:40] <sylvia02> Our intent was to find a private channel
[21:41] <Flannel> sylvia02: Alright.  So, what you can do is join the channel "##sylvias-chat", and assuming no one else is already in there (which I imagine would be rare), then it'll just be you and whomever else you tell to go there.
[21:42] <sylvia02> ok
[21:42] <Ender094> What the heck is going on here?
[21:42] <sylvia02> ender, please dont make a scene
[21:42] <Flannel> Ender094: How can we help you?
[21:42] <Ender094> WHY ARE YOU HARRASSING MY GIRLFRIEND
[21:42] <sylvia02> He is not harrassing me
[21:42] <sylvia02> We were out of line
[21:42] <Flannel> Ender094: We're not.  Simmer down.
[21:43] <Ender094> No we werent
[21:43] <sylvia02> They were not happy about us playing around here like we were
[21:43] <Flannel> It was a simple mistake.  No one was "out of line", but we'd like to avoid using #ubuntu-meeting for your personal correspondance in the future.
[21:43] <Ender094> Why can’t we use it on weekends?
[21:44] <Ender094> not like it will hurt anybody?
[21:44] <Flannel> Ender094: It's not meant for that.  Also, if you're looking for a private place to chat, #ubuntu-meeting is publically logged, so... that'd be less-than-private.
[21:44] <sylvia02> Ender, the matter of the fact is they don't want us using their channels for our personal affairs. I don't see why we cannot respect that.
[21:44] <Flannel> Ender094: Also, you can just create your own channel to chat in, that actually has zero people in it (except you)
[21:45] <Ender094> It doesn’t have the meeting feature I like
[21:45] <Flannel> Ender094: Ubuntu doesn't "close" on the weekends.  It's a community of volunteers, and sometimes we "work" weekends.
[21:45] <Ender094> i don’t see any meetings scheduled on weekends
[21:45] <sylvia02> Ender, stop it.
[21:45] <Flannel> sylvia02: It's alright.
[21:46] <sylvia02> Enough is enough. We need to find our own place
[21:46] <sylvia02> You are starting to embarrass me .
[21:46] <sylvia02> This channel is theirs and we need to respect that.
[21:46] <sylvia02> period
[21:46] <Flannel> Ender094: Meetings do happen on the weekends.  Also, every "meeting" you make is logged and recorded in our meetings, so it still shows up elsewhere, even if there's no one active in that room during the time you are "meeting"
[21:47] <sylvia02> Flannel has a very good point.
[21:47] <sylvia02> If we want our privacy, this may actually be a bad choice for our own sake
[21:47] <Flannel> Ender094: If you'd like a meeting bot in your own channel, Unit193 would be happy to point you to instructions on setting that up, I'm sure.
[21:47] <sylvia02> because when somebody goes through the logs, it become public
[21:48] <Ender094> Ok fine
[21:48] <Ender094> we will find our own channel
[21:48] <Ender094> im getting out of this place. /part
[21:48] <sylvia02> I am sorry about my bf.
[21:49] <sylvia02> We will respect your wishes
[21:49] <Flannel> sylvia02: Like I was saying earlier, you can just join ##sylvias-chat, or ##enders-chat or whatever.  Channels are not a scarse resource.
[21:49] <Flannel> sylvia02: No problem.
[21:49] <sylvia02> Yeah, I see what you are saying
[21:49] <sylvia02> My bf is struggling to accept anything. It is not your fault. Your wishes are not unreasonable.
[21:50] <Flannel> sylvia02: It's fine.
[21:50] <sylvia02> We will do just what you said and create our own place
[21:50] <Flannel> sylvia02: Have fun.
[21:50] <sylvia02> Thank you.
[21:50] <sylvia02> Merry Christmas


[00:03] <snap-l> Wow.
[00:03] <snap-l> rick_h__: So, doing the camping thing this year, or just getting ready for next year?
[00:05] <rick_h__> snap-l: this year. Hopefully, if all goes well will be putting in to buy a trailer end of this week and then work on getting it tweaked and setup
[00:05] <rick_h__> it'd be awesome if we could use it for the 4th of july, but might be later in july we get going with it.
[00:05] <rick_h__> but I think we've got 3 or four trips planned for this year and a big one of taking it to VA for the family visit
[00:06] <snap-l> Cool
[00:06] <rick_h__> cool, mako is going to be in ann arbor greg-g
[00:06] <rick_h__> http://mako.cc/copyrighteous/london-and-michigan
[14:32] <snap-l> Good morning
[14:45] <wolfger> Good morning
[15:44] <rick_h__> morning
[17:02] <wolfger> rick_h__: is always so noncommittal about the quality of the morning...
[17:25] <rick_h__> wolfger: well, sometimes it's hard to tell
[17:27] <snap-l> heh
[17:27] <snap-l> Could be a good morning, but could be a bad morning all the same
[17:27] <snap-l> sounds like an A.A. Milne story. :)
[20:10] <greg-g> rick_h__: yeah, saw that, kinda jealous. 4 weeks of mako should be a fun time.
[20:54]  * greg-g watches the Snowden interview
[21:51] <rick_h__> greg-g: yea, read that stuff. Interesting


[13:27] <smartboyhw> zequence, hello:)
[13:28] <zequence> smartboyhw: hi
[13:30] <zequence> OvenWerk1: I'd rather work on replacing qjackctl with a new tool
[13:30] <zequence> i.e. -controls
[13:30] <OvenWerk1> zequence: what would you use to make jack conections?
[13:31] <smartboyhw> zequence, OK, I'm starting to feel dizzy as to what we are planning for 14.04 LTS now-.-
[13:31] <OvenWerk1> smartboyhw: new artwork.
[13:32] <zequence> OvenWerk1: patchage, or a modded version of it, as falktx uses
[13:32] <smartboyhw> OvenWerk1, well, that's not just it, right?!
[13:32] <zequence> smartboyhw: no
[13:32] <OvenWerk1> I have had patchage crash on me too many times.
[13:33] <OvenWerk1> smartboyhw: sorry, I was joking, art is the one thing we have talked about..
[13:34] <smartboyhw> OvenWerk1, lol. I do think we need to start planning for 14.04 now (don't know if you guys like it), but we seem to have quite a lot of things planned and I can't remember all of them-.-
[13:34] <OvenWerk1> ardour3. Sync the CAPs plugins would be nice.
[13:34] <zequence> We do planning when this cycle is done
[13:35] <zequence> though, 14.04 has already been mapped out quite well in planning already
[13:35] <zequence> one just needs to read through it
[13:36] <OvenWerk1> FF is past, we could look more at 14.04. Only artwork left for this cycle.
[13:36] <smartboyhw> Yeah, and it's madeinkobaia's job:P
[13:37] <zequence> in time
[13:37]  * OvenWerk1 has done the stuff he wanted for this cycle
[13:37] <zequence> yes, and that was very good of you
[13:37] <smartboyhw> OvenWerk1, congratulations
[13:37]  * smartboyhw didn't do anything this cycle basically;P
[13:37] <smartboyhw> Fortunately, I got goals for 14.04
[13:38] <smartboyhw> If not I will be a noob here;P
[13:38] <zequence> We need to have a meeting at some point
[13:38] <zequence> at least one meeting before we start working on the next cycle
[13:38]  * smartboyhw agrees
[13:38] <OvenWerk1> It looks like some of the broken things for xfce will get fixed.
[13:39] <OvenWerk1> arandr can go, I think.
[13:40] <zequence> If someone wants, they could put some time on thinking about how we do beta testing
[13:41] <zequence> we should make sure no application is suffering from bad packaging, etc
[13:41]  * smartboyhw should (by his role)
[13:41] <zequence> and just generally try to catch bugs
[13:41] <OvenWerk1> kdenlive seems to work.
[13:41] <OvenWerk1> jack works, ardour does.
[13:42] <zequence> Did you check full functionality, or just make sure the applications start?
[13:42] <OvenWerk1> the audio applet doesn't
[13:42] <zequence> well, there's one problem then - but I suppose Xubuntu is on it?
[13:42] <zequence> as it's shared by both..
[13:42] <OvenWerk1> kdenlive I made/edited a video.
[13:42] <smartboyhw> OvenWerk1, we have quality control in KDE here;P
[13:42] <zequence> I don't think it's helpful citing which apps works on this channel
[13:42] <OvenWerk1> xubuntu has a fix... if they can get it out
[13:42] <zequence> there's bugs for testing applications. and we need to write test cases
[13:43] <zequence> ok, so then it's not a problem
[13:45] <OvenWerk1> I don't know where to go with blender though. How to test functionality.
[13:45] <smartboyhw> OvenWerk1, well, it's just a matter of how a normal user uses it
[13:45] <smartboyhw> As long as we know how they use it, we test it by doing the exact same
[13:45]  * OvenWerk1 is trying to say there are a number of apps thet require some knowlage of the craft.
[13:46] <zequence> The one who writes the test case needs to know the application
[13:46] <zequence> and the idea is we involve our users in this
[13:46] <smartboyhw> zequence, yes we are supposed to
[13:46] <OvenWerk1> good
[13:47] <OvenWerk1> The one thing I did notice with kdenlive is the docs don't work.
[13:48] <OvenWerk1> It seems the required kde infrastructure is not installed/running
[13:49] <OvenWerk1> Also, there are now 4 BG processes running for KDE that are no longer in use.
[13:49] <zequence> sounds like a packaging problem
[13:49] <smartboyhw> OvenWerk1, huh?
[13:49] <smartboyhw> OvenWerk1, how?
[13:51] <OvenWerk1> kdeinit4 klauncher kded4 /usr/bin/knotify4 were started by kdenlive, but of course kdenlive expects them to remain running so it doesn't kill them.
[13:52] <OvenWerk1> This is part of the problem with any kde app.
[13:55]  * OvenWerk1 kills these things and starts krita
[14:09] <OvenWerk1> krita starts more kde BG stuff... and it is not the same ones, so after running both krita and kdenlive we would have 6 spare things running around. However the doc book in krita is a web page.
[14:11] <smartboyhw> What did I miss?!
[14:12] <OvenWerk1> 06:50 < OvenWerk1> kdeinit4 klauncher kded4 /usr/bin/knotify4 were started by  kdenlive, but of course kdenlive expects them to remain  running so it doesn't kill them.
[14:12] <OvenWerk1> 06:50 < OvenWerk1> This is part of the problem with any kde app.
[14:12] <OvenWerk1> 06:54  * OvenWerk1 kills these things and starts krita
[14:12] <OvenWerk1> krita starts more kde BG stuff... and it is not the same  ones, so after running both krita and kdenlive we would have  6 spare things running around. However the doc book in krita  is a web page.
[14:13]  * smartboyhw recommends OvenWerk1 to use the IRC logs syntax selection of paste.ubuntu.com next time:)
[14:15] <OvenWerk1> They don't seem to be actively using cpu, but they are using 115M of RAM
[14:25] <OvenWerk1> khelpcenter is quite small, we could include it.... but then I got a not found page...
[14:26] <smartboyhw> OvenWerk1, :O
[14:31] <OvenWerk1> There is not a kdenlive doc package, but there are online docs.
[14:36] <OvenWerk1> The kdenlive-data package (which we ship) does seem to have the offline docs there. The help center just doesn't seem to know about it.
[15:17] <OvenWerk1> Hmm, the extra installer for each workflow should include the ubuntustudio meta for that workflow.
[15:18] <OvenWerk1> That would be less confusing for someone who added the menu to another DE
[15:31] <OvenWerk1> GA! found the problem with the kdenlive docbook... which doesn't work in a kubuntu session either.


[16:31] <jdstrand> hi!
[16:31] <jjohansen> \o
[16:31] <jdstrand> #startmeeting
[16:31] <meetingology> Meeting started Mon Aug 18 16:32:07 2014 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:31] <meetingology> Available commands: action commands idea info link nick
[16:32] <jdstrand> The meeting agenda can be found at:
[16:32] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:32] <jdstrand> [TOPIC] Weekly stand-up report
[16:32] <jdstrand> I'll go first
[16:32] <jdstrand> I'm in the happy place this week
[16:32] <chrisccoulson> hi :)
[16:33] <jdstrand> I plan to focus on apparmor: taking up tyhicks' work, policy updates (abstractions, system, click), testing and ultimately, landing
[16:33] <jdstrand> I'm keeping an eye on the openstack point release for trusty
[16:34] <jdstrand> and I'm working with foundations (eg, bhuey) on the pending openjdk-7 security update
[16:34] <jdstrand> mdeslaur: you're up
[16:34] <mdeslaur> I'm on triae this week....although I'm off on vacation on wednesday, so it's a short week for me...someone will have to take over triage
[16:35] <jdstrand> mdeslaur: sarnold and I will handle that
[16:35] <mdeslaur> I'm currently working on an openssl regression on lucid, that exposed a bug in postfix...postfix is now fixed, and I'm going to publish a regression fix for openssl on lucid this afternoon
[16:35] <mdeslaur> and I'll monitor any last minute updates I can possibly work on before I go on holiday
[16:35] <mdeslaur> that's pretty much it for me, sbeattie you're up
[16:36] <sbeattie> I'm on apparmor this week.
[16:37] <sbeattie> I'm reviewing jjohansen's abstract socket patches and testing the kernel to help out landing that.
[16:37] <sbeattie> That's pretty much it for me. tyhicks is not here...
[16:38] <sbeattie> jjohansen: you're up.
[16:39] <jjohansen> I am working on revising and landing the abstract socket mediation
[16:39] <jjohansen> I will also be helping tyhicks with anything he needs for LSS
[16:40] <jjohansen> I think thats it for me, sarnold you're up
[16:41] <jdstrand> chrisccoulson: why don't you go first
[16:41] <jdstrand> s/first/now/
[16:42] <chrisccoulson> this week, I'm focusing on bug 1214034
[16:43] <jdstrand> oh nice
[16:43] <chrisccoulson> I'm also expecting a chromium update from chad, and I have an oxide update to publish too
[16:43] <jdstrand> securty update?
[16:43] <chrisccoulson> it is
[16:44] <jdstrand> is that 1.1?
[16:44] <chrisccoulson> not yet, it's still 1.0
[16:44] <jdstrand> chrisccoulson: does that mean we are still pulling down new chromium content api into 1.0?
[16:45] <chrisccoulson> the 1.0 update is the one that goes with chromium 36.0.1985.143
[16:45] <chrisccoulson> (see http://omahaproxy.appspot.com/)
[16:46] <jdstrand> so, I guess that is a 'yes' :)
[16:46] <chrisccoulson> yeah :)
[16:46] <jdstrand> chrisccoulson: curious, when do we expect 1.1 in trusty?
[16:46] <chrisccoulson> that was driven by the flash update, but there's other fixes in it too
[16:46] <chrisccoulson> 1.1 is probably in another couple of weeks
[16:46]  * jdstrand is guessing backporting to both is taking some time
[16:47] <jdstrand> ackporting isn't the right word
[16:47] <jdstrand> refreshing for both
[16:47] <jdstrand> cool
[16:47] <chrisccoulson> i think that's me done :)
[16:48] <jdstrand> sarnold doesn't seem to be present, so I'll move along
[16:48] <jdstrand> [TOPIC] Highlighted packages
[16:48] <jdstrand> The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.
[16:48] <jdstrand> See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
[16:48] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/ibutils.html
[16:48] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/libmms.html
[16:48] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/cityhash.html
[16:49] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/plib.html
[16:49] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/lightdm-gtk-greeter.html
[16:49] <jdstrand> [TOPIC] Miscellaneous and Questions
[16:49] <jdstrand> Does anyone have any other questions or items to discuss?
[16:51] <sarnold> sorry I'm late. I'm on community this week. I'm finishing a review of some apparmor patches and still have two outstanding MIR audits
[16:52] <jdstrand> sarnold: did you see the new one for bug #1358272?
[16:53] <jdstrand> sarnold: (in backscroll from another channel)
[16:54] <sarnold> jdstrand: just now, thanks :)
[16:54] <jdstrand> np
[16:54] <jdstrand> sarnold: did you have anything else?
[16:55] <sarnold> jdstrand: no, that was it
[16:56] <jdstrand> mdeslaur, sbeattie, jjohansen, chrisccoulson, sarnold: thanks!
[16:56] <jdstrand> #endmeeting
[16:56] <meetingology> Meeting ended Mon Aug 18 16:56:42 2014 UTC.
[16:56] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-08-18-16.32.moin.txt
[16:56] <jjohansen> thanks jdstrand
[16:56] <sbeattie> jdstrand: thanks!
[16:56] <sarnold> thanks jdstrand
[16:57] <mdeslaur> thanks jdstrand!


[12:14] <imbrandon> Toadstool, np
[12:18] <Fujitsu> I didn't want to wait 20 minutes after filing a bug via email... Only to be told I'd left the leading / off the affects line.
[12:19] <LaserJock> crimsun: I attached the debdiff to the bug report
[12:19] <LaserJock> crimsun: http://librarian.launchpad.net/6722675/python-imaging_1.1.5-10ubuntu1.debdiff
[12:19] <LaserJock> _MMA_: yeah, what's up?
[12:19] <_MMA_> I have a newbie.
[12:19] <_MMA_> jussi01 here is going to be working with us.
[12:19] <jussi01> Hi
[12:19] <LaserJock> hi jussi01
[12:19] <_MMA_> Im getting him up with all the links he'll need.
[12:20] <_MMA_> Im talking with him about the importance of MOTU and working with you guys.
[12:20] <LaserJock> imbrandon: I have 3 research related weekly meetings
[12:20] <LaserJock> _MMA_: thanks :-)
[12:21] <imbrandon> _MMA_, cool
[12:21] <imbrandon> LaserJock, ahh
[12:21] <imbrandon> man anyone know christer edwards handle on irc ?
[12:21] <LaserJock> christer or something like that :-)
[12:21] <imbrandon> he is starting yet another Debian package of the day instead of helping the existing one
[12:22] <LaserJock> yeah, I thought that was odd
[12:23] <LaserJock> especially since the first one was a bit contraversial
[12:23] <imbrandon> i left a comment on his blag, but i thought i would twap him on irc too
[12:23] <imbrandon> blog*
[12:23] <LaserJock> heh
[12:23] <LaserJock> swag+blog== blag
[12:23] <crimsun>   python-imaging_1.1.5-10ubuntu1_source.changes: done.
[12:23] <crimsun> Successfully uploaded packages.
[12:23] <imbrandon> heh
[12:23] <LaserJock> crimsun: thank you ever so much
[12:24] <imbrandon> man there is a site at work selling eBooks for $20 bux a pop and makes 40k a month, i need to so do that
[12:24] <imbrandon> lol
[12:24] <imbrandon> eBook about how to get rich, makin him rich
[12:24] <imbrandon> ;)
[12:25] <ajmitch> hi
[12:25] <imbrandon> heya ajmitch
[12:25] <ajmitch> like the one complaining about backports, with no useful suggestions
[12:26] <LaserJock> well obviously Universe is too high of quality for some
[12:26] <LaserJock> and utter crap for others :-)
[12:26] <ajmitch> heh
[12:26] <imbrandon> lol
[12:29] <LaserJock> I have a question about the bug syntax in changelogs, is it supposed to be (Closes LP: #...) or (LP: #...) or ?
[12:29] <LaserJock> the wiki page isn't quite clear for me
[12:30] <ajmitch> and the kde4 debate still rages on
[12:30] <crimsun> LaserJock: it needs only "LP: #number"
[12:30] <crimsun> you can use "Closes: LP: #number" or "(Closes LP: #number)" or whatever as long as the minimum constraint is met
[12:31] <LaserJock> k
[12:32] <LaserJock> but it *has* to have the LP:, right? I want to do Closes: LP #number but I'm thinking that's wrong
[12:32] <ajmitch> check it
[12:33] <crimsun> yes, you need "LP: #"
[12:33] <LaserJock> alright, just so I'm clear
[12:34] <ajmitch> # For Ubuntu/Launchpad bugs
[12:34] <ajmitch> while ($f{'Changes'} =~ /lp:\s+\#\d+(?:,\s*\#\d+)*/ig) {
[12:34] <ajmitch>   push(@launchpad_closes, $& =~ /\#?\s?(\d+)/g);
[12:34] <ajmitch> }
[12:34] <ajmitch> so yeah.. :)
[12:35] <chillywilly> hi
[12:35] <chillywilly> perl?!?
[12:35] <Fujitsu> It doesn't actually do anything on LP yet, however.
[12:35] <chillywilly> egads!
[12:36] <crimsun> chillywilly: since it's part of dpkg-dev, yes
[12:36] <chillywilly> anyone know if there's a core set of upstart scripts written to bring up the base system?
[12:37] <ajmitch> yes
[12:37] <chillywilly> where would I find those?
[12:37] <greff> Is there a way to create standard looking init scripts?
[12:37] <greff> It seems as thought everything in /etc/init.d/ is somewhat standard. I want to be able to create something that looks about the same. Catch my drift?
[12:37] <chillywilly> oh great and powerful motus
[12:37] <crimsun> chillywilly: /etc/event.d/
[12:37] <ajmitch> apt-cache search upstart
[12:37] <chillywilly> yea but I mean source-wise as I don't have the latest bleeding edge package installed
[12:37] <chillywilly> erm, ubuntu installed I mean
[12:38] <chillywilly> not package
[12:38] <crimsun> greff: yes, LSB-ify
[12:38] <crimsun> greff: essentially, modify the initscript, and add lsb-base (>= 3) as a Depends
[12:39] <crimsun> the conversion is pretty straightforward; took about thirty seconds for pulseaudio
[12:47] <pirast> could anyone please apply the debdiff in bug 90814?
[12:47] <Ubugtu> Malone bug 90814 in asterisk "[UPLOAD]  New Asterisk release 1.2.16" [Undecided,Confirmed]  https://launchpad.net/bugs/90814
[12:48] <pirast> i am off now, goog night
[12:48] <pirast> good night
[12:49] <Fujitsu> Night, pirast.
[12:58] <Fujitsu> ajmitch: where is that? On the wiki?
[12:59] <LaserJock> "LDAP out-of-the-box" that should be easy
[12:59] <Fujitsu> crimsun: Can you please officially bless bug #91001.
[12:59] <Ubugtu> Malone bug 91001 in bindgraph "[UVFe]  bindgraph 2.0 -> 2.0a" [Undecided,Unconfirmed]  https://launchpad.net/bugs/91001
[01:00] <Fujitsu> ajmitch: Can you take a look at the above too?
[01:00] <ajmitch> LaserJock: exactly
[01:00] <ajmitch> LaserJock: not to mention that some of us have been working on that sort of thing
[01:01] <LaserJock> ajmitch: whaa?!? ;-P
[01:02] <ajmitch> LaserJock: hard to believe, given the results
[01:02] <ajmitch> but technically there's some work done :)
[01:02] <LaserJock> oh nifty, "Remote accessibility" or "How can I open my box up to the entire world?"
[01:03] <Fujitsu> ajmitch: Do I dare to say `Results? What results?' or would that be danerous?
[01:03] <Fujitsu> *dangerous
[01:03] <ajmitch> Fujitsu: it would be
[01:03] <ajmitch> and I'll rescind that ACK on that UVF request now
[01:04] <Fujitsu> Hah.
[01:05] <Fujitsu> :-/
[01:09] <ajmitch> bye
[01:14] <LaserJock> ajmitch: are you leaving us? :(
[01:15] <imbrandon> LaserJock, remote accessabilty can be good if done right
[01:15] <imbrandon> and secure ;)
[01:16] <LaserJock> sure, I just have my doubts of it being done right or securely
[01:16] <imbrandon> i hear ya
[01:27] <crimsun> Fujitsu: all yours.
[01:27] <Fujitsu> Thanks ajmitch, crimsun.
[01:27] <crimsun> np
[01:59] <pochu> happy hug day!
[02:02] <imbrandon> hrm i wonder how fast a spac qemu box is
[02:02] <imbrandon> if its faster than the ultra iii
[02:02] <imbrandon> or not
[02:02] <zul> whats a spac?
[02:03] <crimsun> it's like a sparc, but it only runs Vista.
[02:03] <imbrandon> its my version of a sparc
[02:03] <imbrandon> lol
[02:03] <zul> imbrandon: i doubt a qemu spac is faster than an ultra 3
[02:10] <bddebian> Heya gang
[02:10] <LaserJock> hi bddebian
[02:11] <bddebian> Heya LaserJock
[02:11] <imbrandon> heya bddebian
[02:11] <bddebian> Hi imbrandon
[02:12] <tonyyarusso> hi bddebian imbrandon
[02:12] <bddebian> Heya tonyyarusso, how's it coming?
[02:12] <Fujitsu> imbrandon: Can you please ack the 3 release tasks in bug #83508?
[02:12] <Ubugtu> Malone bug 83508 in zabbix "Buffer overflow in ZABBIX before 1.1.5 has unknown impact and attack vectors related to "SNMP IP addresses."" [Undecided,Unconfirmed]  https://launchpad.net/bugs/83508
[02:12] <tonyyarusso> bddebian: Waiting for a new tarball... :(  He's had trouble contacting the Linspire guys for some reason it seems.
[02:14] <imbrandon> Fujitsu, done
[02:14] <Fujitsu> Thanks, imbrandon.
[02:14] <imbrandon> np
[02:17] <crimsun> I need to enable sudo's insults so I can differentiate between installs.
[02:18] <LaserJock> :-)
[02:18] <Fujitsu> crimsun: That's my idea!
[02:19] <crimsun> excellent.
[02:21] <sistpoty> hi folks
[02:21] <Fujitsu> Hi sistpoty.
[02:21] <sistpoty> hi Fujitsu
[02:22] <LaserJock> hi sistpoty
[02:22] <sistpoty> hi LaserJock
[02:23] <sistpoty> LaserJock, Fujitsu: give me some hints about the application https://lists.ubuntu.com/archives/motu-council/2007-March/000021.html... I'm still so undecided
[02:24] <crimsun> I'm still waiting to hear back from him
[02:25] <sistpoty> crimsun: did you CC him? not quite sure if he's subscribed
[02:25] <Fujitsu> `Medibuntu'... Is that what I think it is, LaserJock?
[02:25] <sistpoty> (though I guess I could find out)
[02:25] <crimsun> sistpoty: I sent it to him and CCed MC
[02:25] <sistpoty> ah
[02:26] <crimsun> he's probably busy, so there's a grace period
[02:26] <LaserJock> Fujitsu: Media Ubuntu
[02:26] <LaserJock> Fujitsu: not Medical Ubuntu
[02:26] <LaserJock> lol
[02:26] <Fujitsu> LaserJock: Oh, good.
[02:26] <Fujitsu> ajmitch: That's a great idea!
[02:26] <sistpoty> ajmitch++
[02:26] <sistpoty> ;)
[02:26] <Fujitsu> sistpoty: I personally think he also needs more uploads (in addition to the beer).
[02:26] <ajmitch> this is why we have a 2 week period
[02:27] <LaserJock> Fujitsu: if you want to call it that, I think it's a nicer version of Mint
[02:27] <ajmitch> hearing objections, gathering info
[02:27] <Fujitsu> ajmitch: And drinking beer.
[02:27] <sistpoty> ajmitch: unless we'd reach an early +3 or -3
[02:27] <LaserJock> he's done a number of new packages
[02:27] <ajmitch> Fujitsu: that goes without saying
[02:28] <LaserJock> but it seems like he hasn't done a ton of non-NEW stuff and hasn't been doing it for *that* long
[02:28] <ajmitch> sistpoty: heard anything from the sponsors?
[02:28] <ajmitch> how long has he been involved, and how involved has he been around here?
[02:28] <sistpoty> ajmitch: only on the ml
[02:28] <greff> What does Build-Depends: debhelper (>> 3.0.0) mean?
[02:28] <greff> I understand >=, but what does >> mean?
[02:28] <sistpoty> ajmitch: not quite sure, but iirc he's been around for quite some time
[02:28] <crimsun> strictly greater than, greff
[02:28] <sistpoty> (so my brain tends to mix up these things)
[02:29] <ajmitch> sure, I remember him being around for awhile, but that doesn't say much
[02:29] <ajmitch> I've been around for awhile but I don't do anything
[02:29] <sistpoty> hehe
[02:29] <greff> crimsun: Hmm, that's useful how? Will > still allow dpkg -i packagename to work then?
[02:29] <crimsun> greff: err, I presume the strict versioning is purposeful
[02:30] <greff> crimsun: Hehe, where can I learn more about all of this?
[02:30] <crimsun> greff: if such is the case, it should be noted in the changelog
[02:30] <crimsun> greff: Debian Policy Manual and Debian New Maintainers' Guide
[02:30] <greff> crimsun: Thanks a bunch.
[02:30] <crimsun> np
[02:31] <LaserJock> imbrandon:  you can run but you can't hide ;-)
[02:31] <imbrandon> lol
[02:32] <tonyyarusso> ... what's ajmitch looking for a victim for?
[02:32] <crimsun> hey, we have a volunteer!
[02:32] <bddebian> Gah, Bug #23160 is for Hoary
[02:32] <Ubugtu> Malone bug 23160 in laptop-mode "Script fails with error" [Medium,Confirmed]  https://launchpad.net/bugs/23160
[02:32] <ajmitch> fixing stuff
[02:32] <ajmitch> crimsun: poor sucker
[02:32] <imbrandon> lol bddebian
[02:32] <LaserJock> bddebian: is it fixed? :-)
[02:33] <bddebian> No but I'm not sure laptop-mode is even viable anymore
[02:33] <greff> crimsun: Who me?
[02:33] <bddebian> Hasn't been updated since Hoary apparently
[02:34] <crimsun> bddebian: my take is that you would want to ping mjg59 about it, and if he approves, then apply it
[02:35] <crimsun> it should be fixed, certainly, but he may have other plans
[02:35] <LaserJock> ajmitch: I'd hardly call https://beta.launchpad.net/~ajmitch/+packages doing nothing
[02:35] <crimsun> [unlikely, though, since it was demoted to universe releases ago]
[02:35] <ajmitch> LaserJock: all old
[02:35] <LaserJock> no it's not
[02:35] <ajmitch> is too
[02:35] <LaserJock> there's lots of Feisty stuff
[02:36] <LaserJock> yikes, https://beta.launchpad.net/~crimsun/+packages
[02:36] <LaserJock> look at all the Edgy stuff ^^
[02:36] <ajmitch> nothing important
[02:37] <sistpoty> ajmitch: your karma is much higher than mine... so either you really rock or I suck completely or both ;)
[02:37] <ajmitch> see, that's someone who does work
[02:37] <ajmitch> sistpoty: no, I just touched more bugs
[02:37] <bddebian> ajmitch has karma?
[02:37] <ajmitch> see, bddebian knows I don't do anything :)
[02:37] <bddebian> Bah ;-P
[02:38] <LaserJock> ajmitch has lots of karma
[02:38] <LaserJock> Fujitsu: hehe, I've almost had a few of those as well
[02:38] <crimsun> (look at geser's :)
[02:39] <tonyyarusso> Fujitsu: how's that happen?
[02:39] <LaserJock> bddebian: you have 4 times as much bug karma as I do so don't go telling me you are useless :p
[02:40] <Fujitsu> tonyyarusso: dpkg-dev kills a package build if you have `ubuntu' anywhere in your DEBEMAIL. I've been doing SRUs and security updates, so I don't want to change the maintainer field, so I unset DEBEMAIL.
[02:40] <Fujitsu> Running dch without DEBEMAIL set uses some insane default.
[02:40] <LaserJock> insane?
[02:40] <Fujitsu> william@localhost isn't exactly sane for a Debian upload.
[02:41] <sistpoty> I've once completely corrupted a changelog entry for not having DEBEMAIL set in a chroot... took me a while to figure what was going on there

[02:41] <LaserJock> that's not exactly insane
[02:42] <crimsun> but I want "crimsun@ponies" </whine>
[02:42] <LaserJock> your computer isn't named ponies?!?!
[02:42] <imbrandon> what about crimsun@iheartponies ?
[02:42] <crimsun> some insipid admin gave me "FUN" instead.
[02:43] <crimsun> what kind of hostname is "FUN"?!
[02:43] <imbrandon> lol
[02:43] <Fujitsu> crimsun: A fun one, of course.
[02:44] <crimsun> rejecting beryl* bugs seems to help ;)
[02:44] <LaserJock> lol
[02:44] <Fujitsu> ajmitch: How?
[02:44] <Fujitsu> crimsun: Probably.
[02:44] <ajmitch> massfile unmet deps bugs
[02:44] <ajmitch> just got a list of source packages with unmet deps
[02:44] <Fujitsu> Hah.
[02:44] <dsas> any idea why pbuilder would fail as it can't find the package when apt-get update has been ran and the package exists?
[02:44] <Fujitsu> It's about time to do that, ajmitch.
[02:44] <LaserJock> I'm wading through Launchpad bugs, I don't think that's really the "easy" way to get karma ;-)
[02:44] <imbrandon> pbuilder update also
[02:44] <crimsun> dsas: repo mismatch (is universe/multiverse enabled in pbuilder?)
[02:45] <ajmitch> Fujitsu: yes, thatnks for reminding me
[02:45] <ajmitch> Fujitsu: anything else that I've neglected for you?
[02:46] <sistpoty> I guess we should enable the merge web tool for feisty +1... get karma via merge bugs :)
[02:46] <dsas> crimsun: ubuntu/multiverse is enabled by default now isn't it? or doesn't pbuilder care about that?
[02:46] <crimsun> dsas: no, pbuilder does not enable either
[02:47] <sistpoty> hehe
[02:47] <dsas> crimsun: ok, i imagine it's probably that then.
[02:47] <dsas> thanks!
[02:49] <bddebian> LaserJock: I just move bugs around, I don't actually fix anything :-)
[02:49] <LaserJock> bddebian: still
[02:49] <LaserJock> my karma is pathetic, onl 500 for bugs :(
[02:50] <crimsun> I think jdong just earned himself a black mark!
[02:50] <LaserJock> mhm
[02:51] <LaserJock> automatic F
[02:51] <bddebian> Holy cow has mine dropped, sheesh
[02:51] <imbrandon> crimsun, hows that ?
[02:52] <LaserJock> whatever
[02:53] <imbrandon> i do almost have negitive karma, only 2k
[02:53] <imbrandon> ;)
[02:55] <crimsun> imbrandon: he was joking about uploading beryl ;)
[02:55] <imbrandon> ouch
[02:55] <imbrandon> yea thats one upload i wish i dident have on my /+packages
[02:56] <Fujitsu> imbrandon: We all make horrible, horrible mistakes.
[02:57] <crimsun> like, say, breaking the archive toolchain via an alsa-lib upload
[02:57] <crimsun> *whistles*
[02:57] <imbrandon> lol
[02:57] <Fujitsu> How'd you do that, crimsun?
[02:58] <crimsun> wrong /lib32 path for 64-bit arches
[02:58] <crimsun> broke gcc, which proceeded to kill compiles on 64-bit arches
[02:58] <crimsun> "FUN" indeed!
[02:58] <imbrandon> ouch
[02:58] <ajmitch> impressive
[02:59] <sistpoty> nothing too serious here... however I got 2 uploads to -updates rejected :)
[03:00] <ajmitch> that's nothing
[03:01] <sistpoty> yep, but I still find it a little bit ironic :)
[03:02] <ajmitch> :0:> wc -l source-unmet-deps.txt
[03:02] <ajmitch> 64 source-unmet-deps.txt
[03:02] <ajmitch> seems awfully low number of source packages
[03:03] <Fujitsu> ajmitch: That's about right, though I last checked a month or two ago.
[03:04] <ajmitch> oh well
[03:04] <ajmitch> 64 new bugs won't affect much
[03:05] <ajmitch> this was done on amd64, of course
[03:06] <ajmitch> 46 source-unmet-deps.txt
[03:06] <ajmitch> much less on i386
[03:10] <sistpoty> btw.: anyone got a clue what the amd64 toolchain changes have been for which doko did mass-uploads?
[03:11] <ajmitch> no idea
[03:11] <ajmitch> unless there was some change done on the buildds
[03:24] <sistpoty> ok, /me is off to bed now... gn8 everyone
[03:24] <crimsun> 'night.
[03:28] <Toadstool> re
[03:50] <crimsun> cd /tmp
[03:50] <crimsun> gah
[03:51] <bddebian> heh
[03:54] <LaserJock> hmm, we need a whole Kubuntu bug week?
[04:17] <crimsun> I guess I should make that pbuilder/gdebi change
[04:17] <crimsun> since, well, waiting four hours for a vlc build doesn't particularly strike my fancy even if I do have a case of beer
[04:20] <crimsun> imbrandon: have you made that change on your build farm?
[04:20] <Toadstool> is it really worth it in terms of speed? 'cause I'm reluctant to clutter my chroot with x related packages... unless it only requires gdebi-core...
[04:20] <Toadstool> am I thinking aloud? :p
[04:21] <imbrandon> crimsun, the pbuilder thing ?
[04:21] <crimsun> imbrandon: yes
[04:22] <imbrandon> crimsun, no because it required a shitton of backports, wasent sure it was worth it
[04:22] <crimsun> k
[04:22] <imbrandon> and i realy dident wanna run the buildd's on feisty
[04:22] <crimsun> wussy
[04:22] <imbrandon> hehe
[04:22] <crimsun> nevermind the fact that my machines all run breezy  *whistles*
[04:22] <imbrandon> ;)
[04:24] <LaserJock> hmmm?
[04:25] <LaserJock> oh, because you need gdebi from Feisty?
[04:25] <imbrandon> yea and it requires a bunch of other stuff
[04:25] <imbrandon> because its all versioned so tight
[04:27] <LaserJock> I guess I've just gotten used to running Feisty on everything :/
[04:27] <LaserJock> hmm
[04:28] <crimsun> if it weren't for quilt push -a and quilt new, I dunno what I'd do
[04:28] <LaserJock> I wonder if it'd be worth setting up a repo on tiber for backporting MOTU stuff
[04:28] <crimsun> I already do that
[04:28] <LaserJock> and setting up various MOTU tools
[04:29] <crimsun> I pretty much login, pbuilder-release update, and build away
[04:29] <crimsun> log in, even
[04:29] <LaserJock> log in where?
[04:29] <crimsun> tiber.
[04:29] <imbrandon> tiber has builders too LaserJock
[04:29] <LaserJock> oh, you build on tiber?
[04:29] <LaserJock> I know
[04:30] <imbrandon> just x86 though
[04:30] <crimsun> I pretty much have to
[04:30] <LaserJock> I just didn't know anybody used them
[04:30] <crimsun> this machine is far too slow to be useful
[04:30] <crimsun> (this was before the advent of ubuntuwire, btw)
[04:30] <imbrandon> ;)
[04:30] <LaserJock> I honesty don't understand how you get all the stuff done you do crimsun
[04:31] <LaserJock> crimsun: what do you use quilt for?
[04:31] <crimsun> it's an illusion. I have ponies do all the grunt work.
[04:31] <LaserJock> ah
[04:31] <crimsun> oh wait, I just gave away my sekrit
[04:31] <tonyyarusso> ubuntu?wire
[04:31] <crimsun> LaserJock: vlc's patchsys
[04:31] <LaserJock> oh
[04:32] <imbrandon> tonyyarusso, the community build network
[04:32] <tonyyarusso> ah, didn't know it had a name
[04:33] <imbrandon> tonyyarusso, well i guess it does now hehe all the hostnames are *.ubuntuwire.com ;)
[04:33] <tonyyarusso> right
[04:33] <crimsun> dpkg-source: error: file vlc_0.8.6.release.orig.tar.gz has size 647168 instead of expected 16866386
[04:33] <crimsun> oooops.
[04:33] <imbrandon> nice
[04:38] <ajmitch> crimsun: why would you still run breezy?
[04:38] <crimsun> ajmitch: things that break are known
[04:39] <bddebian> heh
[04:39] <crimsun> I fully except my next laptop to run feisty out of the box
[04:39] <crimsun> expect, too
[04:39] <ajmitch> I guess it's only us part-time hackers that run the latest
[04:39] <bddebian> :-)\
[04:39] <tonyyarusso> what lappy crimsun ?
[04:40] <crimsun> tonyyarusso: I'd like an IBM/Lenovo, but I don't know atm.
[04:40] <tonyyarusso> crimsun: I have a T43p
[04:41] <imbrandon> mbp ftw
[04:41] <crimsun> I've seen Ubuntu run on a T43p ;)
[04:41] <tonyyarusso> Only things not ootb: winmodem (linuxant driver works), good 3D accel on ATI card (it kinda works for now)
[04:42] <crimsun> I think right about the release of 6.06, I gave an installfest presentation and thanked deity for the alt installer I had burned
[04:42] <crimsun> feisty's desktop installer is so far beyond that one
[04:42] <crimsun> (6.06's ubiquity, that is)
[05:31] <LaserJock> do ['s mean something in a regex?
[05:33] <Toadstool> yup, [abc]  means "either a, b or c"
[05:35] <LaserJock> doh, I know that
[05:35] <Toadstool> :)
[05:36] <LaserJock> I can't believe I did that :-)
[05:38] <Toadstool> er... is LP supposed to close bugs automagically when I put LP: #xxxx in a changelog?
[05:38] <poningru> zomg that would crazy
[05:38] <LaserJock> I don't think so yet
[05:38] <LaserJock> but that's the plan
[05:38] <LaserJock> Toadstool: did you have one do that?
[05:39] <Toadstool> nope, just asking
[05:39] <Toadstool> I wish it did :)
[05:39] <LaserJock> I'm using that for when it does work
[05:40] <Toadstool> yep, at least the Launchpad-Bugs-Fixed field is correctly set in my .changes so I guess I am not doing anything wrong :)
[05:41] <LaserJock> cool
[05:41] <LaserJock> I guess that part is working
[05:44] <Toadstool> woohoo! bugs count -= 3
[05:45] <LaserJock> \o/
[05:45] <Toadstool> I've done like 100 times more Ubuntu stuff in 1hour thant in 2 months... I need a beer :)
[05:45] <Toadstool> *than eve
[05:46] <Toadstool> even
[05:46] <Toadstool> pff, I can't type
[05:48] <LaserJock> hehe
[07:02] <Toadstool> uhuh :)
[07:03] <LaserJock> Fujitsu: other than being redundant, I can't think of any really
[07:04] <Fujitsu> Redundant? It would be properly searchable!
[07:04] <Fujitsu> And wouldn't have to have an incredibly slow web interfac.
[07:04] <Fujitsu> But it'd have to be read-only.
[07:04] <Fujitsu> There goes that idea.
[07:05] <Toadstool> of course it would be convenient to have some kind of interface with the database (like bts2ldap with the Debian BTS)...
[07:05] <LaserJock> Fujitsu: well, it's not that bad of an idea
[07:05] <nixternal> LaserJock: thanks!
[07:07] <LaserJock> nixternal: for what?
[07:08] <nixternal> heh, leaving that guy hanging for me to get caught up in
[07:08] <Toadstool> LaserJock: we don't need a reason to thank you, you're a MOTU deity :)
[07:09] <nixternal> hehe
[07:09] <LaserJock> lol
[07:09] <LaserJock> I really don't think so
[07:11] <Fujitsu> Toadstool: XML-RPC is scheduled for post-1.0, so it's probably not more than a couple of years away.
[07:11] <Toadstool> haha
[07:12] <Toadstool> it's been postponed like a million times right? :)
[07:12] <Toadstool> (xml-rpc)
[07:12] <Fujitsu> Soyuz 1.0 was scheduled for early last year, everything was meant to be 1.0 in early October last year.
[07:12] <Fujitsu> Ah.
[07:13] <Fujitsu> Well, I think they've always responded `later'.
[07:13] <Fujitsu> They've been saying that for 2 years now.
[07:13] <Toadstool> true
[07:14] <LaserJock> 1.0 should be pretty soon, unless there are more delays
[07:15] <LaserJock> after 1.0 I"m told xml-rpc will be the/a big push
[07:15] <Fujitsu> LaserJock: `pretty soon' is rather relative.
[07:15] <Fujitsu> Ah, that sounds more promising.
[07:15] <LaserJock> well, I've heard within the month
[07:15] <Fujitsu> Then we just have to write nice tools to work with it.
[07:15] <Fujitsu> Really!?
[07:15] <Toadstool> that'd be awesome
[07:15] <LaserJock> well, I'm not saying anything definite
[07:15] <Fujitsu> beta is looking pretty nice.
[07:16] <LaserJock> but it sounds definately soonish
[07:16] <Fujitsu> OK.
[07:16] <LaserJock> I've been trying to get down what exactly we can expect for Feisty+1
[07:16] <Fujitsu> Then they've just got another 2000 bugs to fix.
[07:17] <Toadstool> (uhuh, running out of beer)
[07:17] <nixternal> Ubuntu 7.10 "The Goofy Goose" Release?
[07:17] <Fujitsu> LaserJock: What's on the Feisty+1 list so far?
[07:18] <Fujitsu> nixternal: It might be `H[a-z] + h[a-z] +', you know...
[07:18] <LaserJock> Fujitsu: 1.0
[07:18] <LaserJock> Fujitsu: perhaps PPA
[07:18] <LaserJock> not sure
[07:18] <Toadstool> PPA?
[07:18] <LaserJock> XML-RPC will get hopefully a lot of love
[07:18] <LaserJock> Personal Package Archives
[07:18] <Toadstool> oh
[07:18] <nixternal> Ubuntu 7.10 "The Hairy Hamster"
[07:19] <Fujitsu> XML-RPC will make Malone almost production-standard, IMO.
[07:19] <Toadstool> am I the only one to think that XML-RPC should get higher priority than PPA?
[07:19] <Fujitsu> Toadstool: No. Definitely not.
[07:21] <Fujitsu> A lack of PPA is easy to workaround, whereas XML-RPC is practically impossible.
[07:21] <Toadstool> agreed
[07:22] <LaserJock> well, PPA will be used by the vast LP users
[07:22] <LaserJock> xml-rpc is only helpful for a minority
[07:23] <Fujitsu> But XML-RPC is a whole lot more helpful to those people. XML-RPC provides something that simply cannot be done (without excessive screen-scraping and LP-overloading) now. PPA can be done right now.
[07:23] <Fujitsu> But anyway, I believe that PPA is pretty much finished.
[07:24] <Toadstool> which is good, devs will have more time to focus on more important things *evil grin*
[07:25] <Fujitsu> Yeah, like the new UI, which is even slower than old one! Hooray!
[07:25] <poningru> is ntfs-config supposed to be in universe?
[07:25] <poningru> cause its not in edgy
[07:26] <Fujitsu> It's new in Feisty.
[07:26] <poningru> Fujitsu: are you talking to me?
[07:27] <Fujitsu> poningru: Yep.
[07:27] <poningru> Fujitsu: all the docs in help.ubuntu.com say install ntfs-config but that package isnt available in edgy
[07:27] <poningru> even though the docs say they should be
[07:30] <Fujitsu> I'm sure it's new in Feisty.
[07:30] <poningru> it is
[07:30] <Fujitsu> !info ntfs-config edgy
[07:30] <ubotu> Package ntfs-config does not exist in edgy
[07:34] <imbrandon> re
[07:36] <imbrandon> hum if i did nfs /home and some scriptfoo and some apache magic i could probably make a motu only ppa :)
[07:36] <imbrandon> if only there was more hours in the day
[07:37] <LaserJock> hmm
[07:38] <Toadstool> imbrandon: when I wake up in the morning, my first thought is "if only there were more hours in the night"... I guess it's somehow related ;)
[07:38] <imbrandon> sleep is for the weak ;)
[07:38] <LaserJock> I ended up getting access to all the LP private bugs :/
[07:39] <LaserJock> oops
[07:39] <imbrandon> LaserJock, thats what you get for becomming a LP bug contact ;)
[07:39] <LaserJock> apparently
[07:39] <LaserJock> I was supposed to just get aces to the non-private bugs
[07:39] <LaserJock> but apparently LP doesn't know that
[07:39] <Toadstool> imbrandon: I am definitely weak (and definitely drunk tonight too)
[07:40] <Fujitsu> Security Contact should have access to the private ones... Unless Launchpad Bugs is subscribed directly to them.
[07:40] <Fujitsu> GAH.
[07:40] <Fujitsu> LP has exploded!
[07:40] <Toadstool> what did you do?! :)
[07:40] <Fujitsu> OperationalErrors!
[07:40] <Toadstool> ouch
[07:41] <Fujitsu> And it's the weekend too.
[07:41] <LaserJock> so now I've left the team until they figure it out
[07:42] <imbrandon> you left just bacause of that? it might have been intentional
[07:42] <imbrandon> heh
[07:42] <Fujitsu> imbrandon: I'm not they'd like LaserJock having access to their code....
[07:43] <imbrandon> Fujitsu, sure anyone can have access , as long as you sign a nda :)
[07:43] <imbrandon> ;)
[07:43] <Fujitsu> That's probably just a friendly-seeming front.
[07:43] <imbrandon> nah i know one or two non-employees that have the code
[07:43] <Fujitsu> I've left most of my PHP skills behind. I'm glad of it.
[07:44] <imbrandon> easy to do when your 16 , not using it for 16 years ;)
[07:44] <LaserJock> imbrandon: I tried getting access to the LP wiki and was denied
[07:44] <LaserJock> it's pretty much the same thing
[07:44] <imbrandon> ouch
[07:45] <Fujitsu> As I said... It's a risk they're unlikely to take, even with an NDA.
[07:45] <Toadstool> Fujitsu: I totally banned PHP from my own servers/machines/whatever :)
[07:45] <Fujitsu> Toadstool: I never allowed it on them :)
[07:45] <Toadstool> hehe
[07:45] <imbrandon> Toadstool, thats about as ignorant as the comment you made on your blog
[07:46] <Fujitsu> imbrandon: I agree. It's not at all ignorant!
[07:46] <LaserJock> guys
[07:46] <imbrandon> why ? because you dont like it ? or do you have a valid reason hehe
[07:47] <Fujitsu> imbrandon: It's insecure. It's slow... It's not thread-safe... There are some horrible things written in it... The mish-mash of code and presentation is revolting...
[07:49] <imbrandon> thats all about the things that are written in it, nothing about the core its self
[07:49] <Toadstool> imbrandon: don't get me wrong about the KDE4 stuff. My blog post is just what I felt like with the little information the Kubuntu team provided on<EMAIL_ADDRESS>I am sorry if it looks offensive. Might be a language issue
[07:49] <imbrandon> the same can be said for perl,python, and just about any scripting lang
[07:50] <Toadstool> next time I'll think a million times before posting something similar
[07:50] <Fujitsu> In Dapper:
[07:50] <Fujitsu> php5 5.1.2-1ubuntu3.6
[07:50] <imbrandon> Toadstool, everyone is entitled to their own opinion but you should have 1) objected when the spec was approved 2) replied in the medum it was presented in ( email ) even if you also bloged aobut it
[07:51] <Fujitsu> 6 security fixes (some of them being multiple vulnerabilities) in 10 months? That must be the most secure thing EVER!
[07:52] <imbrandon> 6 security fixes is minor imho, look at the linux kernel its self in that saem timeframe, and php runs on more systems
[07:52] <imbrandon> Fujitsu, it was approved at UDS
[07:53] <Fujitsu> The last security update fixed 6 CVEs, most of which were code-execution flaws.
[07:53] <imbrandon> and?
[07:54] <Fujitsu> I've not seen such an impressive record of flaws in Python or Perl.
[07:54] <Toadstool> oh crap, yet another php sux0r never-ending discussion ;)
[07:54] <imbrandon> perl had just as many when it was king of the web, and python isnt scruntinized as much because it isnt used as widely on the web
[07:55] <imbrandon> perl actualy had/has more tbh
[07:55] <imbrandon> without looking
[07:55] <imbrandon> perl is probably THE most insecure web lang, it wasent ment to be used for web, it was adapted to it, like python is now
[07:58] <Toadstool> good ol' days, eh? :)
[08:09] <imbrandon> nixternal, are you going to cherry pick the security update for ktorrent for breezy/dapper/edgy ?
[08:12] <nixternal> I could if needed
[08:12] <imbrandon> looks like your the man if your up for it
[08:12] <imbrandon> if you need a sponsor when done feel free to poke me
[08:13] <nixternal> with a size 12 boot :)
[08:13] <imbrandon> lol
[08:13] <nixternal> I think I just heard arms to platter noises coming from my other box
[08:13] <imbrandon> http://www.imbrandon.com/misc/music/jonobacon/jonobacon-reflections.ogg     , needs to be the startup sound for my kubuntu boxen
[08:13] <nixternal> heh
[08:15] <Toadstool> :)
[08:17] <Fujitsu> Bugs about initrd-tools can be swiftly killed, can't they?
[08:18] <crimsun> probably the same category as laptop-mode. They're still valid bugs but much lower priority than their replacements.
[08:19] <Fujitsu> initrd doesn't work with modern kernels, so it can't be valid any more.
[08:20] <crimsun> well, it won't be valid for our default kernel(s), true, but we do have to consider that people might want to run 2.[24]
[08:39] <Fujitsu> Do we have a standard tag for .desktop-addition bugs yet?
[08:40] <LaserJock> .desktop-addition?
[08:43] <Fujitsu> Yes... Bugs that just request the addition of a .desktop.
[08:44] <LaserJock> ohh
[08:44] <LaserJock> that would be a good one
[08:44] <Fujitsu> More useful when we can search for an absence of tags.
[08:45] <LaserJock> heh, I saw that LP bug
[08:46] <Fujitsu> As did I.
[08:46] <Fujitsu> I immediately subscribed.
[08:47] <LaserJock> man, and I went through all that trouble to set up my email for LP bugs
[08:47] <LaserJock> spent a whole day figuring that out
[08:48] <Fujitsu> I'd love to be able to search for something with tags like `!desktop !upgrade', and get some real, fixable bug listings.
[08:49] <imbrandon> LaserJock, ever get the recipe for procmail ?
[08:49] <imbrandon> i seen the request after you were offline
[08:49] <imbrandon> but i have one
[08:49] <LaserJock> imbrandon: well, it took a combination of figuring out how to get the mail *to* procmail (I have cpanel on the server) and then gettting .procmail
[08:49] <LaserJock> but I got it in the end
[08:50] <imbrandon> ;)
[08:50] <LaserJock> I had some stupid regex
[08:50] <LaserJock> but I figured it out eventually
[08:54] <Fujitsu> I like bug #89199. Very pleasant.
[08:55] <Ubugtu> Malone bug 89199 in mysql-admin "User admin & Restore both crash or lockup Mysql Admin." [Undecided,Confirmed]  https://launchpad.net/bugs/89199
[08:55] <Fujitsu> And it's a dupe too.
[09:44] <nixternal> imbrandon: you still around?
[09:45] <nixternal> imbrandon: http://nixternal.com/pkg/ktorrent/edgy/ktorrent_edgy.debdiff
[09:45] <nixternal> there is the Edgy debdiff for KTorrent to fix the security issue
[09:46] <nixternal> I will do Dapper and Breezy tomorrow. I am gonna go crash
[09:47] <imbrandon> nixternal, cool, thanks, sleep well
[09:48] <nixternal> will try/do
[10:01] <Fujitsu> imbrandon: Can you please work your core-dev magic on bug #42564?
[10:01] <Ubugtu> Malone bug 42564 in trac "Upgrade to Trac 0.9.5 for dapper (security fixes)" [Medium,Fix released]  https://launchpad.net/bugs/42564
[10:12] <Fujitsu> Nafallo: When you're around... What do you think about disabling mp3lib in mplayer? I don't think there's any other solution at the moment.
[10:13] <Nafallo> Fujitsu: why? I enabled it because of a bugreport. It still doesn't work?
[10:23] <Fujitsu> Nafallo: Haven't you seen the bug? (bug #85751)
[10:24] <Ubugtu> Malone bug 85751 in mplayer "Distorted MP3 sound" [Undecided,Confirmed]  https://launchpad.net/bugs/85751
[10:24] <Nafallo> I have a mailbacklog from hell on most lists :-P
[10:24] <Fujitsu> Ah.
[10:32] <Nafallo> Fujitsu: I could revert mp3lib and add mad again...
[10:32] <Fujitsu> Nafallo: I think we'll have to.
[10:32] <imbrandon> Fujitsu, done ( sorry a bit slow atm, firefighting at work
[10:32] <imbrandon> few 2650's decided to die
[10:32] <Nafallo> Fujitsu: I don't want to rely entirely upon ffmpeg though :-)
[10:33] <Fujitsu> imbrandon: Thanks! No problem with the slowness :)
[10:33] <Fujitsu> Nafallo: Better to have it actually working, though.
[10:33] <Nafallo> yea :-)
[10:33] <Fujitsu> Gah.
[10:34] <Fujitsu> keescook: Your last two security updates to mplayer in Feisty should really have gone into bzr.
[10:35] <Nafallo> oh. the branch is outdated?
[10:35] <imbrandon> no more source packages spec failed miserably
[10:35] <imbrandon> hehe
[10:35] <Nafallo> thanks for the hint :-P
[10:36] <Fujitsu> Nafallo: If you're going to make another release, it'd be advisable to add XS-Vcs-Bzr (or whatever it is)
[10:36] <Nafallo> Fujitsu: got any docs on that? :-)
[10:36] <imbrandon> personaly i stoped using bzr on lp for packages because it becomes out of date quicky if people dont use it ( most dont check unfortunately ) and 2) you cant delete branches
[10:37] <Fujitsu> Nafallo: Just put something like `XS-Vcs-Bzr: http://launchpad.net/~ubuntu-dev/mplayer/ubuntu' in debian/control.
[10:38] <Fujitsu> crimsun: What would you do that for?
[10:38] <crimsun> pkgmaintainermangler: Error: debian/vlc-plugin-alsa/DEBIAN/control already contains an Original-Maintainer field; aborting
[10:38] <Nafallo> okidoki :-)
[10:38] <Fujitsu> imbrandon: Branch deletion is being worked on at the moment (I saw people talking about it 12 hours ago).
[10:38] <imbrandon> Fujitsu, nice
[10:38] <Fujitsu> imbrandon: There is also a junk product for putting useless branches on.
[10:38] <imbrandon> would have been good 6 months ago when i gave up on bzr in lp
[10:39] <crimsun> I think I just hit a pkgmaintainermangler bug
[10:39] <Fujitsu> crimsun: Probably. It's not exactly bug-free.
[10:40] <Fujitsu> It'd be nice if LP would eventually check for the existence of XS-Vcs-Bzr, and reject the upload if it hasn't been pushed.
[10:40] <imbrandon> crimsun, possibly, i dont like it much at all anyhow, i think it should warn not error imho
[10:40] <Fujitsu> imbrandon: That's different...
[10:40] <imbrandon> ?
[10:40] <Fujitsu> crimsun: That's the binary-mangler on the buildds, isn't it?
[10:41] <Fujitsu> imbrandon: You're complaining about the dpkg-dev change, are you not?
[10:41] <imbrandon> yea
[10:41] <crimsun> imbrandon: well, I can live with the dpkg-dev side, but every last build of vlc just FTBFS on pkgmaintainermangler
[10:41] <imbrandon> nice
[10:42] <crimsun> +Maintainer: MOTU Media Team<EMAIL_ADDRESS>[10:42] <crimsun> +XSBC-Original-Maintainer: Sam Hocevar (Debian packages<EMAIL_ADDRESS>[10:42] <crimsun> looks ok to me, nay?
[10:42] <Fujitsu> crimsun: Yep.
[10:42] <imbrandon> yea
[10:42] <crimsun> oh well, I'll bug pitti on Monday
[10:43] <Fujitsu> I can see why it's doing it... But it should have affected other packages.
[10:43] <imbrandon> btw wth is XS*- ?
[10:43] <Fujitsu> imbrandon: X = extended. S = put in .dsc. B = put in DEBIAN/control in .deb.
[10:44] <Fujitsu> And I'm not sure about the C bit.
[10:44] <Fujitsu> Changes, perhaps.
[10:44] <supervillain> Hello, I'm trying to build squid-prefetch, but I got "cp: cannot stat `debian/{postinst,prerm,postrm}': No such file or directory"
[10:44] <Fujitsu> supervillain: That is one of the dreaded bashisms. *jarring chord*
[10:44] <crimsun> ls -l /bin/sh
[10:44] <imbrandon> bashism in rules ?
[10:45] <crimsun> yes, {,} is a bashism
[10:45] <supervillain> how do I convert it to dash?
[10:45] <crimsun> e.g., list them separately
[10:46] <imbrandon> change debian/{postinst,prerm,postrm} to debian/postinst \n debian/prerm \n etc etc etc
[10:47] <supervillain> any reason why squid don't have visible_hostname checker in postinst? Since, most of the people when squid install, it's asking to use visible_hostname $HOSTNAME
[10:47] <Fujitsu> crimsun: Your vlc upload must be the first one to use a non-*ubuntu* new maintainer since dpkg-dev started enforcing the new rules
[10:47] <crimsun> Fujitsu: that's what it looks like
[10:49] <supervillain> thanks for the bashism tip.
[03:25] <bddebian> Heya
[03:27] <lionel> hi bddebian
[03:28] <bddebian> Hello lionel
[04:19] <imbrandon> ajmitch, ping
[04:19] <imbrandon> ( or any other mono packagers arround )
[04:42] <nixternal> imbrandon: you get a chance to check out that debdiff? Would it be easier to create a security bug for this, and then attach my debdiffs to them?
[04:44] <keescook> nixternal: sure, it could help coordination.  I can check them/upload them too.
[04:44] <imbrandon> nixternal, yes
[04:44] <imbrandon> heya keescook
[04:44] <imbrandon> brbr afk
[04:44] <keescook> hiya imbrandon
[04:57] <nixternal> keescook: is there a recommended way of creating the bug that you would like to see?
[04:58] <keescook> nixternal: the "fullest" way to do it would be to fill it out like normal, then link the CVEs, and flag it as security.
[04:58] <nixternal> roger
[04:58] <keescook> then attach the debdiffs, and if it's in universe, subscribe motu-swat
[04:58] <nixternal> hrmm, I wonder if they even created CVEs for it
[04:59] <keescook> nixternal: I can go hunt those down (or get them assigned) too.  what package is it again?
[04:59] <nixternal> ktorrent
[04:59] <keescook> right!  :)
[05:00] <keescook> once I see the debdiffs, I should be able to find/request a CVE
[05:00] <nixternal> I have one debdiff, let me link you really quick
[05:01] <nixternal> http://nixternal.com/pkg/ktorrent/edgy/ktorrent_edgy.debdiff
[05:02] <keescook> cool.  was there a KDE news item about this?  (also, for changelogs, check out the templates and versioning styles here: https://wiki.ubuntu.com/SecurityUpdateProcedures )
[05:02] <nixternal> it isn't a very serious security issue, but from what I seen code wise, they ensure that the chunk file isn't corrupted, and then with versions <2.1.2 .. in the filename was allowed
[05:02] <nixternal> http://lists.kde.org/?l=kde-announce&m=117346514411140&w=2
[05:02] <nixternal> just the announcement
[05:03] <nixternal> so someone could name or place a file in a torrent and have it write to ../../foo/bar/, so unless they were root it wouldn't wipe system files, but it could damage user configuration files
[05:03] <keescook> eewww.  yeah, hadn't seen that before.  I'll request a CVE.
[05:03] <nixternal> rock on!
[05:04] <nixternal> I will do the Dapper and Breezy debdiffs here shortly
[05:04] <keescook> where did you get the patch from?  I'm trying to get a "fuller" description that I can use for the CVE request.  was anything useful in the svn commits?
[05:05] <nixternal> nothing, the svn commit comments say the same exact thing as the ML did
[05:06] <keescook> "security issue" heh.
[05:06] <keescook> so, the ".." is obvious to me, but any idea what the 2nd vulns was?
[05:06] <nixternal> myself and jdong already told them they need better changelogs because they  make it tough for us to get it fixed and accepted
[05:06] <nixternal> keescook: your guess is as good as mine on the other ones
[05:06] <keescook> good call.  :)
[05:06] <keescook> heh
[05:06] <nixternal> let me link you to the svn comments
[05:07] <nixternal> http://websvn.kde.org/trunk/extragear/network/ktorrent/libktorrent/torrent/
[05:07] <nixternal> chunkcounter.cpp, peer.cpp, and torrent.cpp
[05:07] <nixternal> haha
[05:07] <nixternal> Fix 2 security vulnerabilities, both were discovered by Bryan Burns of Juniper Networks
[05:07] <nixternal> lovely
[05:11] <keescook> nixternal: so, for example, especially since there isn't a CVE for this yet, in the References section of the changelogs, add the upstream changeset URL:
[05:11] <keescook> http://websvn.kde.org/?view=rev&revision=640661
[05:12] <keescook> oh! I see the problem, idx could be negative (DoS, heap corruption)
[05:12] <nixternal> oh ya, didn't even catch that with the -- cnt
[05:12] <keescook> yeow, or too big.
[05:13] <imbrandon> hum whats the sru policy on "just needs a rebuild" ?
[05:13] <keescook> imbrandon: dunno, good question.
[05:15] <imbrandon> heh
[05:15] <teardrop> hellow
[05:16] <tsmithe> hi
[05:17] <imbrandon> hello teardrop
[05:17] <teardrop> i need help to configure mi wirelees
[05:17] <teardrop> who can help me plz
[05:17] <imbrandon> teardrop, #ubuntu is for general support
[05:17] <teardrop> yeah but i need onli numbers of directions ip that
[05:22] <nixternal> keescook: that main.cpp file only adds recognition to the guy who found it, I don't need to add that to the patch as well do I?
[05:23] <keescook> nixternal: correct, I'd prefer it's left out to make the patch smaller.  :)
[05:23] <nixternal> seeing as that isn't part of the security issue :)
[05:23] <nixternal> whew, good :)
[05:23] <keescook> right.  :)
[05:24] <nixternal> * debian/patches/kubuntu_02_security_fix.diff - http://websvn.kde.org/?view=rev&revision=640661
[05:24] <nixternal> that is what I added to the changelog, cool?
[05:24] <nixternal> add a quick explanation as well?
[05:25] <keescook> right, see the SUP url I pasted earlier.  there's a template in there
[05:25] <nixternal> err, ya I am looking dead at it ;)
[05:25] <keescook> oh! heh
[05:26] <keescook> so usually I'll put the svn changeset into References, and just say "backported upstream fix" for the patch line
[05:26] <nixternal> OK
[05:27] <keescook> let me know when you've got the bug report ready, and I'll link to it for the CVE request email I'm writing.
[05:28] <nixternal> let me do that now
[05:28] <teardrop> any speack spanish can help me :( plz
[05:29] <tsmithe> !es > teardrop
[05:29] <dsas> is the process to get a debdiff reviewed and uploaded simply "assign bug to motureviewers" ?
[05:32] <Adri2000> dsas: assign to ubuntu-universe-sponsors ;)
[05:32] <Adri2000> and hi everyone :)
[05:32] <keescook> hiya Adri2000
[05:33] <dsas> Adri2000: in that case https://wiki.ubuntu.com/MOTU/Bugs is out of date.
[05:36] <lionel> hi Adri2000 !
[05:36] <Adri2000> hey lionel :)
[05:36] <dsas> I just fixed it :)
[05:36] <Adri2000> dsas: ok, cool :
[05:36] <Adri2000> :)
[05:38] <nixternal> keescook: bug 91174
[05:38] <Ubugtu> Malone bug 91174 in ktorrent "KTorrent security issue with releases <2.1.2 (Breezy - Feisty)" [Undecided,Unconfirmed]  https://launchpad.net/bugs/91174
[05:38] <keescook> nixternal: cool!  thanks.
[05:44] <nixternal> keescook: I will put some debdiffs up there in a few. I need to redo the Edgy debdiff to be a .1 revision in the changelog as well as fix the Maintainer to Core Dev and not MOTU
[05:44] <keescook> nixternal: cool, thanks.
[05:46] <imbrandon> keescook, write me a howto on setting it up and i'll get them going on the community build machines ;)
[05:46] <nixternal> imbrandon: haha, I was going to say the same thing, but to use locally :)
[05:47] <keescook> imbrandon: https://help.ubuntu.com/community/SbuildLVMHowto
[05:47] <imbrandon> http://www.imbrandon.com/hello.aspx
[05:47] <keescook> nixternal: you made a 2nd bug?
[05:48] <nixternal> huh?
[05:48] <nixternal> I made one boog
[05:48] <keescook> https://launchpad.net/bugs/91174 just appeared too
[05:48] <Ubugtu> Malone bug 91174 in ktorrent "KTorrent security issue with releases <2.1.2 (Breezy - Feisty)" [Undecided,Unconfirmed]
[05:48] <nixternal> hrmm
[05:48] <nixternal> interesting
[05:48] <keescook> imbrandon: the important bit is http://people.ubuntu.com/~kees/scripts/mk-sbuild-lv.sh
[05:48] <nixternal> beta.lp boog?
[05:49] <keescook> that script does everything  :)
[05:49] <imbrandon> keescook, rockin
[05:50] <imbrandon> apache2 rocks , aspx , php , python , perl all on the same website ;)
[05:50] <nixternal> keescook: that is odd. I will just reject 74 and leave 72 open since you started working on it :)
[05:50] <keescook> nixternal: okay, cool.
[05:51] <nixternal> done
[05:53] <keescook> nixternal: aagh.  I sent the 91174 for the CVE request.  I'll dup it and go back to using 91172.
[05:53] <nixternal> lol
[05:53] <nixternal> I apologize for my double post (finger fumbling)
[05:54] <keescook> if I could type/read, I'd be dangerous
[05:54] <nixternal> same here :)
[05:54] <nixternal> KTorrent devs need to learn how to "document" properly
[05:54] <nixternal> jeesh, you have to trace everything back just to figure out what it "could" be
[06:00] <nixternal> edgy fix attached
[06:01] <keescook> heh, 91174 is the "primary" now.  sorry I messed that all up.
[06:02] <nixternal> hahaha
[06:58] <keescook> nixternal: we've got CVEs.  :)  CVE-2007-1384 CVE-2007-1385 (they'll be visible after they sync)
[07:04] <_MMA_> Hey guys. How does the versioning on packages work for bug fixes?
[07:04] <_MMA_> I have to fix something in the ubuntustudio metas.
[07:05] <ivoks> what's the actual version?
[07:05] <ivoks> and what ubuntu release?
[07:06] <ivoks> which
[07:06] <_MMA_> .1 Feisty
[07:06] <ivoks> .1?
[07:06] <ivoks> whole version
[07:06] <_MMA_> Thats what we made it.
[07:06] <ivoks> ubuntustudio-audio_0.1
[07:06] <_MMA_> joejaxx: ping
[07:07] <ivoks> then it's ubuntustudio-audio_0.2
[07:07] <ivoks> you can add additional changes and then release it
[07:07] <_MMA_> And for a bug-fix thats fine?
[07:07] <joejaxx> ok
[07:08] <ivoks> yes
[07:08] <_MMA_> Ok. Thanx.
[07:09] <joejaxx> ivoks: thanks
[07:09] <ivoks> np
[07:58] <pirast> could anyone please apply the debdiff in bug 90814?
[07:58] <Ubugtu> Malone bug 90814 in asterisk "[UPLOAD]  New Asterisk release 1.2.16" [Undecided,Confirmed]  https://launchpad.net/bugs/90814
[08:04] <rdw200169> Ubuntu is dying for an easy to use firewall app...  that works
[08:05] <rdw200169> Is there any work being done to replace Firestarter for ease of use and functionality?
[08:07] <Laser_away> well, I don't know of any. But you could ask the Firestarter people about features
[08:07] <pirast> rdw200169, why use a firewall? or for what?
[08:07] <pirast> rdw200169, ubuntu comes with a no ports open policy, at least for edgy afaik
[08:08] <Laser_away> pirast: there first thing a lot of people do is open up a bunch of ports ;-)
[08:08] <Laser_away> *the
[08:09] <pirast> mhm k thats right
[08:10] <ivoks> it's not
[08:10] <ivoks> what ports do people open?
[08:10] <rdw200169> exactly
[08:11] <Laser_away> printing, avahi
[08:11] <ivoks> last thing i want is tome sort of norton firewall that doesn't work
[08:11] <ivoks> or makes any communication impossible
[08:11] <Laser_away> I suppose a fair amount end up laying with ssh, http, ..
[08:11] <Laser_away> s/laying/playing/
[08:12] <ivoks> people who install web server should know what they are doing :)
[08:12] <rdw200169> yup
[08:12] <ivoks> i have web server and is open :)
[08:12] <rdw200169> but isn't the goal of ubuntu to make things easy?
[08:12] <rdw200169> OS X makes it very easy
[08:12] <ivoks> rdw200169: yes, it is...
[08:12] <rdw200169> and i think ubuntu should too
[08:13] <ivoks> rdw200169: do you use firewall on osx?
[08:13] <rdw200169> but still be, overzealously, secure
[08:13] <rdw200169> absolutely
[08:13] <ivoks> for what?
[08:13] <ivoks> firewall on osx is close/open
[08:14] <ivoks> it's better to have services listen on localhost, don't you think?
[08:14] <rdw200169> i'm a firewall junkie, running a linux router as an ISP for 25 users currently
[08:14] <ivoks> hehe i'm running firewalls for >300 users :)
[08:15] <rdw200169> yes, but you have to turn on services to allow ssh, etc...
[08:15] <ivoks> i agree
[08:15] <rdw200169> not if you want to run a samba share, or ftp, whatever, locally
[08:15] <rdw200169> i wish..
[08:15] <ivoks> where's the logic in opening ssh but then firewalling it?
[08:16] <ivoks> this is how OSX does it
[08:16] <ivoks> it's open or closed
[08:16] <rdw200169> i'm in iraq right now, providing internet for some of my peers, for a price of course
[08:16] <Laser_away> ivoks: the idea is you can use the firewall and only open what you need
[08:17] <Laser_away> some people will use it, others won't
[08:17] <Laser_away> but it seems like a nice tool to have
[08:17] <Laser_away> I think especially in the future
[08:17] <ivoks> Laser_away: i just don't logic in installing services and then firewalling it
[08:17] <ivoks> Laser_away: it's better to not install it in first place, right? :)
[08:17] <Laser_away> ah
[08:17] <ivoks> ah well...
[08:17] <Laser_away> but that assumes the user knows what they are doing ;-)
[08:18] <rdw200169> exaclty
[08:18] <Laser_away> in the future people will be installing all kinds of stuff
[08:18] <Laser_away> they'll need a tool to see what's going on
[08:18] <ivoks> ok, then we should have everything closed on start
[08:18] <ivoks> and then pick what to open
[08:18] <rdw200169> hackers?
[08:19] <man-di> isnt running services and closing access to them like wasting resources?
[08:19] <ivoks> man-di: i agree :)
[08:19] <ivoks> man-di: (my point exactlly)
[08:19] <Laser_away> ivoks: that's essential what a firewall does
[08:19] <rdw200169> which one, the hacker, or the user?
[08:19] <ivoks> it's different with windows
[08:19] <Laser_away> close off everything, then choose what you want to open
[08:19] <rdw200169> they are right now
[08:19] <ivoks> windows open ports by default
[08:19] <man-di> ivoks: they did in the past but do they still?
[08:19] <ivoks> user doesn't have to install anything; one gets OS with open ports
[08:20] <ivoks> man-di: not in 2003, but yes in XP
[08:20] <man-di> ivoks: XP = past (for me)
[08:20] <rdw200169> or, lets say someone wants to install Apache2 to run a webserver, and a popup asks if they want to open that port
[08:20] <ivoks> and one thing... windows doesn't have sockets
[08:21] <ivoks> rdw200169: i think that should be easily done with dbus
[08:21] <ivoks> but i would prefere having apache installed listening only on localhost
[08:21] <rdw200169> ...
[08:21] <ivoks> same goes for postfix, dovecot, etc...
[08:22] <ivoks> this is better than having listen = * and then firewalling
[08:22] <rdw200169> then what good are those services?
[08:22] <ivoks> rdw200169: whata good are they if they are firewalled? :)
[08:22] <man-di> ivoks: IMO this could be asked on installation with debconf
[08:22] <ivoks> man-di: ubuntu has zero questions policy
[08:22] <man-di> ivoks: if you want only localhost it gets enabled
[08:22] <man-di> oh
[08:23] <man-di> I'm only a Debian Java maintainer wanting to join Ubuntu to make Java in Ubuntu better
[08:23] <man-di> zero questions is good for desktop uses
[08:23] <man-di> users
[08:23] <man-di> probably not so good for server users
[08:23] <man-di> but I dont wanna start a discussion about this yet
[08:26] <ivoks> make java * better
[08:27] <ivoks> :D
[08:27] <ivoks> sorry
[08:27] <ivoks> man-di: no question is good for server too (look at redhat), but only if by default services (except ssh) listen only on localhost
[08:28] <rdw200169> i'm picturing something, as a firewall tool, that would work with, or be a part of, the network administration tool
[08:28] <rdw200169> since they're all related
[08:30] <ivoks> and not enabled by default
[08:30] <ivoks> ubuntu already has quite a number of pop-ups
[08:30] <ivoks> :)
[08:33] <dsas> people just hit "yeah ok let it use the internet" anyway, anything to make the pop-up stops.
[08:34] <ivoks> right
[08:35] <pirast> could anyone please apply the debdiff in bug 90814?
[08:35] <Ubugtu> Malone bug 90814 in asterisk "[UPLOAD]  New Asterisk release 1.2.16" [Undecided,Confirmed]  https://launchpad.net/bugs/90814
[08:39] <ivoks> pirast: only changelog?
[08:39] <pirast> ivoks, yeah
[08:39] <ivoks> pirast: you didn't add ubuntu changes first time?
[08:40] <ivoks> :)
[08:40] <pirast> the ubuntu1 upload is in the archives
[08:40] <pirast> in that i removed older ubuntu changes
[08:41] <pirast> ivoks, that diff adds the removed old ubuntu changes.
[08:41] <ivoks> i see
[08:43] <ivoks> i'll do it, but later...
[08:43] <ivoks> ok?
[08:44] <pirast> ivoks, yeah, thanks :)
[08:47] <joejaxx> how is everyone? :)
[08:53] <tsmithe> grrreeaaa^Wangry
[09:24] <ivoks> pirast: uploaded
[10:08] <tarheelcoxn> hi. I'm looking at https://lists.ubuntu.com/archives/ubuntu-motu/2007-March/001379.html
[10:09] <tarheelcoxn> I'm wondering if there's been talk in here about that, specifically about the wiki bits
[10:14] <pirast> ivoks, thx
[11:21] <pirast> Fujitsu, ping
[11:24] <Fujitsu> pirast: Yep?
[11:25] <pirast> Fujitsu, an Asterisk package fixing the changelog has just been uploaded.. you may want to have a look at it ;-)


[00:06] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (disco-proposed/main) [1:19.04.3 => 1:19.04.4] (core)
[00:11] -queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (xenial-backports) [3.0.2-0ubuntu4~16.04.1]
[00:11] -queuebot:#ubuntu-release- Unapproved: accepted lxcfs [source] (xenial-backports) [3.0.2-0ubuntu1~16.04.1]
[00:13] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (xenial-backports) [3.0.2-0ubuntu1~16.04.1]
[00:18] <mwhudson> so what's the python3.7-defaults story?
[00:18] <mwhudson> ruffus needs bad-testing or marking as a "big" test
[00:18] <mwhudson> and then it's gotten entangled with the perl transition?
[01:04] <xnox> mwhudson, yes https://code.launchpad.net/~xnox/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/358468
[05:08] <doko> mwhudson: disentangled, perl went in. ruffus is the last blocking one for python3-defaults
[05:09] <doko> ahh no, looking at notest ...
[05:13] <doko> graphviz is blocking perl as well via the failing python-ruffus test
[05:40] -queuebot:#ubuntu-release- Unapproved: automake-1.16 (disco-proposed/main) [1:1.16.1-3 => 1:1.16.1-4] (core) (sync)
[06:09] <mwhudson> doko: we need to point Laney at https://code.launchpad.net/~xnox/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/358468 then?
[06:10] <mwhudson> or sil2000 but he's on leave
[06:10] <mwhudson> maybe apw
[08:25] <doko> Laney: please update for bionic: laney:force-badtest libreoffice/1:6.0.3-0ubuntu1/i386
[08:25] <doko> to  libreoffice/1:6.0.6-0ubuntu<IP_ADDRESS>
[08:26] <doko> still fails on i386 with the same issues
[08:27] <doko> infinity: for bionic you have: adconrad:unblock ocrmypdf/6.1.2-1ubuntu1  please could you mark this test as failing as well? seen triggered by python3-defaults
[09:03] <Laney> doko: https://code.launchpad.net/~laney/britney/hints-ubuntu-bionic-glib2.0/+merge/358449
[09:03] <Laney> mwhudson: thanks
[09:04] <Laney> (I do get the emails though)
[09:20] -queuebot:#ubuntu-release- Unapproved: nautilus (disco-proposed/main) [1:3.26.4-0ubuntu7 => 1:3.26.4-0ubuntu8] (ubuntu-desktop)
[11:07] -queuebot:#ubuntu-release- Unapproved: plasma-discover (cosmic-proposed/universe) [5.13.5-1ubuntu6 => 5.13.5-1ubuntu6.1] (kubuntu)
[11:08] -queuebot:#ubuntu-release- Unapproved: plasma-discover (disco-proposed/universe) [5.13.5-1ubuntu6 => 5.13.5-1ubuntu7] (kubuntu)
[11:15] <Laney> xnox: can you do ruffus retries with the right triggers pls
[11:43] <doko> Laney, xnox: looks like LocutusOfBorggave those back
[11:44] <Laney> coordination is hard
[11:51] -queuebot:#ubuntu-release- Unapproved: zeroc-ice (disco-proposed/universe) [3.7.1-4ubuntu2 => 3.7.1-5] (cli-mono) (sync)
[12:02] -queuebot:#ubuntu-release- Unapproved: accepted zeroc-ice [sync] (disco-proposed) [3.7.1-5]
[12:29] <doko> python3-defaults migrated \o/
[12:33] <LocutusOfBorg> lol somebody generated a trigger wrongly
[12:33] <LocutusOfBorg> libhtml-parser-perl/3.72-3build2 ibmoose-perl/2.2011-1build1 libnet-ldns-perl/0.75-3build1 perl/5.28.0-3
[12:33] <LocutusOfBorg> forgetting an "l" :)
[12:33] <LocutusOfBorg> this should make perl a little better if libzonemaster-perl tests are good
[12:33] <LocutusOfBorg> qaplà doko!
[12:59] -queuebot:#ubuntu-release- Unapproved: zeroc-ice (disco-proposed/universe) [3.7.1-5 => 3.7.1-5ubuntu1] (cli-mono)
[13:05] -queuebot:#ubuntu-release- Unapproved: accepted zeroc-ice [source] (disco-proposed) [3.7.1-5ubuntu1]
[14:08] <xnox> mwhudson, i am wondering if clisp is missbuilt on 32bit platforms
[14:25] -queuebot:#ubuntu-release- Unapproved: gnome-initial-setup (cosmic-proposed/main) [3.30.0-1ubuntu3 => 3.30.0-1ubuntu3] (ubuntu-desktop, ubuntugnome)
[14:26] -queuebot:#ubuntu-release- Unapproved: rejected gnome-initial-setup [source] (bionic-proposed) [3.30.0-1ubuntu3.1]
[15:50] <santa_> dear release wizards,
[15:52] <santa_> not sure if this is relevant for the pre-release work but systemd has a higher version in cosmic than disco because of a security update: https://launchpad.net/ubuntu/+source/systemd
[15:53] <santa_> that got into my way when building packages for disco, not a big tradegy since I could workaround it
[15:59] <cjwatson> I could copy it forward but I'd rather wait until disco is properly open before doing stuff like that
[16:00] <cjwatson> Just in case it gets in the way of some transition that's blocking disco opening
[16:01] <xnox> santa_, cjwatson - well there is one more security update coming
[16:02] <xnox> (in security proposed ppa)
[16:08] <santa_> no prob, just wanted to notify the issue, just in case
[16:14] <xnox> santa_, yeah, cool thanks.
[16:47] <infinity> doko: unblocks have nothing to do with tests.  That test has very much regressed from the looks of it.
[16:47] <infinity> doko: (re: ocrmypdf)
[17:14] <ginggs> infinity, doko: i think that ocrmypdf failure is due to ghostscript
[17:14] <infinity> ginggs: The last two definitely seem to be addressed by:
[17:14] <infinity> https://github.com/jbarlow83/OCRmyPDF/commit/517b385fe5cb2195023100a807e6f18dc7e6faea#diff-e00b5801e6b2703e3d116bb5e533a81d
[17:14] <infinity> Not sure about the first.
[17:17] <vorlon> vim hinted through; maybe that's enough to get perl in
[17:17] <vorlon> ah no, clisp-module-gdm needs separate sorting
[17:18] <infinity> vorlon: And the two bizarre rdep failures for clisp itself...
[17:18] <ginggs> infinity: i think this https://git.spwhitton.name/ocrmypdf/commit/?h=debian&id=6b5934ff4ef974613474fa69077777d2d2f338a5
[17:23] <xnox> vorlon, infinity - should fix livecd-rootfs tests [ubuntu/disco-proposed] livecd-rootfs 2.544 (Waiting for approval)
[17:28] <infinity> xnox: That change is silly (IMO)
[17:29] <infinity> xnox: snap-seed-parse isn't some third-party binary we have no control over, it's *from* livecd-rootfs, and there's no reason for it to be logging informational messages to stderr.
[17:29] <infinity> xnox: Ignoring stderr because we're dumb isn't the right answer.
[17:29] <xnox> infinity, i'm not ignoring stderr.
[17:29] <xnox> infinity, i'm logging it to the full log. and there are messages there, printed always.
[17:29] <infinity> xnox: You're sending stderr to stdout, so yes, you're ignoring that there's stuff on stderr.
[17:30] <xnox> on my books, ignoring would mean 2>/dev/null
[17:30] <infinity> xnox: From the POV of autopkgtest trapping stderr as "maybe there were errors" (which is a sane default), redirecting it to stdout is ignoring. :)
[17:30] <xnox> infinity, i agree this is not nice, but this unblocks the world. making that script better is/was out of scope for me.
[17:31] <xnox> infinity, i did flag this up previously, but there is no tracktion on this. and all of these people are gone this week.
[17:31] <xnox> there are multiple things wrong here =) people really should run livecd-rootfs adt before upload, locally. it works.
[17:32] <xnox> and cpc sauce should not have started to use a newly introduced functions before livecd-rootfs migrates and gets published in their ppa.
[17:32] <infinity> Yeah, I guess the real problem here is that the result is on stdout, so the author decided to log to stderr.
[17:32] <infinity> Taking a second argument for output file, then logging to stdout (except for actual errors to stderr) would be saner.
[17:33] <xnox> i'm happy to open that as a bug report
[17:33] <infinity> Please do, and assing to the original committer with prejudice. :)
[17:33] <infinity> But yeah, we can take your hack for now.
[17:34] <infinity> I'm okay with temp hacks, as long as they're actually temp.
[17:34] <infinity> Knocking on all the wood.
[17:34] <xnox> cause like doko has been pointlessly retrying livecd-rootfs tests for days now =) he clearly wants to keep the planet warm via our scalingstack ;-)
[17:38] <Laney> :/
[18:58] <vorlon> anyone else already working on clisp?
[19:19] <infinity> vorlon: I only scraped the surface enough to say "WTF", feel free to dig deeper (please).
[19:21] <infinity> vorlon: If the cl-asdf and cl-unicode failures end up being the only perl/gdbm blockers, I'm tepted to badtest them (even though that's a bit of a lie) because hey, two out of three lisp interpreters still work.
[19:22] <infinity> vorlon: I'd be more comfy about that call if I knoew what the most popular common list interpreter was, mind you.
[19:23] <coreycb> doko: can you reject my latest openstack-pkg-tools upload to disco? it is fixed instead by your latest upload of python3-defaults.
[20:07] <vorlon> infinity: well good news, I can't get cl-asdf/armhf to pass at all on the porter box
[20:08] <infinity> vorlon: That's news?
[20:09] <mwhudson> NOTAREGRESSION i assume?
[20:09] <mwhudson> also not a regression is my python-tornado SRU failing to build in cosmic
[20:09] <vorlon> infinity, mwhudson: I mean that I can't get a clean baseline
[20:09] <vorlon> it passes on autopkgtest
[20:09] <mwhudson> ah
[20:09] <vorlon> then fails on the porter box
[20:09] <infinity> Why have I forgotten the name of the porter?
[20:10] <vorlon> rugby?
[20:10] <infinity> Okay, better question, why can't I see it in DNS? :p
[20:10]  * infinity restarts the VPN.
[20:10] <mwhudson> the arm64 porter has always had oddball dns
[20:10] <infinity> Well, it's rugby.inernal, if I recall, but irritatingly not resolving for me.
[20:11] <mwhudson> well modulo the typo, yes
[20:11] <infinity> Though, neither is ftpmaster.internal, so... I blame systemd-resolved.
[20:12] <vorlon> infinity: yes, see discussion internal #is right now
[20:12] <mwhudson> those are fun looking errors
[20:12] <vorlon> nm something systemd-resolved something something broken
[20:12] <vorlon> anyway, cheating and using my access to autopkgtest infra :/
[20:14] <infinity> vorlon: So, you're saying that on rugby, it fails the same way with the release pocket version of clisp?  Or fails differently?
[20:14] <vorlon> infinity: fails differently
[20:14] <vorlon> (at an earlier stage)
[20:14] <infinity> Fun.
[20:30] <vorlon> ugh and launching a disco autopkgtest container gave me no network by default
[20:30] <tsimonq2> vorlon: Would that happen to be an LXD container?
[20:30] <vorlon> yes
[20:31] <tsimonq2> wxl ran into the exact same thing with Cosmic images last cycle and we just could not figure it out...
[20:31] <tsimonq2> (It worked on my machine, so it was just me suggesting ideas, but... :P)
[20:31] <vorlon> it's not generally speaking a problem
[20:31] <vorlon> I don't know what's up with this particular disco image
[20:32] <teward> vorlon: does a manually launched disco image in LXD work without issue with networking?
[20:32] <vorlon> cloud-init missing from the image, that might be it
[20:32] <teward> just curious :P
[20:32] <teward> ahhhh, cloud-init, that evil thing...
[20:32] <vorlon> cloud-init, that essential piece of infrastructure
[20:32]  * tsimonq2 hands teward another gallon of coffee.
[20:33]  * teward dumps it over tsimonq2 and goes back to determining whether he should propose an SRU or just a backport of partclone due to the major bug he found in it today
[20:40] <vorlon> ok, and an autopkgtest container gives me the same result as on rugby, and not the behavior seen in the autopkgtests
[20:41] <infinity> ...
[20:41] <vorlon> https://paste.ubuntu.com/p/DzvTdhT9KC/ if someone wants to explain this
[20:42] <infinity> vorlon: export AUTOPKGTEST_TMP
[20:42] <vorlon> oh. it's caused by the runtests.lisp being sensitive to $AUTOPKGTEST_TMP being set in env. :P
[20:42] <vorlon> yeah
[20:43] <vorlon> aaaand now it passes with clisp from -proposed
[20:43] <infinity> ...
[20:43] <infinity> With clisp from proposed? :(
[20:43] <infinity> WTF.
[20:43] <infinity> I mean, yay, you can badtest it with "passes with manual test", but also, WTF.
[20:44] <infinity> clisp is a flaming heap.
[20:44] <vorlon> well, I also wasn't very granular, let me see about --all-proposed
[20:44] <infinity> I'm not sure how all-proposed would change much with those two cl* tests.
[20:44] <infinity> Did anything really change other than clisp itself being rebuilt?
[20:47] <vorlon> infinity: point being that when I pulled in clisp from -proposed I also pulled in a bunch of other stuff (e.g. perl) and I don't know *why* clisp would care, but maybe it does
[20:48] <infinity> vorlon: Right, I wasn't questioning the "you had a bunch of taint" argument, just that I too can't see why it would matter in this case. :P
[20:48] <vorlon> k
[20:48] <infinity> Since clisp's dependency chain is approximately nil.
[20:48] <vorlon> ITYM 'NIL'
[20:48] <infinity> And cl-asdf even less so (literally just wants *some* lisp interpreter)
[20:49] <vorlon> dependencychainp?
[20:49] <infinity> (( stahp))
[20:50] <teward> vorlon: because i'm tired: ITYM = ?
[20:50] <infinity> teward: I Think You Mean.
[20:50] <teward> ah, of course, thanks. :)
[21:21] <infinity> vorlon: Okay, publisher run to remove those two things is about to go.
[21:21] <infinity> ... in 2 minutes.
[21:24] <infinity> vorlon: Of course, that removal will break all the cl-* autopkgtests that test-depend on clisp and attempt to run it...
[21:24] <infinity> Unless they're somehow magically conditional.
[21:24] <vorlon> ¯\_(ツ)_/¯
[21:25] <infinity> Yeah, I don't think there is a magical "only run this test if the deps exist" conditional in autopkgtest is there?
[21:25] <infinity> That might be useful.
[21:25] <vorlon> there is now
[21:25] <vorlon> recently added. not sure we support it yet.
[21:25] <infinity> As would be a Test-Architectures field, maybe.
[21:25] <vorlon> and I don't remember what it's called
[21:26] <vorlon> but I did see it show up as a restriction in a diff recently - skip-not-installable or so?
[21:26] <infinity> Oh, nice.
[21:26] <vorlon> https://launchpad.net/debian/+source/autopkgtest/+changelog tada - well-named
[21:26] <infinity> Although, not-avilable would be more what I'm after.
[21:30] <infinity> vorlon: Yeah, that looks like it's what it implies (it'll skip if the installation pass fails), which is icky.  But in this case, would work alright.
[21:31] <infinity> vorlon: Still gross, though, cause it means tests with that restriction will now skip/"pass" if the dep chain is temporarily in an uninstallable state, when what I think the submitter really wanted was "if the deps don't exist".
[21:31] <infinity> Oh well.
[21:38] <vorlon> infinity: alright, I can't reproduce the cl-unicode/i386 segfault either
[21:38] <vorlon> so maybe we should just badtest those?
[21:38] <infinity> vorlon: Fine with that too, it'll just sail back in.
[21:38] <infinity> (but also, wtf)
[21:39] <vorlon> of course, this means those packages' autopkgtests can no longer be used to catch regressions in either sbcl or ecl
[21:39] <infinity> vorlon: Just one test of one CL package on one arch each, it's probably acceptable collateral damage.
[21:40] <infinity> We certainly have much more scary/dangerous badtests (*cough*systemd*cough*)
[21:40] <vorlon> and what should we make of the fact that in all cases, the bad addresses are 0xaf[...]?
[21:41] <infinity> 0xaffluenza?
[21:42] <vorlon> looks like clisp doesn't have any ASLR.  maybe that's reason enough to kill it
[21:43] <infinity> I have no strong opinions about how many lisp inerpreters/compilers we need, nor which ones.
[21:44] <infinity> It feels like Debian's CL people have more or less settled on sbcl as the One True C Lisp.
[21:53] <mwhudson> it's also the only common lisp i have drunk beer with two of the authors of!
[21:54] <infinity> mwhudson: I've had beer with several of the systemd authors, I'm not sure that's helped me hate it any less.
[21:54] <infinity> SUCCESS (631/8)
[21:54] <infinity> I think I'm about to get a lot of email.
[21:56] <mwhudson> infinity: fair
[21:59] <infinity> doko: Do you have an archive opening mail prepped?
[22:00] <tsimonq2> >_>
[22:09] <xnox> infinity, i acknoledge systemd continious flakiness. but also note that it's like a leaky poo.... cause it's constant improvements and constant new regressions =/ never ending battle.
[22:09] <infinity> "It's like a leaky poo".
[22:09] <infinity> Thanks for that.
[22:10] <xnox> the current flakiness around activating / starting / that weird gdm is the latest puddle.
[22:11] <infinity> This metaphor isn't getting any more pleasant.
[22:18]  * xnox ponders how many publishing cycles it will take, given that like delete is done; yet publish is not yet there.
[22:19] <infinity> xnox: Patience.  LP's copy interface is async, I'm making sure everything went through before I publish again and turn reports back on.
[22:19] <xnox> nice! thanks for doing it without havoc.
[22:21] <infinity> I wish there was a restricted copy_package_sync() that britney could use.
[22:21] <infinity> Better yet, move_package_sync(), so it would copy/delete atomically, and get a pass/fail return.
[22:21] <infinity> Sadly, there is not.
[22:22] <xnox> well. imho we should only do copy_package; not move. and have an separate pass to notice duplicate/equal things published in both -proposed and release, and clean that up later.
[22:23] <infinity> That's probably what we should be doing today, to avoid things accidentally going missing.
[22:23] <xnox> cause having identical thing published in both -release and -proposed is harmless; removing a thing from -release without a new one publish and -proposed one removed as well, is bad.
[22:23] <infinity> But move would be cleaner.
[23:59] <vorlon> infinity: still waiting for everything to publish?


[01:15] <DylanW> Hi all, just wondering if anyone can tell me the default username and password for the Mythbuntu Live CD?
[01:17] <DylanW> !help
[01:17] <Zinn> !help For a  complete list of my knowledge visit: http://www.baablogic.net/Zinn.cgi  Other available commands: !status, !about, !bug [bug_number].
[01:26] <tgm4883> DylanW, there isn't one?
[01:26] <tgm4883> maybe ubuntu/ubuntu
[02:29] <DylanW> I tried ubuntu, but it was rejected. By default the live cd logs you in automatically but I'm trying to load a video driver that will give me more than 800x600 and you need to logout and log back in to active it.
[02:34] <DylanW> All sorted, I used passwd to reset the password. Thanks for your time!
[13:28] <qwebirc84612> anyone use a mac mini for nackend
[13:30] <qwebirc84612> i am curious if anyone uses firewire to a cable box for video on a mac mini
[15:50] <qwebirc83677> I am looking for some help setting up a server and client. Client is dual boot connected to TV and server is in other part of house.
[15:50] <qwebirc83677> I didn't find a wiki page...
[15:51] <qwebirc83677> any takers?
[22:03] <qwebirc81719> Just installed mytbuntu 12.04. Mythtv frontend pops up asking for my location and language; I enter it, press save. Tells me it can't connect to the database. I click next and finish, it starts over. I click cancel, I get a message that mythtv frontend has closed unexpectedly and it respawns.
[22:04] <qwebirc81719> If I'm quick I can hit applications and get to a terminal before it respawns, but I'm at a loss for how to fix this.
[22:05] <qwebirc81719> Funny how it thinks me closing the program is it crashing. Not sure how that works.
[22:38] <qwebirc81719> Right, it's because mysql server isn't being configured properly.