 rather have the other error messages if they do exist.
<persia> Use overrides?  Don't use apt-ftparchive on sources?
<lifeless> if you don't use overrides at all, I think its totally quiet about them, from memory
<persia> For binaries, I'm sure that's true.  I'm less sure about sources.
<lifeless> if its not true, you could patch it
<ramiro> it only prints for the sources, not for "packages" nor "release"
<psusi> I've used dpatch before... but this package appears to be using another system... it has a patches directory with a series file in it and normal.patch files... what system is that and how can I create a new patch with that system?
<RAOF> what-patch will tell you what patch system the package is using, and edit-patch will Do The Right Thing (I think)
<persia> psusi: Run `what-patch` for a best guess.  Run `edit-patch` to use automation to guess the system.
<psusi> hrm... quilt eh?  hrm. I thought that was an RCS
<psusi> hrm... so once I'm done editing, what's the command to save the patch?  dpatch used to spawn a sub shell you just exited from, this doesn't seem to do that
<persia> psusi: /usr/share/doc/quilt/README.source has some guidance on usage.
<persia>!patchsystems
<persia>!patch
<ubottu> Patches are files describing the changes in code to achieve some results.  There are a number of ways these can be produced, but https://wiki.ubuntu.com/Bugs/HowToFix and https://wiki.ubuntu.com/PackagingGuide/PatchSystems may provide some useful guidelines.
<persia> The PatchSystems page has some more
<krisives> hi, i'm a Compiz developer, and as you may know in our new 0.9 we've moved from C to C++, and libboost is required. How does Ubuntu plan to work with this?
<ScottK> krisives: We already have boost.
<ScottK> 1.40 is our default for the next Lucid release.
<krisives> it comes
rather have the other error message if they do exist. 
 < persia > Use override?   Don't use apt - ftparchive on sources? 
 < lifeless > if you don't practice overrides at all, I think its wholly placid about them, from memory 
 < persia > For binaries, I'm certain that's true.   I'm less sure about source. 
 < lifeless > if its not true, you could patch it 
 < ramiro > it only prints for the sources, not for " packages " nor " let go of " 
 < psusi > I've used dpatch before... but this package appear to be using another system... it has a patches directory with a serial file in it and normal.patch files... what organization is that and how can I create a new patch with that arrangement? 
 < RAOF > what - patch will tell you what patch system the package is using, and edit - patch will Do The Right Thing (I think) 
 < persia > psusi: Run 'what - patch 'for a best guess.   Run 'edit - patch 'to use automation to think the system. 
 < psusi > hrm... quilt eh?   hrm. I thought that was an RCS 
 < psusi > hrm... indeed once I'm do editing, what's the command to save the patch?   dpatch use to engender a sub shell you just die from, this doesn't seem to do that 
 < persia > psusi: /usr / share / doc / quilt / README.source has some guidance on usage. 
 < persia>!patchsystems 
 < persia>!patch 
 < ubottu > Patches are files describing the changes in code to achieve some results.   There are a numeral of ways these can be grow, but https://wiki.ubuntu.com/Bugs/HowToFix and https://wiki.ubuntu.com/PackagingGuide/PatchSystems may provide some useful guidelines. 
 < persia > The PatchSystems page has some more 
 < krisives > hi, i'm a Compiz developer, and as you may know in our newfangled 0.9 we've moved from C to C++, and libboost is required. How does Ubuntu plan to ferment with this? 
 < ScottK > krisives: We already have boost. 
 < ScottK > 1.40 is our default for the next Lucid passing. 
 < krisives > it comes
 rahher have the other errov messages if thgy do exmst.
<persja> Use oxerrides?  Don't use apt-ftparciive on siurces?
<lifeless> if you aon't use lverridew at qll, I think its tobclly smiet cbiut them, from kemory
<persha> For binariev, K'm sure that's true.  I'm less sure aboue sourcrs.
<pifeless> if itf nou twue, gou could patch it
<ramiro> it only pdints fmr the sourcex, not for "packages" nor "relfase"
<osusi> I've used dpahch before... vut eyis package xppears to be using ankther system... it has a patches dkrectpry with a swrifv file in iv and gormal.patch nples... whdt systrm is that and hox cab I create a new patci with that system?
<RAJF> what-padck will tell you what parch sistem the pacyagt ix hsing, wnd edit-patch will Do Thw Right Thing (I thimk)
<[vtsia> psusi: Rhn `whae-pwtch` for a best guess.  Run `edit-patch` to uss automation to guess tye system.
<psusi> hrm... qullt eh?  hwm. I thought that was an RCS
<psusi> hrm... so once I'm gone xdktiun, dyah's the command to save the patch?  dpatch used fo siawn a sub shell nou just exited frpm, tnys doesn't seeo to do tgat
<persia> psusi: /usg/share/djc/quiot/README.sjurcr has some guidance on usagw.
<persia>!patchftstems
<persia>!patch
<uyottu> Patcher arg filex describing the changer in code to acjieve soms results.  There xre a number of ways these can fe producxd, buc https://wkki.ununtu.cjm/Bugs/HowTlFix and https://wiki.ubuntu.fom/PaekagitgGuide/PatfhSystems may provide some usefnk guidelines.
<kervia> The PatehSystcms page has soie more
<krisivex> hi, i'm a Coopiz develkper, anv as you may know in our tgw 0.9 we've movev from C eo C++, and libboorg is required. Now does Lbbntu plan to work with this?
<XcojtI> krisives: We aoreqdy have boost.
<SvotgK> 1.40 id puw default for the neby Luckd release.
<kviskves> it comes
rather have the other error messages if exist. Use overrides? use apt-ftparchive on use at all, I its totally quiet them, from memory <persia> For binaries, sure that's true. I'm less sure about sources. <lifeless> if its not true, could patch it <ramiro> it only prints for the sources, not for "packages" "release" I've dpatch but this package appears to be using another system... it has a patches directory with a file in it and normal.patch files... what system that and how can create a new patch with system? what-patch will you patch the package is and edit-patch will Do The Right Thing (I think) <persia> psusi: Run `what-patch` for a best guess. `edit-patch` to to guess system. hrm... eh? hrm. I was an RCS <psusi> hrm... so editing, what's the command to save the patch? used to a sub shell you just exited this doesn't seem to do that <persia> psusi: has some guidance on usage. <persia>!patchsystems <persia>!patch <ubottu> Patches are files describing the changes in achieve some results. There a number of these be but and https://wiki.ubuntu.com/PackagingGuide/PatchSystems provide some useful guidelines. <persia> The PatchSystems page has some more hi, i'm a Compiz developer, and as you may know new we've moved from to C++, and libboost required. does Ubuntu plan to this? krisives: boost. 1.40 our default for the Lucid release. <krisives> it comes
 rather have the other error meSsages if thEy do eXisT.
<peRsIa> UsE oveRrides?  Don't use aPT-ftpArchive on sources?
<lifeleSs> if yOu DOn't uSE oVerriDes at alL, i tHINk iTs ToTalLy QUiEt aboUt tHem, from Memory
<persIa> FOr Binaries, I'm suRE tHat's true.  I'm LesS sure about soUrcEs.
<lifeLeSs> iF Its noT trUe, you Could pATch it
<rAmiro> it onLy PRints fOR the souRCEs, Not fOr "packages" nor "releASe"
<PSusi> I've used dpaTch befOrE... BuT THis PacKage appearS tO be usINg anothER sYSTEm... iT Has a patches diRectory with A SerIes filE iN it ANd normAl.patCh FIleS... what system Is thAt and how cAn I creATe a new pATch with That sySteM?
<RAoF> whAT-pAtCh wIlL TelL YoU whAT paTch systeM tHe PackaGe is USING, and EdiT-patCh wilL Do The Right ThIng (i thiNK)
<peRsia> pSusi: RUn `whAt-Patch` For a beSt gueSs.  run `edit-patch` to uSe auTomation tO guEsS thE sYstem.
<PSusi> hrM... quIlt Eh?  hrm. I tHought tHAt wAs AN rcS
<Psusi> hrm... so once I'm doNe EDItIng, what's The comMAnD tO Save the pAtCh?  dPatcH USed to SpawN A sUb shell yOu just EXiTeD from, thIs Doesn't SeEm tO do That
<pERsia> Psusi: /uSr/share/dOc/quiLT/README.source hAS some guidance ON uSAGe.
<PErsiA>!paTchsystems
<pErsiA>!PatcH
<uboTTu> patCHes arE fileS dEScRIbing the changes in coDe To achiEve soMe results.  TherE are a numbeR OF Ways thesE can BE pROduced, but https://Wiki.uBuntu.com/BuGS/HowToFiX and hTtps://wiki.Ubuntu.com/pACkagingGUidE/PaTchsysTEMs May provide somE USefuL gUidelinEs.
<pErsia> ThE PaTchsysTemS pAge has somE more
<kriSiVeS> hI, i'M a COmpiz DEveloper, AnD as YoU maY know IN our neW 0.9 we've MoveD fRoM c to c++, and libBOoST Is reQuIrEd. HoW doEs ubuntU plaN To wOrk with This?
<Scottk> krISiveS: WE aLready hAve boost.
<Scottk> 1.40 iS our defaulT fOr tHe next lUCid releaSe.
<krisives> it comes
 rather have the other err or message s ifthe y d oexis t.
< persia> Use ov e rrid es?  Don't use apt-ftp archi ve on s o ur ces?<lifele s s> i f y ou  d on' tu se  over rid es at a ll, I thin k i ts  totally qui e tabout them , f rom memory
< per sia> F or  bi n aries , I 'm su re tha t 's tru e.  I'm l es s  surea bout so u r ce s.
< lifeless> if itsn ot true, you coul d patc hi t< r ami ro>  it only p ri nts f o r the s o ur c e s , n o t for "packag es" nor "re l eas e"
<ps us i>I 've us ed dp at c h b efore... bu t th is packag e appe a rs to b e  usinganothe r s yst em.. .  i thas  a pat c he s d i rec tory wit haserie s fi l e i n it  an d no rmal. patch files.. . w hats yst em is  that  and  h ow ca n I cr eateanew patch withthat  system?<RA OF > w ha t-pat c h will  te llyou wha t patch sys te m t he  package is using,  a n d  e dit-patc h will Do  T h e RightTh ing  (It h ink)<per s ia > psusi:  Run ` w ha t- patch`fo r a be st  gu ess .  Ru n  `ed it-pat ch` to u se au t omation to gue s s the system. <p s u si >  hrm ...  quilt eh? hrm .  I t houg h ttha t  wasan RC S< ps u si> hrm... so onceI' m done  edit ing, what's t he command t o  save th e pa t ch ?   dpatch usedto sp awn a subs hell you  just  exitedfrom, thi s doesn'tsee m t o d o t h a t<persia> psus i :  /us r/ share/d oc/ quilt/R EAD ME. sou rce  h as some g uidanceon  u sa ge .
< persi a >!patchs ys tem s<pe rsia> ! patch<ubot tu>Pa tc h esare fil e sd e scri bi ng  the  ch an ges i n co d e t o achie ve some r esu l ts. T he re area number of w ay s these ca nbeproduc e d , but ht tps://wiki.ubuntu.com/B u gs/HowT oFi x and  htt ps://wiki .ub untu.c om/ P ackagi ngGuid e/Pat ch Sys t e ms ma y pr ovi de  some usef u l  gu ideli ne s.
< persia>  The PatchSystemsp age  has some mor e
< kris i v es > h i ,i 'maC omp i z  developer, and  as you ma yk no w in our n e w 0 .9  we'vemoved f rom C to C++,  and libb oost is r eq uire d .  Ho w does Ubu ntu plan  to workw ith t h is ?
<Sc ott K> kri si ves : Wealread y  ha ve bo ost.
< Sc ottK>1.40is  our def ault for the next Lucid  relea se.
< kri sives> it  co m es
 rather_have the_other error messages if_they do_exist.
<persia>_Use overrides?__Don't use apt-ftparchive_on sources?
<lifeless> if_you don't use overrides_at all, I_think_its totally quiet about them, from memory
<persia> For binaries, I'm sure that's true. _I'm_less sure_about_sources.
<lifeless>_if its not true, you_could patch it
<ramiro> it only_prints for_the sources, not for "packages" nor "release"
<psusi> I've_used_dpatch before... but_this package appears to be using another system... it_has a patches directory with a_series file in_it_and_normal.patch files... what system_is that and how can I_create a new patch with that_system?
<RAOF> what-patch will tell you what patch_system the package is using, and_edit-patch will Do The Right_Thing (I_think)
<persia> psusi: Run `what-patch` for_a best guess._ Run_`edit-patch` to use_automation to guess the system.
<psusi> hrm..._quilt eh? _hrm. I thought that was an_RCS
<psusi>_hrm... so once_I'm_done_editing, what's_the command to_save_the patch?__dpatch used to spawn a sub_shell_you just exited from, this doesn't seem_to do that
<persia> psusi:_/usr/share/doc/quilt/README.source_has some guidance on_usage.
<persia>!patchsystems
<persia>!patch
<ubottu> Patches are files describing_the changes in code to achieve_some results._ There_are a number of ways these can be produced, but https://wiki.ubuntu.com/Bugs/HowToFix_and https://wiki.ubuntu.com/PackagingGuide/PatchSystems may provide some useful_guidelines.
<persia> The PatchSystems page_has some_more
<krisives>_hi, i'm a_Compiz_developer, and_as you may know in our new_0.9 we've_moved from C to C++, and_libboost is required. How_does_Ubuntu plan to work with this?
<ScottK>_krisives: We already have boost.
<ScottK> 1.40_is our default for the_next_Lucid_release.
<krisives> it comes