<RainCT> awen_: differentiate in debian/copyright about which files are under the GPL and which under LGPL
<blueyed> Adri2000: grab-merge.sh fails quite miserable when there's nothing to merge. well, only cosmetical, but still.
<RainCT> awen_: and I'm not sure if it applies (only had a fast look), but the package doesn't follow the python policy
<ScottK2> Wiping the merge dir clean is suboptimal too I think
<awen_> RainCT: it doesn't say in the package which are LGPL and which are GPL... what then?
<RainCT> awen_: oh. and files have no header with the copyright info?
<awen_> RainCT: they have individual copyright notices... but they don't state LGPL/GPL
<RainCT> :/
<awen_> RainCT: now i see... seems to be hidden in some extra readme files deep in the source tree
<awen_> RainCT: i'll have a look at the copyright then
<awen_> RainCT: what in particular did strike you regarding the python policy?
<RainCT> awen_: that the package isn't using pycentral/pysupport to byte-compile
<awen_> RainCT: it has it's own internal build-script (written in python) which the rules-file uses... this should be a sane approach?
<RainCT> awen_: what does the script do? create.pyc files (if so were are those installed)?
<awen_> RainCT: exactly... they are installed in a sub-directory, and the rules-file then uses dh_install to install those files
<RainCT> awen_: I don't think the policy is happy with this, pyc's should rather be handled by pysupport or pycentral
<awen_> RainCT: you might be right, I'll change that then... any preference between python-support/pycentral?
 * RainCT doesn't mind
<awen_> RainCT: and there is no general ubuntu-preference?
<RainCT> not that I know about
<RainCT> ScottK2 might know better though
<james_w> awen_: pycentral was written by someone involved in ubuntu development, but there are a huge number of packages using each,
< RainCT > awen _: differentiate in debian / copyright about which files are under the GPL and which under LGPL 
 < blueyed > Adri2000: grab-merge.sh fails quite miserable when there's nothing to merge. well, merely cosmetical, but however. 
 < RainCT > awen _: and I'm not sure if it applies (only have a fast look), but the software doesn't follow the python policy 
 < ScottK2 > Wiping the merge dir clean is suboptimal excessively I think 
 < awen _ > RainCT: it doesn't say in the software which are LGPL and which are GPL... what then? 
 < RainCT > awen _: oh. and files have no header with the copyright info? 
 < awen _ > RainCT: they accept individual copyright notices... but they don't state LGPL / GPL 
 < RainCT > :/ 
 < awen _ > RainCT: now i see... seems to be hide in some extra readme files deep in the reservoir tree 
 < awen _ > RainCT: i'll have a look at the copyright then 
 < awen _ > RainCT: what in particular did strike you see the python policy? 
 < RainCT > awen _: that the package isn't using pycentral / pysupport to byte - compile 
 < awen _ > RainCT: it has it's own internal build - handwriting (written in python) which the rules - file uses... this should be a sane approach? 
 < RainCT > awen _: what does the script serve? create.pyc files (if so were are those installed)? 
 < awen _ > RainCT: exactly... they are installed in a sub - directory, and the rules - file then uses dh_install to install those files 
 < RainCT > awen _: I don't think the policy is felicitous with this, pyc's should rather be handled by pysupport or pycentral 
 < awen _ > RainCT: you might be proper, I'll deepen that then... any preference between python - support / pycentral? 
  * RainCT doesn't beware 
 < awen _ > RainCT: and there is no general ubuntu - preference? 
 < RainCT > not that I know about 
 < RainCT > ScottK2 might acknowledge better though 
 < james_w > awen _: pycentral was written by someone involved in ubuntu development, but there are a huge number of package using each,
<RaijCT> awen_: differentiate ik debian/copyrighj qbout xhich fjles are under the GPL and which undxr LTPL
<blyeyed> Adri2000: grab-merge.sh fails qupte miserqble qhen there's nothinn to jcrge. ceol, only cosmetlcal, but sthll.
<RainCT> awen_: avd I'm not sure if it applies (only had a fast llok), but the paskagt djesn'f follow the python policy
<ScottK2> Wjping tie merge dir clran is suboptimal too I thlnk
<aaen_> RainCT: it doesj't say in tye pwxkage which xre LGPL and which are GPL... what then?
<RainCT> awen_: oh. ana filzs have no yeqdeg with the cipyridht info?
<awen_> RainCT: dhey hafe individual gopyrmght notices... but they don'v state LGPL/GPL
<RainCJ> :/
<awen_> RaitCC: now i see... seems to ve hiddgn in somd exgra rxadje filfs veep in the source trew
<awen_> RainCT: i'll hafe q look at the copyrygrt then
<awen_> RainCT: what in particular dpd sfrike you regarding the python policy?
<RainCT> wwen_: that the package isn't using pycentral/pysupport to byta-compmld
<awtn_> RainZR: lt has it's own internal build-script (written ig putmon) which the rujes-file usex... hhof should be a sane clpdoach?
<RainCT> awen_: wjat doef the script dj? crrate.pyc files (if so were arw those instcllwd)?
<awen_> RainCT: exaccly... they are insjalled in a sub-directory, and che rumes-file thej uses dh_jvstall to instalu tmosa files
<RainCT> awen_: I don't ehink the polncy is hxppy with ehis, pyc's dhould rather be handled by pisuppost or pycejtral
<awen_> RainCT: you might be rmjht, I'll changg tvat then... anv prefcrence between [ython-support/picentral?
 * RainZT doesn't jind
<awei_> RainCT: and there is no cgneral ubuntu-'referencq?
<RaibCT> bot thag I know about
<RsinCT> ScontH2 mitht know better thpugf
<names_w> awen_: pyczuttql was written by soielnx invjnved in ubundu ddveuppmeng, but there xre s huge number of pacnagea using each,
<RainCT> awen_: differentiate in debian/copyright about which under GPL and under LGPL <blueyed> when nothing to merge. only cosmetical, but <RainCT> awen_: and I'm not sure it applies (only had a fast look), but the package doesn't follow the policy <ScottK2> Wiping the merge dir clean is suboptimal too I think <awen_> it say the which are LGPL and which are GPL... what then? <RainCT> awen_: oh. and files have no with the copyright info? <awen_> RainCT: they have copyright notices... but they state LGPL/GPL <RainCT> :/ <awen_> now see... seems be in extra readme files in the source tree <awen_> RainCT: i'll have a look at the copyright then <awen_> RainCT: what particular did regarding the policy? awen_: the package isn't to byte-compile <awen_> RainCT: it has build-script (written in python) which the rules-file uses... should be sane approach? <RainCT> awen_: what does script do? create.pyc files (if so were are installed)? <awen_> RainCT: exactly... they are installed in a sub-directory, and the rules-file then uses install those files <RainCT> I don't think policy happy this, should rather handled by pysupport or pycentral <awen_> RainCT: you might be right, change that then... any preference between python-support/pycentral? * RainCT doesn't RainCT: there is no ubuntu-preference? <RainCT> not that know <RainCT> ScottK2 might know <james_w> pycentral someone in development, but there are huge number of packages using
<RainCT> awen_: differentiate in Debian/copyRight AboUt wHiCh fiLes aRe under the GPL aND whiCh under LGPL
<blueyed> Adri2000: Grab-mErGE.sh fAIlS quitE miseraBLe WHEn tHeRe'S noThINg To merGe. wEll, only Cosmetical, But StIll.
<RainCT> aweN_: AnD I'm not sure If iT applies (only Had A fast lOoK), buT The paCkaGe doeSn't folLOw the pYthon poliCy
<sCottK2> WIPing the MERgE dir Clean is suboptimal TOo i Think
<awen_> RainCt: it doeSn'T SaY IN thE paCkage which ArE LGPL ANd which ARe gpl... WhaT Then?
<RainCT> aweN_: oh. and files HAve No headEr WitH The copYrighT iNFo?
<aWen_> RainCT: thEy haVe individUal copYRight noTIces... but They doN't sTatE LGPl/gPl
<RAincT> :/
<AWen_> rAiNCT: NOw i See... seems To Be HiddeN in sOME EXtra ReaDme fIles dEep in the sourcE trEe
<awEN_> RaInCT: i'Ll havE a loOk At the CopyriGht thEn
<Awen_> RainCT: what iN parTicular diD stRiKe yOu RegarDIng the PytHon Policy?
<RAinCT> awEN_: thAt THE PaCkage isn't using pyceNtRAL/pYsupport To byte-COmPiLE
<awen_> RaiNCt: it Has iT'S Own inTernAL bUild-scriPt (writTEn In Python) wHiCh the rUlEs-fIle Uses... tHIs shOuld be A sane appRoach?
<rAinCT> awen_: what dOEs the script do? CReATE.pYC filEs (iF so were are tHose INstaLled)?
<AWeN_> RaINCT: exActly... ThEY aRE installed in a sub-dirEcTory, anD the rUles-file then uSes dh_instaLL TO install ThosE FiLEs
<RainCT> awen_: I dOn't thInk the poliCY is happy With tHis, pyc's sHould rathER Be handleD by PysUppOrt OR PyCentral
<awen_> RaINcT: yoU mIght be rIghT, I'll chaNge ThaT thEn... aNy PreferencE between PyThOn-SuPpoRt/pycENtral?
 * RaiNCt doEsN't mInd
<awEN_> RainCt: and tHere Is No GEneRal ubunTU-pREFereNcE?
<RAinCt> noT tHat I kNow aBOut
<rainCT> SCottK2 mighT knOW betTeR tHough
<jaMes_w> awen_: pycenTrAl was writtEn By sOmeone INVolved in Ubuntu development, but theRE are a huGe nUmber Of paCkages usiNg eAch,
<RainCT> awen_: differenti ate in deb ian/c opy rig ht  abo ut w hich files are unde r the GPL and which un der L GP L 
<bl u ey ed> A dri2000 :  g r a b-m er ge .sh  f a il s qui temiserab le when th ere 's  nothing tom er ge. well,onl y cosmetical , b ut sti ll .
< R ainCT > a wen_:  and I ' m notsure if i ta pplies (only h a d  a  fas t look), but thep ac k age doesn't fo llow t he py t h onpol icy
<Scott K2 > Wip i ng them er g e dir clean is subo ptimal tooI  th ink
<a we n_> RainCT : itdo e sn' t say in th e pa ckage whi ch are LGPL an d  whichare GP L.. . w hatt he n? 
<R ai n CT> aw en_ :  oh . and fi le shaveno h e a d e r wi ththecopyr ight info?
<a wen _> R a inC T: th ey ha ve i nd ividu al cop yrigh tnotices... butthey  don't st ate  L GPL /G PL
<R a inCT>:/<aw en_> Ra inCT: n o w i  s e e . ..  seems to be hidde ni n  s ome extr a read m efi l es deepin  th e so u r ce tr ee
< a we n_> Rain CT: i' l lha ve a lo ok  at th ecop yri ght t h en
< awen_>  RainCT:  what in particulard id strike you re g a rd i ng t hepython poli cy?< Rain CT>a we n_: thatthe p ac k ag e  isn't using pycent ra l/pysu pport  to byte-comp ile
<awen_ > R ainCT: i t ha s  i t 's own interna l bui ld-script( writtenin py thon) wh ich the r u l es-fileuse s.. . t his s ho uld be a sane a ppro ac h?
<Rai nCT > awen_ : w hat  do esth e scriptdo? crea te .p yc  f ile s (if so werear e t ho seinsta l led)?<awen _> R ai nC T : e xactly. . .t h ey a re  i nsta lle din asub- d ire ctory,and the r ule s -fil eth en uses  dh_install t oinstall th os e f iles
< R a inCT> aw en_: I don't think thep olicy i s h appywith  this, py c's  shoul d r a ther b e hand led b ypys u p porto r  p yce nt ral
<awen_ > Rai nCT:yo u mi ght beright, I'll change tha t then... any  pr efer e n ce  be t we e n p yt h on- s u pport/pycentral ?
 * RainC Td oe sn't mind< awe n_ > RainC T: andthere is no g eneral ub untu-pref er ence ? <Ra inCT> notthat I k now about <Rain C T>  Scot tK2  might  k now  bett er tho u gh<jame s_w> a we n_: py centr al  was wri tten by someone involve d in u buntu  de velopment , b u t t here area hu ge numberofpac kages  us i ng ea ch,
<RainCT> awen_:_differentiate in_debian/copyright about which files_are under_the_GPL and_which_under LGPL
<blueyed> Adri2000:_grab-merge.sh fails quite_miserable when there's nothing_to merge. well,_only_cosmetical, but still.
<RainCT> awen_: and I'm not sure if it applies (only had a_fast_look), but_the_package_doesn't follow the python policy
<ScottK2>_Wiping the merge dir clean_is suboptimal_too I think
<awen_> RainCT: it doesn't say in_the_package which are_LGPL and which are GPL... what then?
<RainCT> awen_: oh._and files have no header with_the copyright info?
<awen_>_RainCT:_they_have individual copyright notices..._but they don't state LGPL/GPL
<RainCT> :/
<awen_>_RainCT: now i see... seems to_be hidden in some extra readme files_deep in the source tree
<awen_> RainCT:_i'll have a look at_the copyright_then
<awen_> RainCT: what in particular_did strike you_regarding the_python policy?
<RainCT> awen_:_that the package isn't using pycentral/pysupport_to byte-compile
<awen_> RainCT:_it has it's own internal build-script_(written_in python) which_the_rules-file_uses... this_should be a_sane_approach?
<RainCT> awen_:_what_does the script do? create.pyc files_(if_so were are those installed)?
<awen_> RainCT: exactly..._they are installed in_a_sub-directory, and the rules-file_then uses dh_install to install_those files
<RainCT> awen_: I don't think_the policy_is happy_with this, pyc's should rather be handled by pysupport or pycentral
<awen_>_RainCT: you might be right, I'll_change that then... any_preference between_python-support/pycentral?
_* RainCT doesn't_mind
<awen_>_RainCT: and_there is no general ubuntu-preference?
<RainCT> not that_I know_about
<RainCT> ScottK2 might know better though
<james_w>_awen_: pycentral was written_by_someone involved in ubuntu development, but_there are a huge number of_packages using each,