/srv/irclogs.ubuntu.com/2009/09/14/#ubuntu-meeting.txt

=== edson is now known as ecanto
=== starcraftman is now known as CanMoose
=== CanMoose is now known as starcraftman
stochasticWho all is here for the Ubuntu Studio developers meeting?07:59
stochastichmm, are any studio developers around?08:05
stochasticLooks like the lack of reminder e-mail and the non-mandatory status of the meeting killed the turnout.08:06
jonostochastic, maybe send out the reminder a week before?08:22
jonoubuntu studio is awesome :)08:22
stochasticyeah, next month I'll do that08:22
jonostochastic, :)08:24
jussi01Im here now08:48
jussi01got stuck in a work meeting08:48
jussi01stochastic: TheMuso ^08:48
* TheMuso is here08:52
TheMusoBut I think its a no go.08:52
=== dholbach_ is now known as dholbach
=== ogra_ is now known as ogra
=== pgraner` is now known as pgraner
=== james_w` is now known as james_w
=== fader|away is now known as fader_
=== imlad|away is now known as imlad
=== marjomercado is now known as marjo
RoAkSoAxmorning15:51
=== mhall1191work is now known as mhall119|work
=== ember__ is now known as ember
keesjdstrand, mdeslaur: I'll go first?  I've still got neon to finish, and the 777 symlink thing to test18:04
mdeslaurkees: that's the nautilus glibc thing?18:05
keeswell, just glib (not glibc)18:05
jdstrandglib, not glibc18:05
mdeslauryeah, glib18:05
mdeslaurd'uh18:05
keesuhm, and I think once bug 322562 is solved, we can start on the sync-to-LP project18:06
ubottuLaunchpad bug 322562 in malone "Cannot lookup bug list from CVE" [Medium,In progress] https://launchpad.net/bugs/32256218:06
keeseverything else seems like it's in place.  nominations was the big missing piece, and that appears to work on edge now18:07
jdstrandcool18:07
keesI've got one item for the end of the meeting, but for tasks, I'm done.18:08
jdstrandshall I go?18:08
keessure18:08
=== noy_ is now known as noy
jdstrandok, well, this is going to be a busy week. I've got an openoffice.org and kdelibs update I'm working on. I started on but need to finish a gnutls regression that was reported in Debian which we are affected by (but no one has reported it in Ubuntu)18:09
jdstrandI need to update my libvirt/apparmor patch and resubmit to upstream. I'd like to get to it this week, but based on how oo.o is going so far, that may not happen18:10
jdstrandthere is also a weird valgrind bug that cjwatson asked me to help out with, but again, we'll see if I can get to it18:11
keesjdstrand: I can help with the OOo build process...18:11
jdstrandkees: well, I have all that documented. I just need to rebuild my schroots18:12
keesjdstrand: yeah, well, we can take that offline18:12
jdstrandkees: the problem is patches aren't applying cleanly. I'm early in the process, so we'll see18:12
keesugh18:12
jdstrandthat's it on tasks, but I have two items at the end of the meeting18:13
mdeslaurmy turn?18:14
keesyuppers18:14
mdeslaurI'm publishing openssl and openexr in a couple of minutes18:15
mdeslaurI'll take freeradius18:15
keesfreeradius is just a DoS though?18:15
mdeslaurI want to work on packaging the apparmor apache2 stuff to my PPA18:15
mdeslaurkees: DoS on a network service18:15
keesmdeslaur: ah, right18:15
mdeslaurAnd want to investigate the aa-logprof bug18:16
mdeslaurthat's it for me18:16
keesokay, item from me: reviewing sponsorship processes.18:17
keesI want to compare the security-sponsorship process to the "standard" sponsorship proceses18:17
keesthe goal being to make our sponsorship work more visible to the world.  dholbach is using some of their process to track how much is happening, etc18:18
keesand we don't really show up in there.18:18
keesnothing formal, yet, but just wanted to give a heads-up for potential process changes.18:18
* jdstrand nods18:18
keesthat's it from me.18:18
robbiewthat's a good idea18:18
jdstrandI only have one extra thing18:19
=== greg_g is now known as greg-g
jdstrandwe may want to clarify the partner package tracking process18:19
mdeslaurjdstrand: good idea18:20
keesjdstrand: how so?18:20
jdstrandI'm not sure that is documented anywhwere, but I was pinged about whether we will alert partner package maintainers about it18:20
jdstrandI said 'yes', but I'm not sure it's been documented, the process, etc18:20
jdstrandoh, I did have one other thing18:21
keeswe're not exporting issues in partner packages yet...  http://people.canonical.com/~ubuntu-security/cve/pkg/opera.html18:22
keesbut I know we can look them up.18:22
keesoh, maybe opera doesn't have any at the moment18:22
jdstrandin UCT it seems that for dapper EOL packages, we should 'ignore' them so we can actually retire those CVEs. as it is, nothing will ever retire in UCT cause dapper is there18:23
jdstrandkees: we don't have opera anymore18:23
jdstrandadobe-flashplugin would be one18:23
keesah, right.  ok, I take it back.  we *are* exporting details: http://people.canonical.com/~ubuntu-security/cve/pkg/sugarcrm.html18:23
keeshttp://people.canonical.com/~ubuntu-security/cve/pkg/adobe-flashplugin.html18:23
jdstrandkees: ah, so I can just point the maintainers to that and we are done18:23
jdstrandkees: I like that18:23
keesjdstrand: right, that's why I created them.18:23
keeson my todo list is to also publish an RSS feed, but... it's low priority18:24
jdstrandkees: cool, I'll follow up and document that somewhere18:24
keessweet18:24
jdstrandkees, mdeslaur: what do you think about the dapper EOL stuff?18:24
jdstrandideally, I think it needs to be automated with check-cves18:25
keesjdstrand: "stuff" being what?18:25
jdstrand12:21 < jdstrand> oh, I did have one other thing18:25
mdeslaurwell, is dapper desktop EoL as in "dead", or is it now reverted to the community18:25
jdstrand12:23 < jdstrand> in UCT it seems that for dapper EOL packages, we should  'ignore' them so we can actually retire those CVEs. as it is,  nothing will ever retire in UCT cause dapper is there18:25
keesmdeslaur: community18:25
ScottKkees: I disagree.18:26
keesjdstrand: oh, sorry, I jumped over that while digging up URLs  :)18:26
mdeslaurif it's community, then the CVEs shouldn't be marked "ignored"18:26
ScottKIt's got to be dead.18:26
jdstrandI was under the impression dead18:26
keesokay, I'll take "dead".  :)18:26
jdstrandI mean, if someone really wants to submit a patch, we can process it, but I think that should be the exception18:26
mdeslaurScottK: if that's the case, what happens to all the stuff in universe that depend on stuff that's now "dead" in main?18:26
ScottKIt's dead too, IMO.18:27
ScottKI'd like it if it could be moved to old-releases now, but I understand that's technically problematic.18:27
jdstrandif it is not dead, then we need to make sure all of our reporting is very accurate18:27
mdeslaurhmm...so do we consider all of dapper universe as being "dead"?18:27
jdstrandI have looked at it, but would imagine there are issues in our reporting18:28
ScottKIf the policy isn't clear to you two, then maybe the tech board needs to clarify18:28
jdstrands/have/haven't/18:28
ScottKtwo/three18:28
keesmy take was that it simple moved out of "commercially supported".18:28
jdstrandwell, the desktop is considered EOL18:28
jdstrandgutsy is EOL18:28
keesso, while I'd be okay with "dead" since it simplifies tracking (kind of), the reality of the situation is that the package still exists, and is still vulnerable.18:29
jdstrandthe two should mean the same thing-- dead18:29
ScottKMy take is "Dumped on the community" is not a good plan.18:29
mdeslaurso the question is: is dapper universe "Dead/EoL" also?18:29
keesjdstrand: actually, that language just suddenly convinced me.18:29
jdstrandit only still exists because the archive can't handle moving it18:29
keeswe have declared dapper desktop EOL, which is the same as "out of the tracker"18:29
ScottKJust to make it more fun, next month Kubuntu Hardy is EOL, but Ubuntu isn't.18:29
ScottKGood luck figuring that one out.18:29
keesScottK: ooh, I'd forgotten about that.18:30
mdeslaurScottK: oh!18:30
jdstrandScottK: thank you for pointing that out, I don't think any of us were thinking about it :)18:30
keesScottK: it should be possible-ish to do it in the same way we did dapper desktop eol: static package lists18:30
ScottKThen I never have to worry about KDE3 again.....18:30
keesheh18:30
mdeslauruhm...kde packages are part of Ubuntu also, which we support18:31
ScottKYep.18:31
keesScottK: <random>do you happen to know who to poke about fridge schedules?  this meeting is on the fridge iCal, but doesn't show up on the website.18:31
ScottKI'm really not sure how you handle it.18:31
mdeslaurI don't see how we can stop support for kde packages if they're in main18:31
ScottKkees: Nope.18:31
keesok18:31
jdstrandmdeslaur: we'll just need to look at them and see if there is something we can/should do18:31
mdeslaurjdstrand: what do you mean?18:32
ScottKOnce again, I don't know what the policy is, but someone ought to decide.18:32
jdstrandmdeslaur: I mean I don't think we'll solve what is supported or not in this conversation :P18:32
mdeslaurjdstrand: ah! well, me either :P18:32
jdstrandwe also need to look at the language of the Kubuntu release and consult slangasek once we have a grasp of the issues18:33
* kees nods18:33
jdstrandso, dapper?18:33
ScottKEOL18:33
mdeslaurdapper universe?18:33
ScottKEOL if it needs X18:34
jdstrandEOL/dead +1 (it's been in all documentation and release notes)18:34
keesdead +1, but I don't yet have any idea how to correctly "show" this automatically in ubuntu-cve-tracker18:34
jdstrandlike I said, the formal policy should be 'dead'. if someone is inclined to give a patch, we can process without USN if required18:35
ScottKImplementation detail.18:35
* kees nods18:35
jdstrandit is an implementation detail, but that was actually my original question :)18:35
kees"ignored" means we don't care, not "not-affected", so I think it's okay.18:35
jdstrand(I had assumed everyone knew it was dead)18:35
jdstrandkees: yes, 'ignored'18:35
mdeslaurok, ignored +118:35
jdstrandkees: 'ignored (end-of-life)'18:36
keesjdstrand: right, but if one runs ./scripts/madison it shows up in "universe" instead of "main", though it should show up as DNE, kind-of.18:36
keesyeah18:36
keesanyway, DNE is wrong, so I'm stuck wondering how to automatically show it.  but, not important at the moment.18:36
keesjdstrand: you had another issue?18:36
keeswait, no, that was it.18:36
jdstrandkees: wrt dapper? no. I just want to make sure we fix it in the tracker so that we can a) retire things and b) ensure our reporting is valid18:37
* kees nods18:37
jdstrandthat is it from me18:37
keesokay, anything else?18:38
jdstrandnope18:38
keescool, meeting over.  thanks!18:38
robbiewthnx18:39
jdstrando/18:40
=== Seeker`_ is now known as Seeker`
=== fader_ is now known as fader|away
=== imlad is now known as imlad|away
=== robbiew is now known as robbiew-afk

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!