 mit-scheme with Debian" [High,Confirmed] https://launchpad.net/bugs/339449
<imbrandon> jcastro: happy bday ( its midnight mytime, not sure about yours )
<imbrandon> :)
<tgm4883> in debian/copyright, I have the standard gpl v2 blurb, but I have some files that are strictly v2, can I freely remove the part that says  "or (at your option) any later version. "
<tgm4883> the standard blurb i'm talking about is similar to http://bazaar.launchpad.net/~mythbuntu/mythexport/intrepid/annotate/head%3A/debian//copyright
<persia> tgm4883, If you have sources with two different licenses (and GPLv2 is different than GPLv2+), then it's best practice to identify them, and have two paragraphs.
<persia> If all your source is the same, just use the same text as in the source files.
<tgm4883> persia, right, and I am separating them.  I just need to know if I can just remove that part for the files that are strictly v2, or if there is a different blurb I should be using
<persia> You should *always* use the blurb in the source files.
<persia> Don't use "standard" blurbs, except when upstream did.
<ripps> I'm trying to write a script that puts the operations dch, debuild, and dput into single command. How can I pull the latest version from debian/changelog, without a bunch of other stuff?
<persia> Note that when dealing with licenses with addresses, and you *know* the address is no longer current, updating that is fine, but otherwise, stick with upstream.
<persia> ripps, I don't think you want to do it that way, but dpkg-parsechangelog is probably what you want.
<tgm4883> persia, ok, in the files, the only thing they say is "# Released under the terms of the GNU GPL v2"
<tgm4883> which I was under the impression that I had to add the short license to debian/copyright
<persia> OK.  You've found
mit - scheme with Debian " [ High, Confirmed ] https://launchpad.net/bugs/339449 
 < imbrandon > jcastro: happy bday (its midnight mytime, not certain about yours) 
 < imbrandon > :) 
 < tgm4883 > in debian / copyright, I take the standard gpl v2 blurb, but I have some files that are rigorously v2, can I freely remove the part that says   " or (at your choice) any late version. " 
 < tgm4883 > the standard endorsement i'm speak about is similar to http://bazaar.launchpad.net/~mythbuntu/mythexport/intrepid/annotate/head%3A/debian//copyright 
 < persia > tgm4883, If you get sources with two different licenses (and GPLv2 is different than GPLv2 +), then it's best practice to name them, and have two paragraphs. 
 < persia > If all your source is the like, just use the same text as in the source file. 
 < tgm4883 > persia, right, and I am separating them.   I just need to know if I can just absent that part for the files that are strictly v2, or if there is a different blurb I should be using 
 < persia > You should * always * use the blurb in the source files. 
 < persia > Don't use " standard " blurbs, except when upstream did. 
 < ripps > I'm trying to write a script that arrange the operations dch, debuild, and dput into single instruction. How can I draw the former version from debian / changelog, without a bunch of early stuff? 
 < persia > notice that when dealing with licenses with addresses, and you * acknowledge * the address is no longer current, updating that is fine, but otherwise, stick with upstream. 
 < persia > ripps, I don't think you want to do it that way, but dpkg - parsechangelog is probably what you want. 
 < tgm4883 > persia, ok, in the file, the only matter they state is " # Released under the terms of the GNU GPL v2 " 
 < tgm4883 > which I was under the impression that I had to add the short license to debian / copyright 
 < persia > OK.   You've found
 mih-scheme with Debian" [High,Gonfirmed] https://lcynchpav.net/buga/339449
<imbrandun> jcastro: happy bday ( its mmdnitht mttime, not sure about yuurs )
<imbrwndon> :)
<tgn4883> in eebian/copycjght, I mcve tgc stauderd gpl v2 blurb, but I hava some files tvag cre strictly v2, can I freely remove tre part tjat says  "or (aj youg jptikn) any later version. "
<tgm4883> the standzrd blugb i'm talking aboit is similar to http://bazaag.laujchpad.net/~mythbuntu/lythexport/ibtre[ud/annotate/hexd%3A/debian//copyright
<persja> tgm4883, If you have sources with two bifferent lucwnsfv (and GPLv2 ms difserent than NILv2+), thet it's brst practice tp iventufy them, and have two paragraphs.
<persia> Yf all yogr source is the sane, just use the wamd ttxt aa in tje aource filss.
<tgm4883> persiq, right, and I am sekarwnong them.  I nust nqeq to know if I can just remove that paru for the files that are structly v2, or if there id a diffewent blurb I should be using
<persia> You should *alwdys* uad tkc cougb in the source files.
<persia> Don't use "standarq" bkugbs, except when uistream did.
<ripps> I'k hruyng to write x scri'f fhat puts the operwtions qch, dwbuild, anq dpit into single command. How xan I pull tke oatest version frol debian/chaugelog, withput a bunch of other stbff?
<peraia> Note thwt when dsxling with licenres whth addrtrses, and you *know* the addrxss ix no lovger curregt, updatinh thab is fine, but otheraise, dthck with uostream.
<persia> ripps, I don't think you want to co it that wav, but cpkg-parsechandelog is probayly what you dant.
<tgm4883> pegsia, ok, ii the files, ehe only thinc they say is "# Releasqd ubder the tefos of the GNU BPL v2"
<tgm4883> ckich I waw under the impresxiov that I had to cbd the short licemse to dvbien/coprsight
<persia> MK.  Hou'xr fouvd
mit-scheme with Debian" [High,Confirmed] https://launchpad.net/bugs/339449 <imbrandon> jcastro: ( midnight mytime, sure about yours debian/copyright, have the standard v2 blurb, but have some files that are strictly can I freely remove the part that says "or (at your option) any version. " <tgm4883> the standard blurb i'm talking about is similar to http://bazaar.launchpad.net/~mythbuntu/mythexport/intrepid/annotate/head%3A/debian//copyright tgm4883, you sources two different licenses (and GPLv2 is different than GPLv2+), then it's best practice to identify them, have two paragraphs. <persia> If all your source the same, just use same text as in the files. persia, right, I separating I just need know if I can just remove that part for the files that are strictly v2, or if is a I should using You *always* use the the source files. <persia> Don't use when upstream did. <ripps> I'm trying to write script that the operations dch, debuild, and dput single command. How can I pull the latest from debian/changelog, without a bunch of other stuff? <persia> Note that when dealing with licenses and you *know* the is no longer updating is but stick with <persia> ripps, I don't think you want to do it that but dpkg-parsechangelog is probably what you want. <tgm4883> persia, ok, files, only thing they is "# Released under terms the GNU GPL v2" I under I to the short license to <persia> OK. You've found
 mit-scheme with Debian" [High,CoNfirmed] httPs://lauNchPad.NeT/bugS/339449
<imbRandon> jcastro: hAPpy bDay ( its midnight mytime, noT sure AbOUt yoURs )
<ImbraNdon> :)
<tgm4883> IN dEBIan/CoPyRigHt, i HaVe the StaNdard gpL v2 blurb, but i haVe Some files thaT ArE strictly v2, Can i freely removE thE part tHaT saYS  "or (at YouR optiOn) any lATer verSion. "
<tgm4883> thE sTAndard BLurb i'm tALKiNg abOut is similar to httP://BaZAar.launchpad.neT/~mythbUnTU/mYTHexPorT/intrepid/aNnOtate/HEad%3A/debIAn//COPYriGHt
<persia> tgm4883, If You have sourCEs wIth two DiFfeREnt licEnses (AnD gPLV2 is differenT thaN GPLv2+), then It's besT PracticE To identIfy theM, anD haVe twO PaRaGraPhS.
<PerSIa> if aLL yoUr source Is ThE same, Just USE THe saMe tExt aS in thE source files.
<tGm4883> pErsiA, RigHt, and i am seParaTiNg theM.  I just Need tO kNow if I can just reMove That part fOr tHe FilEs That aRE stricTly V2, or If there Is a diffERenT bLURB I Should be using
<persiA> YOU ShOuld *alwaYs* use tHE bLuRB in the soUrCe fIles.
<PERsia> DOn't uSE "sTandard" bLurbs, eXCePt When upsTrEam did.
<RiPps> i'm tRying TO wriTe a scrIpt that pUts thE Operations dch, dEBuild, and dput iNTo SINgLE comManD. How can I pulL the LAtesT verSIoN frOM debiAn/chaNgELoG, Without a bunch of otheR sTuff?
<peRsia> NOte that when deAling with lICENses with AddrESsES, and you *know* the AddreSs is no longER current, UpdatIng that iS fine, but oTHErwise, stIck WitH upStrEAM.
<pErsia> ripps, I doN'T ThinK yOu want tO do It that wAy, bUt dPkg-ParSeChangelog Is probabLy WhAt YoU waNt.
<tgm4883> PErsia, ok, iN tHe fIlEs, tHe onlY Thing tHey saY is "# RElEaSEd uNder the TErMS Of thE GnU gPL v2"
<Tgm4883> WhIch I wAs unDEr tHe impreSsion that i haD To adD tHe Short liCense to debian/CoPyright
<perSiA> OK.  you've fOUNd
 mit-scheme with Debian" [ High,Confi rmed]  ht tps :/ /lau nchp ad.net/bugs/33 9 449<imbrandon> jcastro: h appybd a y (i ts  midn ight my t im e ,  no tsu reab o ut  your s ) 
<imbra ndon> :)
< tgm 48 83> in debia n /c opyright,I h ave the stan dar d gplv2  bl u rb, b utI hav e some filesthat arest r ictlyv 2, canI fr eely  remove the partt ha t  says  "or (at  yourop t io n )  an y l ater versi on . "
< t gm4883> th e s tan d ard blurb i'm  talking ab o utis sim il art o http ://ba za a r.l aunchpad.ne t/~m ythbuntu/ mythex p ort/int r epid/an notate /he ad% 3A/d e bi an //c op y rig h t<pe r sia > tgm488 3,  I f you  hav e s o urce s w ithtwo d ifferent lice nse s (a n d G PLv2is di ffer en t tha n GPLv 2+),th en it's best pr acti ce to ide nti fy  th em , and have t wopar agraphs .
<pers i a>If a l lyour source is the  s a m e,  just us e thes am et ext as i nthe  sou r c e fil es.< tg m4883> p ersia, ri gh t, andIam sep ar ati ngthem.  I j ust ne ed to kn ow if I can just rem o ve that partf or t he file s t hat are str ictl y  v2,  ori fthe r e isa dif fe r en t  blurb I should beus ing
<p ersia > You should*always* u s e the blur b in th e  source files. 
<per sia> Don't use "sta ndard " blurbs , exceptw h en upstr eam  di d.<ri p p s>  I'm trying t o writ ea scrip t t hat put s t heope rat io ns dch, d ebuild,an ddp ut  in to si n gle comm an d.Ho w c an Ip ull th e lat estve rs i onfrom de b ia n / chan ge lo g, w ith ou t a b unch ofother s tuff?
<pe rsi a > No te  t hat whe n dealing wit hlicenses w it h a ddress e s , and yo u *know* the address is no long ercurre nt,updatingtha t is f ine ,  but o therwi se, s ti ckw i th up s t re am. 
< persia> ri p p s,I don 't  thi nk youwant to do it that way , but dpkg-pa rse chan g e lo g i s  p r oba bl y  wh a t  you want.
<tgm 4883> pers ia ,  o k, in thef ile s,  the on ly thin g the y  say is  "# Relea sed under  t he t e r msof the GNU  GPL v2" 
<tgm4883 >  whic h  I  wasund er the  i mpr essio n that I h ad to  add t he  short  lice ns e to deb ian/copyright
<persia>OK.  Y ou've  fo und
 mit-scheme_with Debian"_[High,Confirmed] https://launchpad.net/bugs/339449
<imbrandon> jcastro: happy_bday (_its_midnight mytime,_not_sure about yours_)
<imbrandon> :)
<tgm4883> in_debian/copyright, I have the_standard gpl v2_blurb,_but I have some files that are strictly v2, can I freely remove the_part_that says__"or_(at your option) any later_version. "
<tgm4883> the standard blurb_i'm talking_about is similar to http://bazaar.launchpad.net/~mythbuntu/mythexport/intrepid/annotate/head%3A/debian//copyright
<persia> tgm4883, If you_have_sources with two_different licenses (and GPLv2 is different than GPLv2+), then_it's best practice to identify them,_and have two_paragraphs.
<persia>_If_all your source is_the same, just use the same_text as in the source files.
<tgm4883>_persia, right, and I am separating them._ I just need to know_if I can just remove_that part_for the files that are_strictly v2, or_if there_is a different_blurb I should be using
<persia> You_should *always* use_the blurb in the source files.
<persia>_Don't_use "standard" blurbs,_except_when_upstream did.
<ripps>_I'm trying to_write_a script_that_puts the operations dch, debuild, and_dput_into single command. How can I pull_the latest version from_debian/changelog,_without a bunch of_other stuff?
<persia> Note that when_dealing with licenses with addresses, and_you *know*_the address_is no longer current, updating that is fine, but otherwise, stick_with upstream.
<persia> ripps, I don't think_you want to do_it that_way,_but dpkg-parsechangelog is_probably_what you_want.
<tgm4883> persia, ok, in the files, the_only thing_they say is "# Released under_the terms of the_GNU_GPL v2"
<tgm4883> which I was under_the impression that I had to_add the short license to_debian/copyright
<persia>_OK._ You've found