/srv/irclogs.ubuntu.com/2005/01/15/#ubuntu-meeting.txt

=== Lovechild [~dnielsen@82.150.72.35] has left #ubuntu-meeting ["Leaving"]
=== mjg59 [mjg59@cavan.codon.org.uk] has joined #ubuntu-meeting
=== pitti [~martin@195.227.105.180] has joined #ubuntu-meeting
=== pitti [~martin@195.227.105.180] has joined #ubuntu-meeting
=== pitti [~martin@195.227.105.180] has joined #ubuntu-meeting
=== highvoltage [~jonathan@dumbledore.hbd.com] has joined #ubuntu-meeting
=== skyrider [~skyrider@195.128.178.150] has joined #ubuntu-meeting
=== bwb [~nate@ip68-5-253-106.oc.oc.cox.net] has joined #ubuntu-meeting
=== Riddell [jr@muse.19inch.net] has joined #ubuntu-meeting
=== bwb [~nate@ip68-5-253-106.oc.oc.cox.net] has left #ubuntu-meeting []
=== pitti [~martin@195.227.105.180] has joined #ubuntu-meeting
=== bwb [~nate@ip68-5-253-106.oc.oc.cox.net] has joined #ubuntu-meeting
=== zul [~chuck@zul.developer.gentoo] has joined #ubuntu-meeting
=== skyrider [~skyrider@195.128.178.150] has joined #ubuntu-meeting
=== seb128 [~seb128@ANancy-151-1-45-42.w83-196.abo.wanadoo.fr] has joined #ubuntu-meeting
=== sivang [~sivang@box79162.elkhouse.de] has joined #ubuntu-meeting
=== lamont_r [~lamont@mesaradio41.customer.frii.net] has joined #ubuntu-meeting
=== hno73 [~Henrik@henrik.gotadsl.co.uk] has joined #ubuntu-meeting
=== skyrider [~skyrider@195.128.178.150] has joined #ubuntu-meeting
=== skyrider [~skyrider@195.128.178.150] has joined #ubuntu-meeting
=== mvo [~egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting
=== fabbione [~fabbione@port49.ds1-van.adsl.cybercity.dk] has joined #ubuntu-meeting
=== Keybuk [scott@descent.netsplit.com] has joined #ubuntu-meeting
=== hno73 [~Henrik@henrik.gotadsl.co.uk] has left #ubuntu-meeting []
=== hno73 [~Henrik@henrik.gotadsl.co.uk] has joined #ubuntu-meeting
=== bluefoxicy drags ass over from bed with one eye
zulits not that early bluefoxicy 04:55
=== mdz [~mdz@69-167-148-207.vnnyca.adelphia.net] has joined #ubuntu-meeting
bluefoxicyuh04:55
bluefoxicy11 am?04:55
zulstill04:56
mdzmorning04:56
seb128hello mdz 04:56
bluefoxicyheh, I have a problem waking up, it takes me several hours04:56
bluefoxicynormally I become concious at something like 8 or 9 am04:56
bluefoxicyand get up at 12 or 1 pm04:56
=== ..[topic/#ubuntu-meeting:mdz] : Tuesday 4 January 2005 at 1600 UTC: Technical Board -- http://www.ubuntulinux.org/wiki/TechnicalBoardAgenda. Tuesday 11 January 2005: Community Council meeting -- https://www.ubuntulinux.org/wiki/CommunityCouncilAgenda
=== azeem [~mbanck@socks-out.lrz-muenchen.de] has joined #ubuntu-meeting
=== lamont_r notes that it's only 1558 utc
=== elmo [~james@83.216.141.215] has joined #ubuntu-meeting
=== bluefoxicy tries to get trulux in here
=== trulux [~lorenzo@67.Red-80-25-56.pooles.rima-tde.net] has joined #ubuntu-meeting
lamont_rbluefoxicy: what tz you in?04:58
bluefoxicydo I have time to make a glass of koolaid?04:58
truluxhi04:58
bluefoxicylamont_r:  EST04:59
=== haggai [~halls@i-83-67-20-196.freedom2surf.net] has joined #ubuntu-meeting
zulbluefoxicy, it still isnt early ;)04:59
=== lamont_r has no pity. (MST here, and kids in school is really interfering with my night owl schedule)
mdzok05:00
truluxhey pitti05:00
bluefoxicyheh05:00
pittiHi trulux 05:00
sivanghey all05:00
mdzfirst agenda item is to talk about proactive security05:00
mdzis JohnMoser here?05:01
bluefoxicyyo05:01
mdzgo ahead05:01
mdzwhat is the question which needs to be resolved?05:01
truluxpitti, umm, dunno if it's right to say it before the talk starts, but, i apologize of creating specific SELinux kernel packages05:01
bluefoxicyIt's actually been trulux and pitti working on it mostly.  I'm not really in a position to talk about . . . whatever they're up to05:01
=== amu [~amu@amu.developer.debian] has joined #ubuntu-meeting
truluxok, then let me start it05:01
truluxpitti, ready?05:02
bluefoxicybut with certain things such as Stack Smash Protection and PaX, a compatible or mostly compatible environment can be made in which many security flaws are resolved before they exist, for the most part.05:02
pittisure05:02
truluxbluefoxicy, before they exist not, before they get known or even following a similar pattern05:02
trulux;)05:02
bluefoxicy. . . yeah, let trulux and pitti explain it.  I'm just here because i want to see what happens about it, and I'd like to see an official statement soon, if not a roadmap.05:03
truluxthat's because it's called proactive security, which also prevents so-called zero-day exploits05:03
fabbionetrulux: well we have selinux compiled in already... it just question of a boot flag to enable it05:03
bluefoxicyyes05:03
truluxfabbione, i'm working on to get a desktop-ready SELinux system for Ubuntu05:03
truluxfabbione, also i'm the guy developing the 2.4 backport05:03
fabbionetrulux: yeah but the kernel is ready already ;)05:03
pittiI publically announced the first PaX enabled kernels today05:03
bluefoxicypitti:  sweet.  :)05:04
mdzpitti: great05:04
truluxfabbione, heh, sure05:04
truluxpitti, at this point i would like to make some comments05:04
pittithe kernels work mostly fine already. Still some caveats, but Itry to sort them out soon05:04
pittitrulux: go ahead05:04
truluxkay05:04
mdzso, with fabbione's selinux enabling and pitti's PaX kernel, 2 of 3 assignments from Mataro are complete05:04
pittifor my part I must say that I would welcome collaboration with hardened-debian05:04
truluxpitti, me too, and debhard devs would like to05:05
truluxso, this is what i think:05:05
pittimdz: in fact I also digged a bit about what obsd and gentoo do05:05
pittimdz: basically they use gcc-ssp, too05:05
pittimdz: and obsd has something similar like PaX (W^X)05:05
=== mako [mako@micha.hampshire.edu] has joined #ubuntu-meeting
trulux1) we should try to create a team of people with some skills in open source and free software information assurance related software05:06
truluxthat means:05:06
truluxhaving guys with kernel hacking skills, documentation skills, talking skills and *leading* skills05:06
truluxthis is more than protecting buffer overflows05:06
pittiwell, it's about improving general proactive security05:07
bluefoxicypitti: yes, Gentoo uses an SSP GCC exclusively, which brings certain protections with it (variable order rearrangement) under all circumstances.  -fstack-protector is needed to activate the other protections; but both cases have fairly thorough testing.05:07
pitti... and OpenBSD uses SSP for ages now05:07
bluefoxicyyeah05:07
truluxpitti, the point is that we are not just putting proactive security05:07
pittias we already said, the main isseu with SSP is not the technical side, but the supportability over the whole distro lifecycle05:08
truluxfrom the oytside, people will know it as the way of having the information leak-proof05:08
truluxand secured05:08
lamont_rand the ssp croud has yet to provide a moduler set of gcc patches, aiui05:08
pittias long as SSP is not upstream, it might become hard to support05:08
truluxso, they will think in moving to Ubuntu05:08
truluxfor example05:08
truluxpitti, i've talked to Eoth, i would try to move some things to help with that05:08
truluxEtoh05:08
pittiand I was told that even Windows XP now has canaries on the stack (SSP-like)05:08
bluefoxicypitti:  Etoh has tried to get SSP upstream, and they requested a current CVS patch, but I don't think it actually went anywhere.05:09
mdztrulux: if you aren't talking about proactive security, then please explain what you do mean05:09
mdzbecause the specific items we have discussed so far all fall under that heading05:09
pittitrulux: would you like to create SSP packages for universe now? The way we already discussed? 05:09
lamont_rbluefoxicy: I expect that they requested a _set_ of individual patches vs cvs-head05:09
truluxmdz, it's proactive security for us, information assurance for the users05:09
pittiwhich is basically the same05:10
truluxpitti, yes, but with different understanding points05:10
truluxi think i can do the SSP packages05:10
truluxsure05:10
mdzthey're both jargon to the user05:10
pittithat'd be great05:10
mdzbetter to have a name which is more meaningful to the people who would be involved with it05:10
truluxmdz, i still like proactive security ;)05:11
bluefoxicylamont_r: 05:11
pittifor the audience, the plan is to provide completely independent gcc-ssp packages in universe for now05:11
truluxpitti, but why separating the pkgs in -ssp and non-ssp brands?05:11
pittiso they can be used to play without interfering with the release process05:11
mdzpitti: a copy of the source?05:11
bluefoxicylamont_r: http://gcc.gnu.org/ml/gcc-patches/2004-09/msg00348.html  Here's the thread. "It seems that your patch is against GCC 3.4.  Do you have a patch against current GCC CVS?" was never followed up.05:11
pittimdz: so far this seems to be necessary05:11
lamont_rtrulux: it's nice to turn the stack-overrun into a DoS instead of a root vul, but the users still don't consider DoS==secure05:11
lamont_rbluefoxicy: ok05:12
pittimdz: unless trulux is able to "wrap" gcc with the protector, but I think that is difficult05:12
pittilamont_r: it keeps your data secure, though05:12
truluxpitti, i will so my wrappers05:12
truluxshow05:12
mdzif elmo doesn't hate the idea of duplicating the source too much, I think that it's a good idea to keep them as separate as possible05:12
bluefoxicylamont_r:  I look at security as a user-friendly issue.05:12
mdzso that we don't interfere with the progress of the standard gcc05:13
elmoI don't much care, as long as we only do it once - ideally, we'd coordinate with doko and do toolchain-source sans crack05:13
bluefoxicylamont_r:  If someone loads a worm onto my computer via a damaged .png image that then proceeds to get local root via a kernel exploit and then eat my hard disk, this is called 'pissing me off'05:13
=== ogra [~ogra@p508EBC96.dip.t-dialin.net] has joined #ubuntu-meeting
pittilamont_r: avoiding DoS is a matter of fixing the package, no way to get around this :-)05:13
lamont_rpitti: exactly05:13
bluefoxicylamont_r:  a crash annoys me, but I don't need to worry about it eating my machine.05:13
mdzlikewise for a broad class of vulnerabilities05:13
truluxlorenzo@estila:~/proyectos/hardened-toolchain-wrappers $ ls05:13
truluxhardened-gcc-wrapper-1.4.2.c  hardened-ld-wrapper-1.4.2.c  Makefile  suspect.c05:13
truluxlorenzo@estila:~/proyectos/hardened-toolchain-wrappers $05:13
pittilamont_r: the point is just to confine the impact of holes05:13
lamont_rpitti: mind you, I'm all for security blankets, as long as we understand what they are.05:13
mdzthings like SSP are about low-hanging fruit and maybe-good-enough solutions05:14
elmoyeah, I'm a little concerned about the propaganda I'm hearing to be honest - these things are at best a layer05:14
lamont_rmdz: agreed.  low hanging fruit are great to grab.  But calling the result "secure" is laughable05:14
mdzcertainly05:15
bluefoxicyI did a quick analysis on how well this stuff would protect you.  http://www.ubuntulinux.org/wiki/USNAnalysis 05:15
pittilamont_r: we talk about "improving" proactive security05:15
mdzthis is "a feature which makes your system more difficult to attack"05:15
bluefoxicySSP for example would carry about 40% of the torch05:15
pittilamont_r: not reaching the ultimate goal :-)05:15
lamont_rthen again, that's because the end users see security as an absolute, while we see it as a range05:15
truluxwait, can i show what i was meaning? it's just a moment05:15
mdzbluefoxicy: I have a feeling that figure is based on the assumption that SSP prevents all buffer overflows05:15
truluxwe have both wrappers, one for ld and one for gcc05:15
elmowhich it doesn't05:15
truluxi will upload the stuff and you could check it05:16
bluefoxicymdz:  It's more based on the assumption that the classes of buffer overflows that SSP doesn't protect are very rare05:16
pittimdz: SSP does not prevent buffer overflows, neither does PaX05:16
bluefoxicymdz:  mainly, overflows inside structures with data above buffers05:16
pittimdz: it just confines their exploitation05:16
bluefoxicysorry pitti is right, it catches the attack at the end05:16
mdzpitti: yes, that's what I should have said05:17
bluefoxicypitti:  doesn't it actually prevents their exploitation?  Things like SELinux confine it right?05:17
mdzs/prevents/addresses/05:17
pittimdz: just to clarify for the audience :-)05:17
pittibluefoxicy: yes05:17
bluefoxicymdz:  attacks on SSP cannot be guaranteed uness you can find __guard in the GOT with a format string bug, or in the stack.  If you have PaX + ASLR, you need to inject code to read the GOT offset from a register (%efp) as I understand it05:17
pittibluefoxicy: let's say, in most cases it prevents it, but there might be loopholes which still allow exploitation05:17
bluefoxicyand if you have active PaX with memory protections + ASLR, you can't really inject code to do that anyway :)05:18
bluefoxicyso it becomes on the whole a 1/4000000 guessing game any route you take05:18
pitti^ that's what my kernels are for05:18
bluefoxicypitti: yes, but in most cases there will be no possible way of guaranteed exploitation.05:18
pittibtw, PaX prevents executing stuff in writeable pages, so this closes the 1/400000 chance :-)05:19
pittibluefoxicy: right05:19
pittianyway, I don't think we need to discuss this stuff in the meeting05:19
lamont_rjust because the code is normally in the stack doesn't mean it needs to be.05:19
pittiplease leave the technical arguments aside here05:19
mdzyes, do05:19
mdzwe don't need to have an extended debate about these techniques here05:19
truluxi agree05:19
=== lamont_r knows of at least one exploit that did not use any code not found in the attacked application
mdzas I asked before, what is the decision that needs to be made by the board?05:19
pittithis should be more about cooperation05:19
truluxgo forward to what we are talking about05:19
bluefoxicylamont_r:  ASLR from PaX05:19
pittilamont_r: sure, it leaves holes; as I said, nothing is perfect :-)05:20
pittitrulux: do you really think we need a formal statement right now?05:20
pittitrulux: so far our inofficial cooperation works quite nice, or not?05:20
bluefoxicylamont_r:  you'd have to guess where the actual code exists.  You can defeat ASLR by injecting code, which takes us back to PaX' executable/writable separation.05:20
pittiI think we do need an official statement as soon as we officially support it05:21
lamont_rbluefoxicy: off topic05:21
bluefoxicylamont_r:  yes, sorry, i'm getting ahead of the conversation.05:21
mdzif there isn't a decision to be made by the tech board, then we need to move on05:21
truluxpitti, yes, but i would like an official statement05:21
mdzso if there is, please speak up05:21
pittitrulux: okay05:21
truluxok, let me package the wrappers and upload them somewhere05:22
truluxbtw, it would be great to maintain a line of only pax+selinux packages05:22
truluxkernels with non-vanilla selinux/lsm stuff05:22
pittitrulux, bluefoxicy: what is your idea of an "official" statement?05:22
truluxfor ex.05:22
pittitrulux, bluefoxicy: as already said, we don't need to discuss the technical details here. Just the strategic ones05:23
Kamionif no-one is going to answer mdz's question, perhaps this discussion could move elsewhere.05:23
=== fabbione gets some chips
truluxi have finished the development of a TPE subsystem with LSM, so, it can replace grsec's TPE in an only-selinux kernel package05:23
pittitrulux: pleeeease, no tech here05:24
truluxok, sorry05:24
elmoTRULUX/PITTI/BLUEFOXICY: PLEASE ANSWER MDZ OR MOVE ON, KTHXBYE05:24
mdzthe sort of things which would be under the domain of the tech board would be: including packages in the distribution, technical standards for packages, release feature goals05:24
truluxmdz, the decision should be: 1) support or not and collaborate with hardened debian05:24
bluefoxicypitti:  a page somewhere accessable that notes that Ubuntu is at least "examining the potential for proactive security enhancements that stop attacks before they happen" would be vague enough to not create a sense of immediate commitment, but would give the userbase something to look forward to, I think.05:24
mdzif none of those apply to this discussion, then it is not a technical board matter05:24
truluxmdz, i'm answering05:25
mdzthere seems to already be consensus on the technical aspects of this project05:25
bluefoxicypitti:  It'd also give somewhere for people to check back at once in a while to see if specific release goals were made wrt that05:25
trulux2) decide on how to deploy proactive security enhancements05:25
=== daniels [~daniels@amnesiac.heapspace.net] has joined #ubuntu-meeting
mdzthe packages will go into universe, we won't make this a feature goal for Hoary (far too late)05:25
trulux3) stablish a work team05:25
truluxkay05:25
mdzwhat was 1) ?05:26
ogra 1) support or not and collaborate with hardened debian05:26
Kamionteams are a matter for the community council, and in any case should probably just be blessing an existing group of people who're ready to do the work05:26
mdzwill not be supported for hoary05:26
truluxok05:26
bluefoxicy. . . you know what, stop asking me things, I'm dumb.  every time I try to formulate a coherant statement I get too much going on in my head and it comes out gibberish.05:26
mdzcollaboration is not something which needs official approval; go forth and collaborate at will05:26
pittimdz: +105:27
pittiwe can make an official statement when this stuff is a bit more mature05:27
mdz2) what are the deployment requirements?05:28
pittii. e. working and tested packages in universe05:28
bluefoxicyalright05:28
mdzyou need to rebuild a whole bunch of packages and do a lot of testing, yes?05:28
mdzs/rebuild/build with SSP/05:28
pittimdz: a good TB decision would be to provide some resources for that05:28
pittii. e. having a part of the archive SSP-rebuilt in a separate archive05:28
mdzTB doesn't control any resources as far as I am aware, but I would like to hear what you guys believe you need05:29
mdzand can pass that on in other capacities05:29
truluxok05:29
pittiit would be nice to have a buildd support for that05:29
truluxyes05:29
pittia main-ssp archive05:29
truluxwanna build ;)05:29
mdza great deal more than a buildd is required for proper testing05:30
pittito save resources we should skip universe by now05:30
bluefoxicymdz,pitty,trulux:  deployment of SSP requires rebuilding things with SSP.  As far as I'm concerned, adequate testing would make it ideal to just make all the packages in whichever version is SSP protected SSP protected, unless technical issues cropped up (some packages have bugs and SSP exposes them, so they 'break')05:30
truluxmdz, i agree05:30
mdzunless you only support installation from scratch (and not upgrades from Ubuntu)05:30
elmosurely this comes under the derived distro umbrella?05:30
=== doko [doko@dsl-082-082-190-115.arcor-ip.net] has joined #ubuntu-meeting
pittielmo: sounds like it could fit there05:30
mdzelmo: it falls under the derived-distro-with-different-toolchain umbrella, which is much harder05:30
truluxmdz, we need a good machine for rebuilding packages and maintain chroots05:30
mdzour derivation goals for Hoary only extend to package selection and branding, and not toolchain divergence05:30
truluxas testing packages outside jails is crazy05:31
bluefoxicy. . . i do it  o.o05:31
=== bluefoxicy looks at his machine, and the format count, reaching the hundreds now
bluefoxicy. . . trulux is right, testing packages outside jails is crazy.05:32
truluxbluefoxicy, because you use gentoo and you don't need to maintain something working out the box05:32
trulux;P05:32
mdzplease, one of you write up a wiki page describing your resource requirements for doing a proof-of-concept05:32
truluxmdz, i'm uploading some things, wait please05:32
pittiyes, good idea05:32
pittiand defer this discussion05:32
mdze..g, we need a facility to rebuild everything with a different toolchain, put it in a public archive, allow people to install(?), test it05:32
mdztrulux: ok, so you'll take responsibility for writing that?05:32
pittitrulux: I can assist you wit that05:33
lamont_rmdz: toolchain divergence is only a bootstrapping issue, since the toolchain is just another piece of the archive and chroot.05:33
truluxmdz it's already wrote at http://wiki.debian-hardened.org05:33
truluxpitti, i'm putting the new dev layout on the wiki, just a moment05:33
mdzok, wonderful.  when you've done that, please send me an email05:33
truluxmdz@canonical.com right?05:34
mdzcorrect05:34
pittitrulux: let's sort that out without hurry05:34
pittitrulux: apart from the meeting05:34
mdzyes, take your time05:34
pittinext topic?05:35
mdz3) creation of a team is a community council matter05:35
mdzso please bring that up at the CC meeting one week from today05:35
mdzcome prepared with someone who is willing to volunteer to lead the team05:35
=== skyrider [~skyrider@195.128.178.150] has joined #ubuntu-meeting
mdzThat would seem to address the questions about proactive security.  Thanks to everyone who is putting effort into that project, and those who participated in the discussion05:36
mdzwe need to move on to the next agenda item05:36
mdzwhich has to do with accessibility05:36
hno73 Accessibility at boot: can it be done?05:37
mdzhno73: here?05:37
mdzah, good05:37
hno73This is a scaled back proposal from previous ones05:37
hno73please see: http://www.ubuntulinux.org/wiki/AccessibilityAtBoot05:37
mdzI've skimmed it05:38
Keybukthe question seems redundant; either we add a boot option or not05:38
Keybuk(d-i question, that is)05:38
mdzhno73: what sort of guidance do you need from the technical board?05:38
Kamionhno73: additional d-i questions are generally vetoed, I'm afraid05:39
Keybukotherwise is everything you propose packaged and ready for testing?05:39
Kamionthey will need Mark's approval05:39
mdzif you believe it is achievable to implement this before the FeatureFreeze (4 or 5 weeks?), then I think it would make a fine hoary goal05:39
mdzKamion: that page discusses the live CD, rather than the installation05:39
hno73None of this has been developed yet, but it should be fairly basic stuff05:39
mdzKamion: a convenient loophole ;-)05:40
hno73Though I'm not qualified to do it myself ...05:40
amuhno73: for the liveCD it should be possible, guess for hoary there isnt any time for it.05:40
KeybukI tend to agree, though beware that we'd need to turn off bootsplash if you want a prompt during boot05:40
Kamionmdz: only in a parenthesis, most of it seems to be about the live CD05:40
Kamioner, the install CD05:40
Keybukalso a lot of the features seem GNOME-specific, and there's already an accessibility dialog to configure those ?05:40
mdzhno73: the technical board doesn't control development resources, so if there isn't anyone to do the work (yet), we don't have much to talk about here05:40
mdzhno73: however, feel free to contact me via email with a bounty proposal05:41
mdzhno73: we can post it on the website, and if you know anyone who might be interested in doing the implementation, I can contact them on behalf of Canonical05:41
hno73mdz: ok, will do05:41
hno73It's just that the Ubuntu web page sais: "Ubuntu includes the very best in translations and accessibility infrastructure"05:42
mdzthat is one of our goals05:42
hno73and we're quite far from that ATM05:42
mdzagreed05:43
mdzthe major goals for the Hoary release were established months ago, and need to be nearing completion at this stage05:43
mdzI think there is time to do an accessible live CD, if there is someone to do the work05:44
=== seb128 [~seb128@ANancy-151-1-45-42.w83-196.abo.wanadoo.fr] has joined #ubuntu-meeting
mdzbut the existing development resources are pretty much allocated for the Hoary timeframe05:45
mdzmoving on05:45
mdzfabbione: kernel?05:45
fabbionemdz: perhaps we can postpone the kernel stuff to this evening meeting?05:45
mdzit sounds like you're proposing a team05:45
fabbionei think it's more appropriate for the other05:45
fabbionewell also..05:45
mdzin which case it should be the CC meeting05:45
fabbionelet's skip the kernel for now05:46
mdzok05:46
mdzsparc?05:46
fabbioneyes05:46
fabbionethis TB...05:46
fabbionewell i have main done since a long while now05:46
fabbionetested sarge -> hoary upgrades05:46
fabbioneinstalled from scratch....05:46
fabbioneonly a few glitches here and there05:46
mdzare you proposing that sparc become an officially supported architecture for hoary?05:47
fabbionemainly because of a few packages that i didn't spot from universe and that should be instead moved to main05:47
fabbionei want to propose at least its inclusion in the archive05:47
fabbione1) main is up and running05:47
fabbione2) it will free a bunch of my resources to test installations05:48
mdzok, I have no problem with it being part of the archive05:48
fabbione3) i could start building universe05:48
mdzand I believe Mark approved it as well05:48
fabbionemy original proposal was to have a separate archive for non-official arches...05:48
fabbioneand Mark seconded that05:48
=== Keybuk has no problem either
mdzoh?05:48
mdzelmo: thoughts?05:49
fabbionemdz: something like sparc.ubuntu.com05:49
fabbionewhere you see only sparc binaries05:49
Kamion(and arch: all, presumably)05:49
fabbioneto avoid to pollute the mirrors with an arch that might as well disappear if it doesn't takeoff05:49
mdzwhat would the idea be?  to make it easier to mirror only official architectures?05:49
fabbioneKamion: clearly05:49
fabbionemdz: an arch is still a few GB05:49
elmomdz: I'm quite happy to do either, I just didn't have time at Mataro.  doing it separately requires some work, which is why it didn't get done05:50
fabbioneand if for example in 2 months there will be nobody doing sparc...05:50
mdzelmo: which do you feel makes more sense?05:50
Keybukwould we use billie for this?05:50
fabbionewe don't want to kill the mirror with it05:50
mdzbillie?05:50
elmoKeybuk: not for one arch, probably not no, I can just hack up the two mirror masters to ignore sparc and create a separate sparc.ubuntu.com05:50
elmomdz: personally, I'd put it straight in.  it's a very stable arch, it's not going to be flushed.  if nothing comes of it, nothing comes of it.  the mirror's already and insane size05:51
fabbioneelmo: yup.. we know :-) i am just taking up again the discussion to reach a full consensum with an updated status05:51
Keybukmdz: the bit of dak Kinni wrote to do second-class-citizen05:51
lamont_rmdz: yeah, it's not like it's hppa or something.05:51
elmofabbione: I know, you know, mdz didn't tho, and he asked :)05:51
mdzelmo: your call, as far as I'm concerned05:51
fabbioneelmo: i am happy with both the solutions05:52
elmogar, let's just go with sparc.ubuntu.com - it's what we previously agreed on - I will get it done this weeke05:52
fabbionei am anal to avoid problems later if something "goes wrong"05:52
elmos/e$//05:52
lamont_relmo: although for actually populating the real archive, it'd be nice to use fabbione's archive to seed chroots and upload from that.05:52
mdzelmo: do we have a policy that all the builds should happen on the LAN?05:52
elmomdz: I'd like to make one, certainly for supported architectures05:52
elmobefore sparc.ubuntu.com merges, i'd like to have it rebuilt on our buildds05:53
=== trulux [~lorenzo@67.Red-80-25-56.pooles.rima-tde.net] has joined #ubuntu-meeting
truluxkernel oops05:53
truluxsorry05:53
lamont_relmo: agreed05:53
fabbioneelmo: agreed too.05:53
mdzok, but for sparc,ubuntu.com, what will we do about builds?05:53
fabbioneeven if i trust the work i did, i am not as experienced as lamont_r and you05:53
fabbionemdz: i could ship my sparc to the DC if required...05:53
elmomdz: use fabbione's for now, if he's happy to do that?  getting our own buildds is predicated on sparc gaining some momentum05:54
fabbioneit's a U105:54
lamont_rfabbione: and a full rebuild is always a good thing, unless it's going to be pushed on the mirrors05:54
mdzelmo: use fabbione's, and have him download sources from the DC and upload binaries there?05:54
mdzelmo: or ship it over?05:54
fabbionemdz: that's what i already do05:54
mdzfabbione: you upload binaries already? where do they go?05:54
elmomdz: fabbione's remotely makes more sense to me, if he's happy to do it05:54
elmoI don't see much sense in shipping machines around - AFAICR that'd be reasonably expensive05:54
fabbionemdz: people.u.c/~fabbione/sparc/05:54
mdzok05:55
mdzsounds like you guys are already in agreement about what to do, and it sounds fine to me05:55
elmoif we're going to do sparc long term, we'll get machines within a couple of days05:55
mdzbasically moving ~fabbione/sparc/ to sparc.ubuntu.com05:55
elmo(for the DC)05:55
lamont_relmo: does taht require some tweaks in the signature checking?05:55
fabbionelamont_r: my .changes are all signed05:55
mdzwhen sparc.ubuntu.com is up, we can make an announcement about it05:55
elmolamont_r: yeah, it' will05:55
mdzas an alpha test or something05:56
fabbionei only need to tell elmo the key :-)05:56
fabbioneelmo: just remember that i don't have a pool over there...05:56
fabbionethere are only plain _sparc.deb05:56
lamont_rfabbione: good. (but our signatures are only good for source uploads, and making your sig ok for binary uploads would be a policy issue...)05:56
elmofabbione: as long as you have .changes, I don't care05:56
mdzfabbione: as long as you promise not to upload other binaries ;-)05:56
lamont_rfabbione: so he needs to make your sig ok for sparc binary uploads, but not the others.05:56
fabbioneelmo: sure.. i have all the history of stage205:56
mdzok, it sounds like we're finished with the meeting05:57
fabbionemdz: i am not THAT INS4N3... YOU KNOW, DON'T YOU? :P05:57
fabbionelamont_r: gotcha05:57
mdzwe're finished with the set agenda, anyway05:57
mdzany last-minute items?05:57
lamont_rfabbione: hell - I upload binaries every now and then... I'm glad for the security blanket.05:57
fabbioneKERNEL ARFH KERNEL ARFH05:57
KeybukHoary meeting, is that in here at 2200 UTC?05:58
fabbionelamont_r: i don't... remember.. i am anal.. X.. kernel... hundreds of users knocking on my door....05:58
mdzKeybuk: yes05:58
mdzfabbione: we agreed to defer that to CC (for the team) and the hoary devel meeting (for anything else)05:58
=== mako_ [mako@micha.hampshire.edu] has joined #ubuntu-meeting
fabbionemdz: i know.. i was just kidding :-)05:58
mdzso, hearing none, the tech board meeting is adjourned05:59
mdzthanks, everyone05:59
lamont_rthanks mdz05:59
fabbionethanks guys!05:59
=== ..[topic/#ubuntu-meeting:mdz] : Tuesday 4 January 2005 at 1600 UTC: Technical Board -- http://www.ubuntulinux.org/wiki/TechnicalBoardAgenda. Tuesday 18 January 2005: Community Council meeting -- https://www.ubuntulinux.org/wiki/CommunityCouncilAgenda
fabbionecya in a few hours05:59
seb128thanks05:59
pittidid I understand that right?05:59
pittiwe don't have hoary meeting today?05:59
ograpitti: nope....wrong :)05:59
fabbionepitti: at 22:00 UTC today05:59
=== ..[topic/#ubuntu-meeting:Keybuk] : Tuesday 18 January 2005 at 1600 UTC: Technical Board -- http://www.ubuntulinux.org/wiki/TechnicalBoardAgenda. Tuesday 11 January 2005: Community Council meeting -- https://www.ubuntulinux.org/wiki/CommunityCouncilAgenda
seb128pitti: tonight, 2200 UTC06:00
pittifabbione: because of <mdz> fabbione: we agreed to defer that to CC ...06:00
mdzKeybuk: thanks ;-)06:00
pittiah, ok06:00
fabbionepitti: it was for the KERNEL stuff :-)06:00
=== ..[topic/#ubuntu-meeting:Keybuk] : Tuesday 4 January 2005: Hoary Goals meeting. Tuesday 11 January 2005: Community Council meeting -- https://www.ubuntulinux.org/wiki/CommunityCouncilAgenda. Tuesday 18 January 2005 at 1600 UTC: Technical Board -- http://www.ubuntulinux.org/wiki/TechnicalBoardAgenda.
pittifabbione: sure, sorry06:00
fabbioneno problem06:01
=== ..[topic/#ubuntu-meeting:Keybuk] : Tuesday 4 January 2005 at 2200UTC: Hoary Goals meeting. Tuesday 11 January 2005: Community Council meeting -- https://www.ubuntulinux.org/wiki/CommunityCouncilAgenda. Tuesday 18 January 2005: Technical Board -- http://www.ubuntulinux.org/wiki/TechnicalBoardAgenda.
sivangthere's a goal meeting again?06:01
Keybukmdz: do you want to propose an alternate time for next week's tech-board meeting?  one more friendly to you?06:01
mdzKeybuk: yeah, I'll take that to ubuntu-devel06:01
Keybukuh, two-weeks even :p06:01
Keybukokies06:01
=== pitti [~martin@195.227.105.180] has left #ubuntu-meeting []
=== seb128 [~seb128@ANancy-151-1-45-42.w83-196.abo.wanadoo.fr] has left #ubuntu-meeting ["I]
=== thom [~thom@amnesiac.heapspace.net] has joined #ubuntu-meeting
=== silbs [~sbsm0084@adsl-2-195-2.mia.bellsouth.net] has joined #ubuntu-meeting
truluxmdz, http://wiki.debian-hardened.org/Development_layout_organization06:09
truluxmdz, it's still a draft06:09
truluxand now i must go06:09
truluxsee you later!06:09
=== mvo [~egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting
=== hno73 [~Henrik@henrik.gotadsl.co.uk] has left #ubuntu-meeting []
=== silbs [~sbsm0084@adsl-2-195-2.mia.bellsouth.net] has left #ubuntu-meeting []
=== thom [~thom@amnesiac.heapspace.net] has joined #ubuntu-meeting
=== thom [~thom@amnesiac.heapspace.net] has joined #ubuntu-meeting
=== bluefoxicy [~bluefox@pcp485126pcs.whtmrs01.md.comcast.net] has left #ubuntu-meeting ["That's]
=== thom [~thom@amnesiac.heapspace.net] has joined #ubuntu-meeting
=== skyrider [~skyrider@195.128.178.150] has left #ubuntu-meeting []
thomdo we have an agenda for this evening?06:51
=== edomat [~edomat@200.80.239.130] has joined #ubuntu-meeting
mdzthom: I have some notes, yeah07:02
=== maskie [~maskie@196-30-110-70.uudial.uunet.co.za] has joined #ubuntu-meeting
=== lamont [~lamont@mix.mmjgroup.com] has joined #ubuntu-meeting
=== zul [~chuck@zul.developer.gentoo] has left #ubuntu-meeting ["Leaving"]
=== lamont [~lamont@mix.mmjgroup.com] has left #ubuntu-meeting ["Client]
=== lamont [~lamont@mix.mmjgroup.com] has joined #ubuntu-meeting
=== zul [~chuck@zul.developer.gentoo] has joined #ubuntu-meeting
=== sladen [paul@starsky.19inch.net] has left #ubuntu-meeting []
=== sladen [paul@starsky.19inch.net] has joined #ubuntu-meeting
=== amu [~amu@amu.developer.debian] has left #ubuntu-meeting []
=== johnlevin [~johnlevin@dsl-80-42-70-105.access.uk.tiscali.com] has joined #ubuntu-meeting
=== mvo_ [~egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting
=== mdz [~mdz@69-167-148-207.vnnyca.adelphia.net] has joined #ubuntu-meeting
=== lamont_r [~lamont@phantom.acmeps.com] has joined #ubuntu-meeting
=== pitti [~martin@195.227.105.180] has joined #ubuntu-meeting
=== Mithrandir [~tfheen@vawad.err.no] has joined #ubuntu-meeting
=== seb128 [~seb128@ANancy-151-1-45-42.w83-196.abo.wanadoo.fr] has joined #ubuntu-meeting
=== skyrider [~skyrider@195.128.178.150] has joined #ubuntu-meeting
=== hno73 [~Henrik@henrik.gotadsl.co.uk] has joined #ubuntu-meeting
=== Simira [~rpGirl@ti200710a080-5534.bb.online.no] has joined #ubuntu-meeting
=== amu [~amu@amu.developer.debian] has joined #ubuntu-meeting
=== Keybuk [scott@descent.netsplit.com] has joined #ubuntu-meeting
=== mdz rings the meeting bell
mjg59mdz: Is there an agenda?11:01
=== fabbione raises his hand
mdzmjg59: a short one, yes11:01
=== mvo_ too
pittiagenda = hoary goal list?11:01
mdzshall we go over the agenda, or just dive in?11:01
Mithrandirwhere's the agenda? :)11:01
ogra+ fabionne and the kernel lovestory11:01
Mithrandir(except for mail, obviously)11:01
mdzfirst item is to review the pending seed changes11:02
=== jdub [~jdub@home.waugh.id.au] has joined #ubuntu-meeting
mdzseed freeze was some time ago11:02
mdzbut we've been fairly lax in tending to seed changes11:02
mdzso if there is anything on there which is urgent for hoary, we should discuss it and tend to it now11:02
fabbione2.6.10 as deafult kernel?11:03
jdubthe proposals pages need to be farmed for seed updates, i can do that if you want11:03
dokoI need to update the seed for the ISDN stuff, after the meeting11:03
ogragaim-dev is gone into experimenal today, could that be included ?11:03
mdzI'm looking at them now11:03
mdzhttp://www.ubuntulinux.org/wiki/BaseSeedProposals http://www.ubuntulinux.org/wiki/DesktopSeedProposals http://www.ubuntulinux.org/wiki/SupportedSeedProposals http://www.ubuntulinux.org/wiki/ShipSeedProposals11:03
mjg59We need vbetool for ACPI, but I only got that packaged last week11:03
thomi need to update the seeds from the meeting11:03
jdubis there much new stuff since going through them at mataro?11:03
thomwill do so after the meeting11:04
mdzsome of them have to do with feature goals, I think11:04
thomuh, the first meeting there was the BOF in mataro11:04
mdzoh, those pages don't include the seed updates whihc were already made?11:04
mdzgah11:04
mdzok, we'll defer that, then.  maybe we don't have as much to do as I thought11:04
mdznext agenda item is getting caught up on Debian merges11:05
mdzUpstreamVersionFreeze is scheduled for tomorrow11:05
lamont_rmdz: meaning all the sync's need to be current by tomorrow?11:05
mdzwe should either set a later deadline to allow us to get caught up with merges (which inlcude some new upstream versions), or delay UVF slightly so that we can catch up11:05
mdzjdub: what's your opinion?11:05
seb128ogra: that's a binary package of gaim, right ? 11:05
ograseb128: nope, i thought it were finally the missing headers...11:06
=== ogra looks
jdubmdz: if we delay UVF, won't that mean more merges to catch up with?11:06
seb128ogra: the headers come from gaim, so that's a binary made from the gaim source package11:06
lamont_rmdz: I would think allowing the rest of the week for merges of the as-of-UVF package versions to get in would do...11:06
Keybukmdz: bear in mind that shit's going to keep falling until we turn off the hose :o)  so we should decide how long we want to "catch up" and turn off lorraine N-<that number> days beforehand11:06
mdzjdub: yeah, it's mostly a matter of naming I suppose11:06
mdzjdub: the question is how UVF should apply to merges11:06
mdzKeybuk: right11:06
mdzbut since  everyone has only just returned from holidays, we don't have N days11:07
jdubUVF should be the sync-stopper, merges we can handle as bugfixes11:07
mdzthere are 89 open merge bugs11:07
mdzwe should be able to kill them in a day or two11:07
mdzjdub: ok, but we should have a deadline for them11:07
pittiso, sync days tomorrow and the day after?11:07
=== lamont_r plans a merge-rampage for after the meeting
mdzsince they do introduce a lot of new code from upstream11:07
ograseb128: http://people.debian.org/~robot101/gaim/dists/experimental/main/source/11:07
Keybukelmo: about?11:07
elmoyeah?11:08
mdzUVF + 7 days should be more than enough11:08
Mithrandirogra: what's in that?  gaim-dev?11:08
mdzjdub: work for you?11:08
Mithrandirogra: if so, I have the patch and we could ubuntu it.11:08
fabbione<Keybuk> elmo: about?11:08
fabbioneops11:08
fabbionesorry11:08
Keybukelmo: how much time do you need to lobotomize lorraine so that syncs stop, but needs-merged.txt still gets updated?11:09
jdubmdz: was going to suggest that myself :)11:09
mdzKeybuk, elmo: did you talk about the MOM/lorraine stuff, to provide for ongoing merges after new versions are no longer synched?11:09
mdzjdub: ok, done.  please add it to the wiki schedule11:09
ograMithrandir: that would be great....that should be the headers and such...needed for lots of little tools tat just come up on gnomefiles.org11:09
mdzonce UVF is executed, I'll assign the merge bugs out11:09
jdubwe need a clayton's elmo for handling archive-related changes when he's away11:09
mdzanother question is what to do about universe merges11:10
elmoKeybuk: very little11:10
elmoit's probably commenting out one line [tho I haven't checking] 11:10
seb128Mithrandir: you say that you're going to update gaim ? (I planned to do this but if you are going to do it no problem with me :p)11:10
fabbionemdz: i think we can be more flexible with universe...11:10
jdubmdz: last time around we took version sync requests fairly regularly11:10
Mithrandirogra: I've been waiting for it to pass through NEW in Debian, that's why it hasn't been done anything with.11:10
Mithrandirseb128: I could do it, sure.11:10
mdzfabbione: agreed, but we need to connect the work-to-be-done with some people to do it11:10
ograMithrandir: as long as it can get in hoary its fine :)11:10
mdzsince we'll be focusing on main11:10
Mithrandirseb128: I guess this is just the gaim-dev package currently missing?11:11
fabbionemdz: we don't have master-of-universe, do we?11:11
mdzthis should be MOTU territory, but MOTU is a bit vaporous at the moment11:11
lamont_rmdz: that's 89 merge-_MAIN_ bugs open?11:11
mdzthat's a next-tuesday discussion, I suppose11:11
Kamionback, sorry to be late11:11
jdubmdz: so while we can be less stringent about bug priority and so on, we should have people willing and able to test the stuff they propose for update11:11
mdzlamont_r: 89 total, maybe 75 main11:11
lamont_rok11:11
dokomdz: I have to catch up on the python version change for universe, currently it's done for main only (and some packages from universe)11:11
mdzdoko: that's something we should farm out to MOTU if possible11:12
dokosorry, MOTU?11:12
elmothere are python packages in universe?? how did they escape sabdfl's PYTHONWILLALLBEINMAINKTHXBYE streak?11:12
lamont_rmasters of the universe11:12
thommaster of the universe11:12
mdzdoko: the community-based team formed to maintain universe11:12
mdzelmo: we talked him out of some of them11:12
mdzone other quick item before we dive into feature goals11:13
jdubmdz: are we going to finish the sweep of python in main stuff to sanitise it a bit?11:13
mdzdoes anyone here care dearly about mozilla-thunderbird?11:13
jdubmdz: what's up with it?11:13
Keybukmdz: sabdfl, oh, wait, "here" :p11:13
fabbione<- i do...11:13
thomi care deeply about it burning in the utmost fires of hell11:13
Mithrandirmdz: a bit, yes.11:13
jdubmdz: oh, wanting 1.0?11:13
mdzjdub: you mean, now that we have some ammunition to show why it's not a very good policy to blindly include python-*? :-)11:14
mdzthunderbird needs love11:14
mdzlots of it11:14
fabbionemdz: i use thunderbird... but i don't love it enough to maintain YA5GSP11:14
elmoI think thom is the ideal candidate to show it all the love, care and attention it needs11:14
jdubmdz: well, we started looking at stuff in mataro, would be nice to finish it off11:14
mdzfabbione: thunderbird is only ~30M ;-P11:15
seb128yeah, thom !11:15
thomurgh11:15
thomi can't take two mozilla packages i don't use. firefox is quite enough :P11:15
dokowhat was the criteria for inclusion of python stuff in warty?11:15
mdzjdub: yes, I think we should; I think we can do it equally well between the two of us after the meeting or so, though11:15
fabbionemdz: right.. gimme ooo and glibc.. so i can beat the record for the "one man with the biggest (source) package"11:15
jdubmdz: suggest we ask for help with thunderbird, upgrading to 1.0 as well11:15
mdzfabbione: if no one will stand behind it, it is going to rot, and I will propose that we remove it from main for hoary11:15
jdubmdz: sure, didn't want to start a foodfight11:16
fabbionemdz: fine for me...11:16
fabbionemove to out of main...11:16
fabbionei use it.. it doesn't mean i want it in main ;)11:16
jdubmdz: that's a good threat to get someone to help with it :)11:16
jdubmdz: but it's a worthy thing to have in main11:16
Kamionhey, mozilla-thunderbird is in ship11:16
=== Kamion gleefully seconds ditching it
mdzjdub: ok, will you send a call for help to some appropriate places?11:17
elmoerr, there's a lot of user love for thunderbird11:17
lamont_rmdz: push the big red button11:17
elmonot saying that should necessarily matter, just unhelpfully pointing it out11:17
Kamionelmo: true *grump*11:17
jdubmdz: yes11:17
Mithrandirhow bad is the bug list for m-t?11:17
fabbioneMithrandir: i think longer than the one for a1.311:17
lamont_rthe other big question on that front is whether it's 0.9 or 1.011:17
mdzonly about 15 bugs11:18
mdzbut it needs a new upstream version, review of the bugs, matching them to upstream, working with users to clarify and resolve the bugs, etc.11:18
mdzi.e., love11:18
mdzlamont_r: hmm, good point.  if we're going to update it, it should be close to UVF11:18
Mithrandirmdz: I could give it a shot, I think losing it would a) look bad and b) be a shame.11:19
lamont_r1.0 has been out for a bit, but not packaged for debian11:19
mdzjdub: willing to make an exception for t-bird 1.0 vs. UVF in order to allow time for someone to step up?11:19
mdzMithrandir: do you use it?11:19
Mithrandirmdz: somewhat, yes.11:19
jdubmdz: relativelys short amount of time, yeah :)11:19
Mithrandirmdz: it's my local GUI client of choice and I use it for RSS feeds.11:20
jdubmdz: keep in mind it's been released for some time11:20
=== fabbione scratches his head.. looking at Mithrandir and thinking about Simira
mdzMithrandir: it's yours if you want it11:20
ogralol11:20
mdzMithrandir: if you want to look at it, but hand it off to someone else if they step forward, that's fine too11:20
Simiradid I lose something here?11:20
=== Mithrandir wonders what got lost in fabbione's Itaglish-to-Norwaglish translation.
fabbioneSimira: nevermind.. i will tell you later11:21
Mithrandirmdz: ok11:21
Simirafabbione: you better.11:21
mdzgreat11:21
jdubMithrandir: if you look at it, can you give me an idea of how badly broken it is before i announce? :)11:21
Mithrandirjdub: willdo11:21
Simirahey, how about sharing your love with firefox as well?11:21
=== __daniel [~daniel@td9091ba7.pool.terralink.de] has joined #ubuntu-meeting
thomi'm gonna apply love to firefox in the next couple of days11:22
mdzSimira: firefox gets so much love from thom, it would burst if any more were applied11:22
Simiraok, nice11:22
thomi even have patches from upstream for some of the bugs ;P11:22
fabbionenobody wants to give love to the kernel maintainer?11:22
pittithom: please tell me you have a patch for the window injection :-/11:22
mdzwho could fail to love fabio?11:22
ografabbione: we all love you....11:23
thompitti: i wish :(11:23
fabbione:D11:23
Mithrandirfabbione: you have a gf. :)11:23
=== sivang loves fabbione
=== pitti hugs fabbione
mdzone other project which needs a home:11:23
dokofabbione: too late you're getting married :-P11:23
=== bwb [~nate@ip68-5-253-106.oc.oc.cox.net] has left #ubuntu-meeting []
fabbioneMithrandir: a fiance ;)11:23
Simirafabbione: of course we love you *hugs*11:23
mdzthe LSB init script modifications need some serious review; many of them are buggy in various ways11:23
Mithrandirfabbione: gf being a subset of fiance.11:23
lamont_rfabbione: we all love you.11:23
pittimdz: buggy in which sense?11:23
lamont_ras long as the kernels keep coming. :)11:23
=== fabbione feels the love...
thommdz: oh dear lord11:23
fabbioneahha11:23
=== sivang ponders to the log to see what he missed.
mdzthey need a thorough review by someone very comfortable with shell scripting11:23
fabbionethom: like they don't work on serial console...11:24
mdzpitti: changing the behaviour of the script11:24
lamont_rpitti: abort in the presence of errors, as opposed to saying 'fail'11:24
=== lamont_r raises his hand
Keybukmdz: we're going usplurge for hoary still, yes?11:24
Kamion(why don't they use 'trap', anyway?)11:24
thomor frame buffer in some circumstances, iirc11:24
mdzKeybuk: hopefully11:24
Keybukso we could kinda accidentally revert the nathaniel infection and nobody would notice?11:24
lamont_rKamion: not all failures are that trivial to deal with11:24
mdzKeybuk: well, for usplash n+1, we'll need to put it back11:24
lamont_rKeybuk: that would reduce the merge count...11:25
mdzso that the scripts communicate with usplashd11:25
Kamionlamont_r: sure, but it would reduce the set +e evil that's been introduced in a number of them11:25
lamont_rset +e is wrong11:25
Kamionwhich is basically only so that it can go on to test $?11:25
lamont_rmdz: I'll take the script review11:25
mdzlamont_r: ok11:25
Keybukphew, I was about to volunteer, thanks lamont :p11:25
fabbioneahah11:25
thomthe whole thing really needs to get rethought, there're also about 50 packages that got missed in warty11:25
lamont_rKeybuk: please modify your patch breaker to sort out init.d patches. kthanksbye11:26
mdzthom: that too, but first priority is to fix the broken ones11:26
Keybuklamont_r: it does11:26
lamont_rawesome11:26
thomyeah11:26
Keybukhttp://people.ubuntu.com/~scott/patches/*_lsb-init.patch11:26
mdzlamont_r: yeah, you'll be reviewing that stuff anyway, so you can look at those along the way11:26
mdzperfect11:26
lamont_rmdz: right11:26
mdzso, feature goals11:27
mdzwe ran down the list in Mataro11:27
mdzand of course, in the process, received some new must-have feature goals11:27
elmoKeybuk: is that still branding damaged? :)11:27
Kamion(if anyone's editing HoaryGoals, I just saved it; reload)11:28
mdzMark's list is here: http://www.ubuntulinux.org/wiki/MarksHoaryGoals11:28
Keybukelmo: yeah, it's on my TODO list11:28
mdzI need to finish merging that with HoaryGoals11:28
lamont_rbrb11:29
mdzbut among the things which are being bumped to the top of the list are the hardware database and launchpad integration11:29
pittiugh, I should continue to work on hwfu11:30
Kamioncan I request that somebody else take the rest of the UTF-8 task? I've done the glibc generate-UTF-8-locales-on-upgrade bit, but I received two newish hoary goals in Mataro11:30
ograme too...11:30
Kamionor at least two things that weren't previously on the list11:30
mdzoh, and automated testing11:30
mdzKamion: yes, I think that's appropriate11:30
jdubmdz: i thought automated testing was right off?11:30
lamont_rmdz: ISTR automated testing landing in my lap11:31
mdzjdub: that's not what Mark said11:31
mdzunless he changed his mind11:31
MithrandirKamion: the UTF8MigrationTool and such?11:31
mdzMithrandir: yes11:31
jdubi must have missed that mind change somehow11:31
MithrandirKamion: I've actually considered doing it, me being one of the few people who bitch and complain about the beast.11:31
mdzMithrandir: it's bountyable11:31
Mithrandirmoney's always welcome11:32
Mithrandir(:11:32
=== Kamion would certainly be more than happy to trust whatever Mithrandir does on that front
mdzok, Mithrandir, let's discuss details after the meeting11:33
mdzogra and pitti have been working on the hardware database stuff11:33
Mithrandirmdz: ok.11:33
mdzpitti, you already have a lot on your list, so I would prefer that the work be distributed to others if possible11:34
pittiogra: would you be interested in continuing with hwfu? do it together with me?11:34
mdzpitti: of course, if you're very passionate about it, I don't mind if you want to work on it, but you have some heavy goals already11:34
pittimdz: well, I can defer the ssp/grsec stuff a little, it's no hoary goal11:34
pittimdz: I would not mind giving away hwfu11:34
pittimdz: the basic architecture is there11:34
pittiand it works pretty well11:34
ograpitti: sure, i was planning to....if i finally got the utf8 in the lockscreen win ready....but i think i can drop that in in the state it is11:34
pittiit's now a matter of writing plugins for various backends11:35
mdzpitti: you have already signed up for language packs, automated testing and hardware database in addition to ongoing security support etc.11:35
pittimdz: right; before christmas I did nothing else apart from security udpates11:35
pittimdz: but now it calmed down a little11:35
pittimdz: today I talked to carlos about lang packs11:35
pittimdz: and I think I need some time to set up the automated building of the debs11:35
mdzpitti: automated testing has a more flexible schedule because it isn't going into the release11:36
fabbionebrb11:36
pittiI think lang packs should be my first priority now11:36
mdzpitti: just remember that security work tends to come in large, unexpected and unwelcome batches :-)11:36
pittias soon as rosetta is able to export new stuff, I setup the automated building, I guess11:36
pittimdz: I experienced that :-)11:37
mdzso make sure that you budget time for it, so that it doesn't cause feature goals to slip11:37
pittiyes11:37
mdzjdub, mvo: how are the package management tools coming?11:38
ograpitti: as long as i can bug you with one or the other question....i'll take over....11:38
pittiogra: sure11:38
ogra:)11:38
pittiogra: I mirrored the arch archive, so you can read it11:38
mdzjdub, mvo: in particular, when can we add them to the default desktop?11:38
mvo_mdz: I think upgrade-notifier, ubuntu-cd detection and the new sources.list editors is pretty nice11:38
jdubmdz: we should do immediately11:38
mvo_agreed11:38
ograpitti: great.... i'll check it out11:38
jdubmdz: there are still things to clean up, but we should add them now11:38
Keybukaren't we still integrating them into one super-tool ?11:38
jdubmvo_: we should meet later and go over the changes11:38
mdzok11:38
mvo_jdub: ok11:38
mdzso, some seed changes, and adding upgrade-notifier to the default session, right?11:38
jdubmdz: yeah11:38
mvo_yes11:38
mdzoh, and adding gnome-app-installer to the menu11:38
jdubit's in the menu, but in the wrong place ;)11:39
Keybukcan we not rename it to update-notifier?11:39
mdzjdub: what about the infrastructure for providing updated .desktop files to g-a-i?11:39
Keybukconfusing the terms "update" and "upgrade" is bad, m'kay11:39
jdubmdz: going to do that when my mirror completes :)11:39
mdzjdub: or are we going to wimp out on that and do it by hand for hoary?11:39
=== BlackHussar [~chatzilla@216.52.211.100] has joined #ubuntu-meeting
MithrandirKeybuk: people don't know the difference anyhow; apt-get update; apt-get upgrade confuses people, it seems.11:40
jdubmdz: it'll probably be fairly by-hand, but it'll still be a script to run over the archive11:40
mdzKeybuk: I agree, the naming could probably use some work11:40
KeybukMithrandir: but right now we're confusing both in the same sets of tools11:40
Keybukat least using one term exclusively would be nice11:40
mdzeither update-manager and update-notifier, or upgrade-manager and upgrade-notifier11:40
MithrandirKeybuk: I agree11:40
jdubupdate, preferably11:40
mdzwhich one is less painful to modify?11:40
jdubupgrade-manager is not exactly optimal for upgrades yet ;)11:40
mdzMithrandir: apt-get update will become more or less obsolete with upgrade-notifier ;-)11:40
Mithrandirmdz: sed -i s,update,upgrade,g $(find -type f) in the source tree of one of them? :)11:41
mdzjdub: what needs to be done there?11:41
mdzjdub: is ross burton around?11:41
mvo_jdub: what's wrong with upgrade-manager?11:41
jdubmdz: ross did gai, mitario did the update manager11:41
mdzoh, right11:41
jdubmvo_: it's not optimal for upgrades (it's fine for updates)11:41
mdzjdub: s/// then11:41
jdubmvo_: but i think that's post-hoary11:42
mvo_jdub: ahh, agreed11:42
jdubmdz: mvo and i will give status report after discussing it11:42
mdzjdub: didn't we just finish agreeing that "update" and "upgrade" were easily confused? ;-)11:42
mdzjdub: ok11:42
mvo_I'll rename upgrade-notifier to update-notifier then11:42
jdubmdz: they are, because they mean different things11:42
mdzthere is a new handwavy goal to integrate the desktop with launchpad11:42
mvo_I hope that makes everyone happy :)11:42
mdzthis is the Help->report a bug, Help->translate this app sort of stuff11:42
jdubmvo_: don't start that just yet tho ;)11:43
mvo_jdub: ok :)11:43
mdzI hope that when we spec it out, it will reduce to adding some standard menu entries which open the browser with certain URLs based on the package name11:43
mdzbut at any rate, we need someone to do the work11:44
mdzjdub: do you have a bounty candidate for this?11:44
jdubmdz: yeah, a few come to mind11:44
jdubmdz: we just want help menu changes, right?11:44
mdzjdub: it hasn't been formally specified, but yes, I hope it'll boil down to that11:45
jdub(at this stage, we can do more later)11:45
dokomdz: if that can be done in February, I'll look at it.11:45
mdzjdub: let's get with Mark soon and nail down exactly what he expects for Hoary11:45
mdzdoko: this needs to be done by feature freeze, which is 1st week of feb, I think11:45
Keybukmdz: heh, I've been trying to get Mark to agree on URLs for HCT for a while now ... :p  let me know how you get on11:46
mdzand since that date has come up, I'd like to ask if anyone is in trouble with their feature goal assignments11:46
KamionI'm a little worried about kickstart, but it should be achievable at least in skeletal form by then11:47
fabbionemdz, Kamion: i am not 100% sure how much i can dedicate to the kickstart11:47
pittimdz: hw database might not be ready by Feb 111:47
KamionI'm unlikely to be able to give any time to autotesting before feature freeze11:47
mdza few goals can be flexible with respect to feature freeze11:47
mdzthat date is aimed at stuff which is going in the distribution proper11:47
mdzautomated testing can slip11:48
mdz(featurefreeze, that is)11:48
fabbionemdz: i am mostly binded to the 2 things we discussed earlier...11:48
mdzpitti: the collection part of the hardware database needs to be done by feb 111:48
mdzpitti: ogra has said that he can devote time to it, so we'll revisit it after we've talked about that more11:48
mdzs/feb 1/feature freeze/11:48
sivangmdz: I would also like to take a look into the launchpad integration menu stuff, I'll see if I can discuss with jdbub after the meeting. 11:48
pittimdz, ogra: hmm, then we need to speed that up11:48
mdzit's actually the 9th or whatever11:49
mdzsivang: ok, please do11:49
jdubmdz: i have yet to nail down the panel and icon stuff, but that's mostly been due to christmas / new year, etc. i'm going to hammer on that this and next week -> icon stuff at least can slip slightly past the preview.11:49
Keybukmdz: I may have one or two more boot-process changes to speed it up a bit; should be ok by Feb 1 though11:49
mdzKamion, fabbione: so about kickstart11:49
pittiSimira: please finish g-s-t first11:49
ograpitti: will be possible....11:49
pittiSimira: sorry, that wasn't for you11:49
pittisivang: please finish g-s-t first, that's critical11:49
sivangpitti: ofcourse, I just got the idea that the menu thing can wait for feb? 11:50
fabbionemdz: as i wrote above...11:50
mdzKamion: you have taken on a huge load in terms of high-priority goals; is there anything that you can shed to make room for kickstart?11:50
mdzKamion: I think you're most qualified to work on it at this point11:50
Kamionagreed11:50
lamont_rKamion: you're welcome to shed some work my way11:51
Kamionautotesting is really the only primary goal left, I think11:51
thommine also11:51
mdzKamion: I think it goes without saying that you probably won't have time to work on automated testing, so let's take your name off of that11:51
Kamionmost of the rest I've made sizable inroads on or more or less completed11:51
mdzKamion: unless you really want it11:51
Simirapitti: thanks for your trust, but you won't have me to touch that one ;p11:51
mdzkickstart is higher priority in terms of the release schedule11:51
pittiSimira: xchat autocompletion error... :-)11:51
Kamionnah, I expressed half-hearted interest at the meeting and my name ended up on the list. :)11:52
mdzthat's what I thought :-)11:52
seb128pitti: I gave you the command to get a nice completion this morning :p11:52
mdzKamion: what other major pieces are on your plate for pre-feature-freeze?11:52
Simirapitti: I reckoned, yes. :)11:52
mdzKamion: anything where thom or lamont could give you some support?11:52
Kamionin general I think it would be a good idea to get more people involved in installer bugs; I'll see if I can find good introductory pieces to hand out11:52
Kamionthere's no single big piece but a lot of little ones11:53
mdzKamion: if you need to delay bug work to work on features during the next few weeks, that's entirely appropriate11:53
thom(note i can also do itanium testing now)11:53
mdzKamion: but I understand that you probably want to avoid falling behind11:53
Mithrandirthom: lucky you.  Fun with noisy beasts at home, or have you remote access to a Bdale Facilities?11:54
lamont_rthom: d-i currently dies on ia6411:54
fabbionethom: it would be nice if you can start testing the kernel for ia64....11:54
lamont_rMithrandir: he has his very own a500/zx2000 love11:54
Kamionthe other major featurish pieces are the two things Mark brought up in Mataro (first-stage questions, netcfg rf-kill-switch detection) and the low-priority oem stuff11:54
=== zul [~chuck@CPE0006258ec6c2-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-meeting
mdzKamion: will you think on it a bit, and follow up with me, thom and lamont after the meeting to distribute some of that work?11:54
KamionI've been making inroads on the first-stage questions thing and I suspect I'm probably the best person to continue that, but the kill-switch thing could be passed to somebody else11:54
Kamionyes, will follow up11:55
mdzthanks11:55
mdzfabbione: the two things you referred to earlier are the kernel and the other project?11:55
fabbionemdz: yes11:56
Kamionthe other main reason I've been falling behind a little more than expected is getting engaged, which was sort of not on the project plan. :)11:56
mdzfabbione: is there any feature work pending for the kernel, or primarily bugs?11:56
MithrandirKamion: congratulations! :)11:56
lamont_rKamion: as long as she knows what she's marrying into....11:56
Kamionoh, she does11:56
danielsKamion: surely that came way too late after the appropriate freeze ...11:56
KeybukKamion: congrats!11:56
fabbionemdz: no features.. only tons and tons of bugs11:56
mdzKamion: just don't schedule the date for April, OK? ;-)11:57
thomKamion: dude, congrats!11:57
sivangKeybuk: congrets!11:57
Kamionit's August currently11:57
sivangoops11:57
sivangKeybuk: congrats!11:57
dokofabbione: what about the powerpc64 kernel?11:57
jdubKamion: congrats :-)11:57
danielsKamion: congrats, again (so I don't feel left out)11:57
=== Kamion giggles at sivang, I got it :)
seb128congrats :)11:57
sivangerghh irssi completions11:57
ograKamion: congrats !11:57
fabbionedoko: that's low priority11:57
mvo_congrats!11:57
fabbioneKamion: i will tell you how it goes after february... you will have time to reconsider :P11:57
smurfixKamion: conga rats!  ;-)11:57
sivangsmurfix: hehe11:58
jdubKamion: so you won't be needing any high priority bendy goals :)11:58
danielsjdub: bendy totally needs a GUI installer, I think ;)11:59
=== mvo_ chuckles
elmokamions hasn't done the graphical installer yet?????11:59
=== Mithrandir beats elmo with a drainpipe :)
elmo\o/12:00
mdzKamion: how is the hardware detection stuff going?12:00
fabbioneelmo: *cough*sparc*cough*12:00
jdub\u/ <- after drainpipe12:00
=== __daniel [~daniel@td9091b22.pool.terralink.de] has joined #ubuntu-meeting
=== sivang is puzzled about the laugs. who is bendy? :)
Kamion(actually, fwiw: we could call the netcfg rf-kill-switch thing a bug, since it is, I don't know why Mark brought it up during a feature goals meeting)12:00
lamont_rbendy is after hoary12:00
jdubsivang: bendy is the release after hoary12:00
mdzKamion: daniels has his name down for that one, so please feel free to invite him to own up to it :-)12:00
lamont_rbendy badger12:00
=== jdub is writing mail about that now
elmobendy is the object lesson on "why trolling sabdfl is bad, mmkay?"12:00
mdzjdub: please don't send the mail yet; I need time to make my case for a better name12:01
=== elmo looks pointedly at keybuk
sivangjdub: wasn't it grumpy? or was it too grumpy for a name? :)12:01
Kamionmdz: displaying network interface names correctly is the only missing piece I know of12:01
=== mdz scowls at Keybuk
jdubmdz: better than bendy?12:01
mdzjdub: yes12:01
KamionI worked around the framebuffer problem today, which was release-critical12:01
lamont_rsivang: grumy was considered too, well, grumpy12:01
jdubsivang: three dispositive names in a row... grumpy is going to be used for something else.12:01
Keybukjdub: that shouldn't be too hard12:01
mdzKamion: did you get my mail with the macio hotplug stuff?12:01
jdubmdz: you're being serious?12:01
Kamionmdz: yes, haven't had time to do anything serious with it yet :-/12:01
mdzjdub: you mean you don't think it's the worst one yet?12:01
Kamion(but will do)12:01
mdzKamion: just wondering whether you think it's something we should shoot for for hoary12:02
danielsmdz: christ, how'd my name get there?12:02
danielsmdz: (gui installer)12:02
jdubmdz: ok, deferred, let's chat about it in #u-d after the meeting12:02
mdzdaniels: not gui installer; unified hardware detection12:02
mdzdaniels: and to answer your question, because of the X component12:02
Kamionmdz: I don't think the mac-io hotplug stuff is urgent, personally, the /etc/modules workaround is adequate12:02
Kamionand the existing code is easy to deal with12:02
fabbionedaniels: because you own X and it is related to GUY?12:03
mdzdaniels: we'll need your help to get the X autodetection doing the right stuff on the live CD, I assume12:03
amumdz: ack12:03
mdzKamion: ok.  if you get an itch to try it out, please send feedback to the guy who sent it to me; he's very interested in whether it works out12:03
fabbionemdz: Mark explicitly requested that...12:03
mdzfabbione: requested what?12:03
danielsmdz: oh, UHD; sorry, ECONTEXT12:03
mdzone short item, since the live CD came up12:04
fabbionemdz: the sync between X install autodetection and liveCD12:04
mdzwe're going to be developing some significant bits of infrastructure for the live CD12:04
mdzenough that it needs a name12:04
Kamionlive-* not enough?12:04
mdzlike, a brand name12:04
mdza name for the project12:04
KeybukUbuntu LIVE!12:04
mdzit should not be specific to Ubuntu12:05
lamont_rfrankenbuntu?12:05
ogralol12:05
sivangliveshow? 12:05
fabbioneUbuntu-resurrected?12:05
Kamionlively12:05
lamont_r(it's alive....)12:05
sivang:)12:05
sivangor LiveShow12:05
danielsyeah, X install detection and live CD sync is kind of tricky12:05
mdzlively is cute12:05
smurfixlively lizard?12:05
jdubLively Leprechaun12:05
=== Kamion steals jdub's pot of gold.
mdzok, thanks for the suggestions12:06
danielsbut I have a design for it and will move forward after I've fixed my most pressing bugs (xorg module loader plus debian sync, l-r-m 2.6.10, preparing for new fglrx)12:06
mdzmoving ahead with feature goals12:06
mdzpitti: what's the status of language packs?12:06
KeybukKamion: mind out, floor's a bit slippy12:06
pittimdz: carlos will implement time-based po downloads (in a ZIP stream) soon12:07
pittimdz: I agreed with him on an interface today12:07
pittimdz: I still need to setup the automatic deb building12:07
mdzpitti: so the glibc changes are in (yes?), the striptranslations tool is written(?)12:07
pittimdz: and I need to complete the metapackages (but that's relatively easy)12:07
pittimdz: yes and yes12:07
pittimdz: pkgstriptranslations12:08
pittimdz: I also updated debhelper to use it if it's present12:08
mdzpitti: we need to tie the strip process into the autobuilders, and create a tool to build packages from the stripped translations12:08
pittimdz: it just needs to be enabled in /etc/pkgstriptranslations.conf12:08
mdzpitti: oh, so we should be ready to start stripping translations during the build?12:08
pittimdz: yes12:08
mdzpitti: please work with lamont to get that going ASAP12:08
pittimdz: everything is in place12:08
lamont_rcool.. pitti I just need instructions12:08
pittimdz: I did not yet ask for that because we don't yet have lang pack debs12:09
=== fabbione does too
mdzlamont: will need one additional package installed in the chroots, and then a mechanism to copy the files off somewhere after the build is complete12:09
pittilamont_r: just enable pkgstriptranslations in the conffile12:09
mdzpitti: we should start collecting translations now, so that we have something to make debs from12:09
pittilamont_r: and pkgstriptranslations (the deb) must be included into the buidd chroots12:09
lamont_rinstalled and configured.12:09
mdzlamont_r, pitti: we can discuss the details after the meeting, but please get it going soon12:09
pittimdz: no, we don't need to copy the mo files12:09
mdzpitti: we don't?12:09
pittimdz: no, carlos said that the mo files are useless12:10
lamont_rwhat happens to the stripped transalations?12:10
pittimdz: that's why I just delete them12:10
fabbione>/dev/null ?12:10
pittimdz: carlos said that rosetta needs the original po files12:10
mdzpitti: if we throw them away, then we can't create language packs until every package is in Rosetta12:10
pittimdz: so rosetta needs to extract them from the source package12:10
mdzand there are only, what, about 10 packages in rosetta so far?12:10
lamont_rpitti: I'll get with you after the meeting12:10
pittimdz: AFAIUI they can do it automatically now12:10
mdzyes, let's take that discussion elsewhere12:10
pittimdz: but I have to ask carlos again12:11
pittiyes12:11
pittimdz: I will care for that in the next days12:11
mdzdoko: python-minimal seems to be in fairly good shape12:11
mdzdoko: what remains to be done before we make it Essential: yes?12:11
dokotighten the dependency, should be all.12:11
mdzdoes anyone else have outstanding concerns about python-minimal?12:12
mdzwe should probably have some sort of test suite12:12
Kamionseems to debootstrap properly now12:12

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