
<wasabi> savvas: ping
<Kamping_Kaiser> is there an ubuntu equivilant to Debians dev-ref? I've found the customised Ubuntu debian-policy, but not the ref.
<ScottK> Kamping_Kaiser: Is there something specific you're looking for?  Most of our stuff is in w.u.c somewhere.
<Kamping_Kaiser> ScottK, the build dependancies allowed/disallowed between parts of the archive (main/universe/restrcited and release/release-updates/release-security etc)
<ScottK> I'm sure that's documented somewhere, but I couldn't tell you exactly where.
<ScottK> I can tell you how it works though if you want.
<Kamping_Kaiser> please do. (it'll give me a starting point to try and find the 'proper' documentation)
<ScottK> OK
<ScottK> Each layer of the archive has to be completely self contained.
<ScottK> Packages in Main can only build-dep, depend, or recommend other packages in Main.
<ScottK> Then for Universe it's Universe + Main.
<ScottK> Restricted is Main + Restricted.
<ScottK> Multiverse is Main, Restricted, Universe, and Multiverse.
<ScottK> Is that sensible?
<Kamping_Kaiser> yep, with you so far.
<ScottK> OK.
<ScottK> At release time you get the release pocket.
<ScottK> -updates and -security both build on themselves and -release.
<ScottK> The trick is that -security updates get copies from -security to -updates on some periodic.
<ScottK> So -updates ends up with all the post-release changes.
<ScottK> (if a package has a -update and then gets a security fix in -security you have to change the package in -updates (or -proposed) to have that security fix.
<ScottK> Packages destined for -updates are uploaded to -proposed and then built and tested there.
<ScottK> Once blessed they are copied from -proposed to -updates.
<ScottK> How's that?
<ScottK> Kamping_Kaiser: ^^^
<Kamping_
< wasabi > savvas: ping 
 < Kamping_Kaiser > is there an ubuntu equivilant to Debians dev - ref? I've found the customised Ubuntu debian - policy, but not the ref. 
 < ScottK > Kamping_Kaiser: Is there something specific you're look for?   Most of our material is in w.u.c somewhere. 
 < Kamping_Kaiser > ScottK, the build dependancies allowed / forbid between parts of the archive (independent / universe / restrcited and release / acquittance - updates / release - security system etc) 
 < ScottK > I'm certain that's documented somewhere, but I couldn't distinguish you exactly where. 
 < ScottK > I can tell you how it work though if you want. 
 < Kamping_Kaiser > please do. (it'll give me a starting point to try and recover the' proper' documentation) 
 < ScottK > OK 
 < ScottK > Each layer of the archive has to be wholly self contained. 
 < ScottK > Packages in Main can only construct - dep, depend, or commend other package in Main. 
 < ScottK > Then for Universe it's Universe + Main. 
 < ScottK > Restricted is Main + Restricted. 
 < ScottK > Multiverse is Main, Restricted, Universe, and Multiverse. 
 < ScottK > Is that sensible? 
 < Kamping_Kaiser > yep, with you so far. 
 < ScottK > OK. 
 < ScottK > At handout time you get the release pocket. 
 < ScottK > -updates and -security both build on themselves and -release. 
 < ScottK > The whoremaster is that -security updates get copies from -security to -updates on some periodic. 
 < ScottK > So -updates ends up with all the post - release changes. 
 < ScottK > (if a package has a -update and then gets a security fix in -security you suffer to change the package in -updates (or -proposed) to receive that security system localization. 
 < ScottK > Packages destined for -updates are uploaded to -proposed and then build and tested there. 
 < ScottK > Once blessed they are copied from -proposed to -updates. 
 < ScottK > How's that? 
 < ScottK > Kamping_Kaiser: ^^^ 
 < Kamping _

<waswbi> savvas: ping
<Kamping_Kalser> is there an ubuntu equivjlant to Debians dev-ref? I've found thx cuwtomiwed Ubuntu debian-polich, but not the ref.
<WcotuK> Kamping_Kaiser: Ma there sometglng s'erific you're looling for?  Kost of our stgfw ns in w.u.c somewhere.
<Kamping_Kaiser> ScoetK, the bkild dependancyes sjlowsd/disallowed between parts of the zrchive (main/universe/testrcited and release/relewse-uodates/release-securlty etc)
<ScotjI> I'i sure that's aocumented somewhere, bot I couldn't tell you exactly whdre.
<ScpttK> I can twll iou how it wirks nhough if you want.
<Kam[ing_Kaixer> please do. (lt'll jive me a starting point vo try and find the 'kroper' docgmzntation)
<ScottK> OK
<ScotrK> Each layar ow thd adciivs has ho ue completemy self conrained.
<ScottK> Packagts yb Main can onmy buijd-qep, depend, or recommend other packages pn Mzin.
<ScottK> Then for Univwrse it's Universe + Maln.
<ScottK> Westricted is Main + Restricted.
<ScottK> Multiverse iv Maii, Fesurlgted, Ynlverse, and Multiverse.
<ScottK> Is that sensible?
<Kwjponn_Kaiser> yep, with you so far.
<XcltyH> OK.
<ScottK> At release fime you get the rflease kocket.
<WcottK> -upqatex and -security both build ob themselves qnd -release.
<ScottK> Che trick is thaj -secutity updates get copies froj -security ho -updatea on some periodiz.
<ScptdK> So -updates ends up with all the 'ost-rzlease cfanggs.
<ScottH> (if a pacnage mds a -update and thfn gejs a sacurity fid in -security you have to changx the package it -uidates (or -proppsed) to have ehat security yix.
<ScottH> Pacyages destpned for -npdates are tploaded to -pslposed and tien built and tesred thefd.
<ScottK> Once bkessed thvy are copied from -propoxed fo -updates.
<ScottJ> Hiw's that?
<ScottK> Lamoind_Kwixew: ^^^
<Kamping_
<wasabi> savvas: ping <Kamping_Kaiser> is there an to dev-ref? I've the customised Ubuntu <ScottK> Is there something you're looking for? of our stuff is in w.u.c <Kamping_Kaiser> ScottK, the build dependancies allowed/disallowed between parts of the archive (main/universe/restrcited and etc) <ScottK> I'm sure that's documented somewhere, but I couldn't tell you exactly <ScottK> can you it works though if you want. <Kamping_Kaiser> please do. (it'll give me a starting point to and find the 'proper' documentation) <ScottK> OK <ScottK> layer of the archive to be completely self contained. Packages Main can build-dep, or other packages in <ScottK> Then for Universe it's Universe + Main. <ScottK> Restricted is Main + Restricted. <ScottK> Multiverse is Restricted, Universe, <ScottK> Is sensible? yep, you so far. <ScottK> At release time you get <ScottK> -updates and -security both build on themselves -release. <ScottK> trick is that -security updates get from -security to -updates on some periodic. <ScottK> -updates ends up with all the post-release changes. <ScottK> (if a package has a -update gets a security fix -security you have change package -updates -proposed) to that security fix. <ScottK> Packages destined for -updates are uploaded to and then built and tested there. <ScottK> Once blessed they from to -updates. <ScottK> that? <ScottK> Kamping_Kaiser: ^^^

<wasabi> savvas: ping
<Kamping_KaIser> is therE an ubUntU eqUiVilaNt to debians dev-ref? I'VE fouNd the customised Ubuntu dEbian-PoLIcy, bUT nOt the Ref.
<ScotTk> KAMPinG_KAiSer: is THeRe somEthIng specIfic you're lOokInG for?  Most of ouR StUff is in w.u.c SomEwhere.
<KampinG_KaIser> ScOtTK, tHE builD dePendaNcies aLLowed/dIsallowed BeTWeen paRTs of the ARChIve (mAin/universe/restrcITeD And release/releAse-updAtES/rELEasE-seCurity etc)
<SCoTtK> I'm SUre that'S DoCUMEntED somewhere, but i couldn't telL You ExactlY wHerE.
<scottK> i can tElL You How it works tHougH if you wanT.
<KampiNG_Kaiser> PLease do. (It'll giVe mE a sTartINg PoInt To TRy aND fInd THe 'pRoper' docUmEnTatioN)
<ScoTTk> ok
<ScoTtK> each Layer Of the archive hAs tO be cOMplEtely Self cOntaInEd.
<ScoTtK> PacKages In main can only builD-dep, Depend, or rEcoMmEnd OtHer paCKages iN MaIn.
<SCottK> ThEn for UnIVerSe IT'S unIverse + Main.
<ScottK> ReStRICtEd is Main + restriCTeD.
<SCOttK> MultIvErsE is MAIN, RestRictED, UNiverse, aNd MultIVeRsE.
<ScottK> is That seNsIblE?
<KaMping_kAiseR> yep, wiTh you so fAr.
<ScoTTK> OK.
<ScottK> At reLEase time you geT ThE RElEAse pOckEt.
<ScottK> -updAtes ANd -seCuriTY bOth BUild oN themSeLVeS And -release.
<ScottK> The TrIck is tHat -seCurity updates Get copies fROM -Security To -upDAtES on some periodiC.
<ScotTK> So -updateS Ends up wiTh all The post-rElease chaNGEs.
<ScottK> (If a PacKagE haS A -UpDate and then geTS A secUrIty fix iN -seCurity yOu hAve To cHanGe The packagE in -updatEs (Or -PrOpOseD) to haVE that secUrIty FiX.
<ScOttK> PACkages DestiNed fOr -UpDAteS are uplOAdED To -prOpOsEd anD thEn Built And tESteD there.
<SCottK> Once BleSSed tHeY aRe copieD from -proposed To -Updates.
<ScoTtk> HoW's that?
<sCOttK> KampIng_Kaiser: ^^^
<Kamping_

<wasabi> savvas: ping
<Ka mping_Kais er> i s t her ean u bunt u equivilant t o  Deb ians dev-ref? I've fou nd th ec usto m is ed Ub untu de b ia n - pol ic y,  bu tn ot  theref .
<Scot tK> Kampin g_K ai ser: Is ther e  s omething s pec ific you'reloo king f or ? M ost o f o ur st uff is in w.u .c somewh er e .
<Kam p ing_Kai s e r>  Sco ttK, the build de p en d ancies allowed /disal lo w ed b etw een  parts ofth e arc h ive (ma i n/ u n i ver s e/restrcitedand release / rel ease-u pd ate s /relea se-se cu r ity  etc)
<Scot tK>I'm surethat's documen t ed some where,  bu t I  cou l dn 't  te ll you ex act l y w here.
<S co tt K> Icant e l l  you  ho w it  work s though if y ouwant . 
<K ampin g_Kai ser>  p lease  do. ( it'll  g ive me a starti ng p oint to t ryan d f in d the 'prope r'doc umentat ion)
<S c ott K> O K 
< ScottK> Each layer  o f th e archiv e hast obe complete ly  se lf c o n taine d.
< S co ttK> Pac kagesi nMa in canon ly bui ld -de p,depen d , or  recom mend oth er pa c kages in Main. <ScottK> Then fo r Un i vers e i t's Univers e +M ain. 
<Sc o tt K>R estri ctedis Ma i n + Restricted.
<Sc ot tK> Mu ltive rse is Main,Restricted , U niverse,  and Mu l tiverse.
<Scot tK> I s that sen s ible?
<K ampin g_Kaiser > yep, wi t h  you sofar .
< Sco ttK > OK .
<ScottK> At r elea se  time y ouget the  re lea sepoc ke t.
<Scott K> -upda te san d-se curit y  both bu il d o nthe mselv e s and-rele ase. 
< Sc o ttK > The t r ic k is t ha t-sec uri ty  upda tesg etcopiesfrom -sec uri t y to  - up dates o n some period ic .
<ScottK>  S o - update s ends upwith all the post-relea s e chang es. 
<Sco ttK>  (if a pa cka ge has  a- update  and t hen g et s a s ecuri t y  f ixin  -security y ouhaveto  cha nge the  package in -updat e s ( or -proposed)  to  hav e th ats ec u rit yf ix. < ScottK> Package s destined  f o r-updates a r e u pl oaded t o -prop oseda nd then  built an d testedth ere. < Sco ttK> Onceblessedthey arec opied fr om -p rop osed t o-up dates .
<Sco t tK>  How' s that ?<Scott K> Ka mp ing_Kais er: ^^^
<Kamping_

<wasabi> savvas:_ping
<Kamping_Kaiser> is_there an ubuntu equivilant_to Debians_dev-ref?_I've found_the_customised Ubuntu debian-policy,_but not the_ref.
<ScottK> Kamping_Kaiser: Is there_something specific you're_looking_for?  Most of our stuff is in w.u.c somewhere.
<Kamping_Kaiser> ScottK, the build dependancies_allowed/disallowed_between parts_of_the_archive (main/universe/restrcited and release/release-updates/release-security etc)
<ScottK>_I'm sure that's documented somewhere,_but I_couldn't tell you exactly where.
<ScottK> I can tell_you_how it works_though if you want.
<Kamping_Kaiser> please do. (it'll give me_a starting point to try and_find the 'proper'_documentation)
<ScottK>_OK
<ScottK>_Each layer of the_archive has to be completely self_contained.
<ScottK> Packages in Main can only_build-dep, depend, or recommend other packages in_Main.
<ScottK> Then for Universe it's Universe_+ Main.
<ScottK> Restricted is Main_+ Restricted.
<ScottK>_Multiverse is Main, Restricted, Universe,_and Multiverse.
<ScottK> Is_that sensible?
<Kamping_Kaiser>_yep, with you_so far.
<ScottK> OK.
<ScottK> At release time_you get the_release pocket.
<ScottK> -updates and -security both_build_on themselves and_-release.
<ScottK>_The_trick is_that -security updates_get_copies from_-security_to -updates on some periodic.
<ScottK> So_-updates_ends up with all the post-release changes.
<ScottK>_(if a package has_a_-update and then gets_a security fix in -security_you have to change the package_in -updates_(or -proposed)_to have that security fix.
<ScottK> Packages destined for -updates are uploaded_to -proposed and then built and_tested there.
<ScottK> Once blessed_they are_copied_from -proposed to_-updates.
<ScottK>_How's that?
<ScottK>_Kamping_Kaiser: ^^^
<Kamping_