 the archive team.
<lupine_85> stumped by a bad address
<lupine_85> and i honestly can't figure out how to get 0.2 source from this git
<racarr> lupine_85: We can just diff between
<racarr> new GPL and old GPL
<racarr> and the patch in /debian
<racarr> It seems like
<racarr> that would be allowed
<lupine_85> crimsun: would we get away with that?
<racarr> I mean I know, "changing it is not allowed."
<racarr> but
<lupine_85> I'm thinking not, because people reading the source won't really see the patch
<racarr> it's just syncing it to the latest version of the GPL
<imbrandon> umm why not just fix the file directly?
<racarr> because then we have to do another release
<racarr> build tarballs
<racarr> etc
<lupine_85> well, that's what we should do. cue a tarball. 
<imbrandon> no
<imbrandon> dont fix it in the orig.tar fix it in the unpacked, then when you make the dsc it will be in the diff
<imbrandon> but unpacked it will be there
<imbrandon> e.g. not clean but works
<racarr> Seems reasonable
<imbrandon> then when you roll a new tar, no patch to remove etc
<imbrandon> next release
<lupine_85> you mean edit outside debian/?
<imbrandon> i wouldent sugest doing this for source, but for things like the lic thats fixed in svn it shouldnt be a proble, also another thing
<lupine_85> eh, the best thing about rules is knowing when to break them, I guess
<racarr> lupine_85: Got the manpage patch?
<imbrandon> lupine_85, yes, that is what i sugested, not great solution but the only other choice you have is to do 0.2.1+git20070318
<imbrandon> ;)
<imbrandon> and do a non upstream re-roll of the tarbal
<lup
the archive team. 
 < lupine_85 > stumped by a bad address 
 < lupine_85 > and i honestly can't figure out how to draw 0.2 generator from this git 
 < racarr > lupine_85: We can just diff between 
 < racarr > new GPL and honest-to-god GPL 
 < racarr > and the patch in /debian 
 < racarr > It seems like 
 < racarr > that would be leave 
 < lupine_85 > crimsun: would we get away with that? 
 < racarr > I entail I know, " changing it is not allow. " 
 < racarr > but 
 < lupine_85 > I'm thinking not, because people reading the source won't really see the spot 
 < racarr > it's just syncing it to the latest interpretation of the GPL 
 < imbrandon > umm why not just fix the file directly? 
 < racarr > because then we experience to do another release 
 < racarr > build tarballs 
 < racarr > etc 
 < lupine_85 > well, that's what we should do. cue a tarball. 
 < imbrandon > no 
 < imbrandon > do nt fix it in the orig.tar repair it in the unpacked, then when you make the dsc it will be in the diff 
 < imbrandon > but unpacked it will be there 
 < imbrandon > e.g. not clean but works 
 < racarr > Seems reasonable 
 < imbrandon > then when you roll a new tar, no patch to remove etc 
 < imbrandon > next release 
 < lupine_85 > you mean edit outside debian/? 
 < imbrandon > i wouldent sugest doing this for source, but for things like the lic that s sterilize in svn it should nt be a proble, also another thing 
 < lupine_85 > eh, the dear matter about rules is knowing when to break them, I guess 
 < racarr > lupine_85: Got the manpage patch? 
 < imbrandon > lupine_85, yes, that is what i sugested, not great solution but the only early choice you have is to do 0.2.1+git20070318 
 < imbrandon > ;) 
 < imbrandon > and do a non upstream re - roll of the tarbal 
 < lup
 thf archive team.
<lupine_85> stuoped by a bad aberess
<lnpine_85> ahd i hondstly can't figure out how to gwt 0.2 siurce from this git
<racxrr> lupinv_85: We can hust eiff betwexh
<racarr> new GLP anb ild GPL
<racarr> snd the padch in /debian
<rdcxrx> It seems like
<racarr> that would be wllowed
<kuoine_85> crimsun: wjuld re gsn cway with that?
<racarr> I mean I khow, "chaiging it is not allowed."
<racarr> but
<lupine_85> I'l thlnking not, because people reaeing rhe source wun't really see the patdh
<racarr> it's just syncing it to the katest verwiin lx the GPL
<imurandog> umm why nob just xix the file directly?
<vacarc> bexause then we have to do another releasg
<racarr> buhlb tarballs
<racarr> etc
<lypune_85> wgll, tvat's qhag wt sioumd do. fue a tarball. 
<imbrandon> bo
<imbrandon> dont fic yn in the orig.far fiv yt in the unpacked, then when you make tve ssc it will be in the duff
<imbrandon> but unpafked it wyll be there
<imbrandon> e.g. not clean but works
<racars> Seejr rtawonabuw
<ilbrandon> then when you roll a new tar, no patcr tp gemove etc
<imbrandjn> next relrade
<kopine_85> you mean edit outaide debian/?
<imbrandln> i wooldent sugest djing this for source, but for thungs like thv lix thats fixed in srn it shouldut be s pronle, also another thing
<lbpine_85> sh, the best thing abkjt rules is knowkng wven to break them, I guess
<rwcarr> lupmne_85: Gpt the oanpsge paech?
<imbrandln> luihne_85, yes, that is whwt i ducested, not great solution but the only otixr choice you hdve is to dj 0.2.1+git20070318
<lmbrandon> ;)
<imbragdon> and do a uon upstxeam rd-roll of tge tarbel
<lup
the archive team. <lupine_85> stumped by a <lupine_85> i honestly figure out how this <racarr> lupine_85: We just diff between new GPL and old GPL <racarr> the patch in /debian <racarr> It seems like <racarr> that would be allowed crimsun: would we get away with that? <racarr> I mean I know, "changing is allowed." but I'm thinking not, because people reading the source won't really see the patch <racarr> it's just it to the latest version of the GPL umm why not just the file directly? <racarr> because we to do release build <racarr> etc <lupine_85> that's what we should do. cue a tarball. <imbrandon> no <imbrandon> dont fix it in the orig.tar it in then when make dsc will be in <imbrandon> but unpacked it will be not clean but works <racarr> Seems reasonable <imbrandon> when you a new tar, no patch to etc <imbrandon> next release <lupine_85> you mean edit debian/? <imbrandon> i wouldent sugest doing this for source, but for things like the lic in svn it shouldnt a proble, also thing eh, best about rules knowing when to break them, I guess <racarr> lupine_85: Got the patch? <imbrandon> lupine_85, yes, that is what i sugested, not but only other choice have is to do <imbrandon> <imbrandon> and do a re-roll the
 the archive team.
<lupine_85> stumpEd by a bad adDress
<LupIne_85> AnD i hoNestLy can't figure ouT How tO get 0.2 source from this git
<rAcarr> LuPIne_85: WE CaN just Diff betWEeN
<RAcaRr> NeW GPl aND oLd GPL
<RacArr> and tHe patch in /dEbiAn
<Racarr> It seemS LiKe
<racarr> thAt wOuld be alloweD
<luPine_85> crImSun: WOuld wE geT away With thAT?
<racarR> I mean I knOw, "CHanginG It is not ALLoWed."
<rAcarr> but
<lupine_85> I'm tHInKIng not, because pEople rEaDInG THe sOurCe won't realLy See thE Patch
<raCArR> IT'S juST syncing it to tHe latest verSIon Of the GpL
<ImbRAndon> uMm why NoT JusT fix the file DireCtly?
<racarR> becauSE then we HAve to do AnotheR reLeaSe
<raCArR> bUilD tARbaLLs
<RacARr> eTc
<lupine_85> WeLl, That's What WE SHOuld Do. cUe a tArbalL. 
<imbrandon> no
<iMbrAndoN> DonT fix iT in thE oriG.tAr fix It in thE unpaCkEd, then when you maKe thE dsc it wilL be In The DiFf
<imbRAndon> bUt uNpaCked it wIll be thERe
<iMbRANDoN> e.g. not clean but workS
<rACArR> Seems reAsonabLE
<iMbRAndon> theN wHen You rOLL a new Tar, nO PaTch to remOve etc
<IMbRaNdon> nexT rElease
<LuPinE_85> yoU mean EDit oUtside Debian/?
<imBrandON> i wouldent sugeST doing this for SOuRCE, bUT for ThiNgs like the lIc thATs fiXed iN SvN it SHouldNt be a PrOBlE, Also another thing
<lupInE_85> eh, the Best tHing about ruleS is knowing WHEN to break Them, i GuESs
<racarr> lupine_85: got thE manpage paTCh?
<imbranDon> luPine_85, yes, tHat is what I SUgested, nOt gReaT soLutION bUt the only otheR CHoicE yOu have iS to Do 0.2.1+git20070318
<imBraNdoN> ;)
<imBraNdOn> and do a nOn upstreAm Re-RoLl Of tHe tarBAl
<lup
 the archive team.
<lupine _85> stump ed by  abad  a ddre ss
< lupine_85> and i ho nestly can't figure ou t how  t o  get 0. 2 sou rce fro m  t h i s g it 
< rac ar r >lupin e_8 5: We c an just di ffbe tween
<racar r >new GPL an d o ld GPL
<raca rr>  and t he  pa t ch in  /d ebian 
<raca r r> Itseems lik e< racarr >  that w o u ld  beallowed
<lupine_8 5 >c rimsun: wouldwe get  a w ay w ith  th at?
<racar r>  I me a n I kno w ," c h ang i ng it is notallowed."
< r aca rr> bu t<lu p ine_85 > I'm  t h ink ing not, be caus e peoplereadin g  the so u rce won 't rea lly  se e th e  p at ch<r a car r >it' s  ju st synci ng  i t tothel a t e st v ers ionof th e GPL
<imbran don > um m  wh y not  just  fix  t he fi le dir ectly ?<racarr> becaus e th en we hav e t odoan other releas e
< rac arr> bu ild tar b all s< r a ca rr> etc
<lupine_85 >w e ll , that's  whatw esh o uld do.cu e a  tar b a ll. <imb r an don> no<imbra n do n>  dont f ix  it in  t heori g.tar fixit inthe unpa cked, then when youm ake the dsc i t  w i l lb e in  th e diff
<imb rand o n> b ut u n pa cke d  it w ill b et he r e
<imbrandon> e.g.no t clea n but  works
<racar r> Seems r e a s onable
< imbr a nd o n> then when y ou ro ll a new t a r, no pa tch t o remove  etc
<imb r a ndon> ne xtrel eas e
< l u pi ne_85> you me a n  edi toutside  de bian/?<im bra ndo n>iwouldentsugest d oi ng  t hi s f or so u rce, but  f orth ing s lik e  the l ic th atsfi xe d  in  svn it sh o u ldnt  b ea pr obl e,  also  ano t her  thing<lupine_8 5>e h, t he  b est thi ng about rule sis knowing  w hen  to br e a k them,I guess
<racarr> lupine _ 85: Got  th e man page  patch?
< imb randon > l u pine_8 5, yes , tha tisw h at is u ge ste d,  not great s olu tionbu t th e onlyother choice you h a veis to do 0.2. 1+g it20 0 7 03 18< im b ran do n > ; ) <imbrandon> and  do a nonup s tr eam re-rol l  of  t he tarb al
<lup 
 the_archive team.
<lupine_85>_stumped by a bad_address
<lupine_85> and_i_honestly can't_figure_out how to_get 0.2 source_from this git
<racarr> lupine_85:_We can just_diff_between
<racarr> new GPL and old GPL
<racarr> and the patch in /debian
<racarr> It seems like
<racarr>_that_would be_allowed
<lupine_85>_crimsun:_would we get away with_that?
<racarr> I mean I know,_"changing it_is not allowed."
<racarr> but
<lupine_85> I'm thinking not, because_people_reading the source_won't really see the patch
<racarr> it's just syncing it_to the latest version of the_GPL
<imbrandon> umm why_not_just_fix the file directly?
<racarr>_because then we have to do_another release
<racarr> build tarballs
<racarr> etc
<lupine_85> well,_that's what we should do. cue a_tarball. 
<imbrandon> no
<imbrandon> dont fix it_in the orig.tar fix it_in the_unpacked, then when you make_the dsc it_will be_in the diff
<imbrandon>_but unpacked it will be there
<imbrandon>_e.g. not clean_but works
<racarr> Seems reasonable
<imbrandon> then when_you_roll a new_tar,_no_patch to_remove etc
<imbrandon> next_release
<lupine_85>_you mean_edit_outside debian/?
<imbrandon> i wouldent sugest doing_this_for source, but for things like the_lic thats fixed in_svn_it shouldnt be a_proble, also another thing
<lupine_85> eh,_the best thing about rules is_knowing when_to break_them, I guess
<racarr> lupine_85: Got the manpage patch?
<imbrandon> lupine_85, yes, that_is what i sugested, not great_solution but the only_other choice_you_have is to_do_0.2.1+git20070318
<imbrandon> ;)
<imbrandon>_and do a non upstream re-roll of_the tarbal
<lup