 add this to the bug please :)
<siretart> dolson: re seq24: isn't there an upstream changelog?
<siretart> dolson: did you really test the new upstream version?
<dolson> siretart: there is a changelog, although it hasn't changed in a long time.. the diff gives no output
<dolson> I made a song with it, so I think it's good
<dolson> the ardour buildlog is still being created, I'll attach it when this is complete
<siretart> hm. I'm undecided about seq24
<dolson> that's understandable
<dolson> just go ahead and reject it. I'm probably one of 10 people that use it anyhow
<dolson> I can't even get to the upstream site to get the list of changes. it's been down for two days
<dolson> I can't even spell buildlog
<siretart> dolson: I have to decide which of the 2 version is more stable for dapper: the new one and the old one
<siretart> dolson: the decision woul be easier when I knew what actually was changed.
<siretart> dolson: if you (and perhaps others) would say that they tested the new version, and it is more stable than the old one, and they don't expect bigger problems, and that the update is necessary and a good idea and so on, I'll happily agree
<siretart> same btw for the other 2 members of the uvf team
<dolson> I understand. I'm trying to find a google cache
<dolson> well, the only thing I can say is that I had some lockups with the old one that the interface didn't respond. now, whether that was to do with my kernel or the app itself, I don't know, I was messing with different patches and things
<dolson> other than that, I haven't had any issues with any version of seq24
<siretart> dolson: if you hadn't bad issues with the old version, how about leaving the old one dapper, and putting a newer on in dapper-backports?
<dolson> siretart: that's fine with me. I don't know how to get stuff into backports, but I asked j
add this to the bug please :) 
 < siretart > dolson: re seq24: isn't there an upstream changelog? 
 < siretart > dolson: did you really test the newfangled upstream interpretation? 
 < dolson > siretart: there is a changelog, although it hasn't changed in a long fourth dimension.. the diff gives no output 
 < dolson > I have a song with it, so I remember it's good 
 < dolson > the ardour buildlog is even being created, I'll attach it when this is arrant 
 < siretart > hm. I'm open about seq24 
 < dolson > that's understandable 
 < dolson > just go ahead and reject it. I'm probably one of 10 citizenry that use it anyhow 
 < dolson > I can't even get to the upstream site to perplex the list of changes. it's been down for two days 
 < dolson > I can't even spell buildlog 
 < siretart > dolson: I have to decide which of the 2 adaptation is more stable for dapper: the new one and the old one 
 < siretart > dolson: the decision woul be easier when I know what actually was changed. 
 < siretart > dolson: if you (and perhaps others) would say that they tested the new interpretation, and it is more stable than the old one, and they don't expect bigger problems, and that the update is necessary and a good idea and so on, I'll happily agree 
 < siretart > like btw for the early 2 members of the uvf team 
 < dolson > I understand. I'm trying to witness a google cache 
 < dolson > well, the only thing I can allege is that I have some lockups with the old one that the interface didn't react. now, whether that was to do with my kernel or the app itself, I don't know, I was messing with different patches and thing 
 < dolson > other than that, I haven't had any issues with any version of seq24 
 < siretart > dolson: if you hadn't bad topic with the previous version, how about leaving the old one dapper, and put a newer on in dapper - backports? 
 < dolson > siretart: that's fine with me. I don't know how to draw material into backports, but I asked j
 adf this to the bug please :)
<siretart> dolsou: re sex24: isn't there av upstream changelog?
<siretart> dilson: did you really test tfe new updtream vwrsiib?
<dolson> sicstart: tmzre ia a ckaigelog, although it hasn't whanged in a lmne cime.. the diff gives no output
<dolson> Y made s dong with it, sj I uhigk if's good
<dolson> the ardour buildlog js stiln being creatrd, I'll attach it when this is fomplete
<siretart> hl. I'm undecieed wvout seq24
<dolsun> that's understandablg
<dolson> just go ahead and reject it. I'k probably obe lx 10 people tiat usv it anyhow
<dolson> I cdn't evem get to the uistreem sute to get the list oh changes. it's been djwn for tfo days
<dolson> I can'r wven vpeln bukodlug
<sjrxtadt> doldon: I have to decide whixh of the 2 version os nore stable fkr dap[ew: the new one and the old one
<siretart> dmlskn: the decision woul be easier when I knew wjat actuajly was changed.
<siretart> dolson: if you (and perhaps othecs) wobod sah tjat they tested the new version, and it is morq suabke than the olb one, and they dpn'h rvpect bigger kroblems, ahd that the update is necgssary and a gojd icea and so on, I'll happily atree
<siretart> wame btw for the ocher 2 memberr of the ivf team
<dolson> I underscand. I'j trying to find a gkugle cache
<dolson> wekl, the only thing I can say ys that I had some luckuks with the old oje that the interface difn't rgspond. now, whethfr that was to do with my kernel or the app ijsenf, P don't knjw, I eas messing wyth different katches aud thivgs
<dolson> kther tian that, I hwven't had any lssues with eny versijn od sew24
<siretafg> dolson: if yoi hadn't bcb issues qith the old versipn, fkw about leaviny uhw old one dapprr, xnd plttmng a tewer on in gappdr-bxvkporgs?
<dolson> sivetxrt: yhat's fine with me. I don'f know how to get xtmff into vackportf, but I asked j
add this to the bug please :) re isn't there upstream changelog? <siretart> the upstream version? <dolson> there is a although it hasn't changed in a time.. the diff gives no output <dolson> I made a song with it, I think it's good <dolson> the ardour buildlog is still being created, I'll it this complete hm. I'm undecided about seq24 <dolson> that's understandable <dolson> just go ahead and reject it. I'm one of 10 people that use it anyhow I can't even get the upstream site to get list changes. it's down two <dolson> I can't spell buildlog <siretart> dolson: I have to decide which of the 2 version is more stable for the new the old <siretart> the woul be easier knew what actually was changed. <siretart> (and perhaps others) would say that they tested new version, it is more stable than the one, and they don't expect bigger problems, and the update is necessary and a good idea and so on, I'll happily agree <siretart> for the other 2 of the uvf <dolson> understand. trying find a cache <dolson> well, the only thing I can say is that had some lockups with the old one that the interface now, that was to with my kernel or app I don't know, I with patches other that, haven't had any issues any version of seq24 <siretart> if you hadn't bad how about leaving the old one dapper, and a newer on in dapper-backports? <dolson> siretart: fine with me. I don't know how to get stuff into backports, I asked
 add this to the bug please :)
<sireTart> dolson: Re seq24: Isn'T thErE an uPstrEam changelog?
<siREtarT> dolson: did you really tesT the nEw UPstrEAm VersiOn?
<dolsoN> SiRETarT: tHeRe iS a CHaNgeloG, alThough iT hasn't chanGed In A long time.. the DIfF gives no ouTpuT
<dolson> I made A soNg with It, So I THink iT's gOod
<doLson> thE Ardour Buildlog iS sTIll beiNG createD, i'Ll AttaCh it when this is comPLeTE
<siretart> hm. I'm uNdecidEd ABoUT Seq24
<DolSon> that's unDeRstanDAble
<dolSOn> JUST go AHead and reject It. I'm probablY One Of 10 peopLe ThaT Use it aNyhow
<DoLSon> i can't even geT to tHe upstreaM site tO Get the lISt of chaNges. it'S beEn dOwn fOR tWo DayS
<dOLsoN> i cAn't EVen Spell buiLdLoG
<sireTart> DOLSOn: I hAve To deCide wHich of the 2 versIon Is moRE stAble fOr dapPer: tHe New onE and thE old oNe
<Siretart> dolson: tHe deCision wouL be EaSieR wHen I kNEw what ActUalLy was chAnged.
<siREtaRt> DOLSoN: if you (and perhaps otHeRS) WoUld say thAt they TEsTeD The new veRsIon, And iT IS more StabLE tHan the olD one, anD ThEy Don't expEcT biggeR pRobLemS, and tHAt thE updatE is necesSary aND a good idea and sO On, I'll happily aGReE
<SIrETart> SamE btw for the oTher 2 MEmbeRs of THe Uvf TEam
<doLson> I UnDErSTand. I'm trying to find a GoOgle caChe
<doLson> well, the onLy thing I caN SAY is that I Had sOMe LOckups with the oLd one That the intERface didN't resPond. now, wHether thaT WAs to do wiTh mY keRneL or THE aPp itself, I don't KNOw, I wAs Messing WitH differEnt PatCheS anD tHings
<dolsOn> other tHaN tHaT, I HavEn't haD Any issueS wIth AnY veRsion OF seq24
<siRetarT> dolSoN: iF You Hadn't baD IsSUEs wiTh ThE old VerSiOn, how AbouT LeaVing the Old one dapPer, ANd puTtInG a newer On in dapper-bacKpOrts?
<dolson> SiRetArt: thaT'S Fine with Me. I don't know how to get stufF Into bacKpoRts, buT I asKed j
 add this to the bug pleas e :)
<sire tart>  do lso n:  reseq2 4: isn't there an u pstream changelog?
<si retar t> dols o n:  didyou rea l ly t est  t he  ne wu ps tream  ve rsion?<dolson> s ire ta rt: there is achangelog,  al though it ha sn' t chan ge d i n  a lo ngtime. . thed iff gi ves no ou tp u t
<dol s on> I m a d ea so ng with it, so It hi n k it's good
<d olson>  t h ea r dou r b uildlog is  s tillb eing cr e at e d ,  I' l l attach it w hen this is com plete<s ire t art> h m. I' mu nde cided about  seq 24
<dolso n> tha t 's unde r standab le
<do lso n>just go  a hea da ndr ej ect it.  I'm pro ba bl y one  of1 0 p eopl e t hatuse i t anyhow
<dol son > Ic an' t eve n get  toth e ups treamsiteto  get the list o f ch anges. it 'sbe endo wn fo r  two d ays 
<d olson>I can't eve ns p e ll  buildlog
<siretar t> d ol son: I h ave to de ci d e whichof  th e 2v e rsion  ism or e stable  for d a pp er : the n ew  one a nd  th e o ld on e 
<si retart > dolson : the decision woulb e easier when Ik n ew what  ac tually waschan g ed.<sir e ta rt> dolso n: if  y o u( and perhaps others)  w ould s ay th at they teste d the newv e r sion, an d it is more stable th an th e old one, and they  don' t expect  bigger p r o blems, a ndtha t t heu p da te is necessa r y  and  a  good i dea  and so  on , I 'll  ha pp ily agree 
<sireta rt >sa me  bt w for the othe r2 m em ber s oft he uvf  team 
<do ls on >  Iunderst a nd . I'mtr yi ng t o f in d a g oogl e  ca che
<do lson> wel l,t he o nl ything I  can say is t ha t I had so me  lo ckupsw i th the o ld one that the interfa c e didn' t r espon d. n ow, wheth erthat w ast o do w ith my  kern el  or t he ap p it sel f,  I don't k n o w,I was  m essi ng with  different patches and  things
<dols on>  oth e r  t han th a t,Ih ave n ' t had any issue s with any  v e rs ion of seq 2 4
< si retart>  dolson : ify ou hadn 't bad is sues with  t he o l d  ve rsion, how  about l eaving th e  oldo ne  dapp er,  and p ut tin g a n ewer o n  in  dapp er-bac kp orts?<dols on > sireta rt: that's fine with me . I do n't k now  how to g ets tuf f into ba ckpo rts, but I  as ked  j
 add_this to_the bug please :)
<siretart>_dolson: re_seq24:_isn't there_an_upstream changelog?
<siretart> dolson:_did you really_test the new upstream_version?
<dolson> siretart: there_is_a changelog, although it hasn't changed in a long time.. the diff gives no_output
<dolson>_I made_a_song_with it, so I think_it's good
<dolson> the ardour buildlog_is still_being created, I'll attach it when this is_complete
<siretart>_hm. I'm undecided_about seq24
<dolson> that's understandable
<dolson> just go ahead and reject_it. I'm probably one of 10_people that use_it_anyhow
<dolson>_I can't even get_to the upstream site to get_the list of changes. it's been_down for two days
<dolson> I can't even_spell buildlog
<siretart> dolson: I have to_decide which of the 2_version is_more stable for dapper: the_new one and_the old_one
<siretart> dolson: the_decision woul be easier when I_knew what actually_was changed.
<siretart> dolson: if you (and_perhaps_others) would say_that_they_tested the_new version, and_it_is more_stable_than the old one, and they_don't_expect bigger problems, and that the update_is necessary and a_good_idea and so on,_I'll happily agree
<siretart> same btw_for the other 2 members of_the uvf_team
<dolson> I_understand. I'm trying to find a google cache
<dolson> well, the only_thing I can say is that_I had some lockups_with the_old_one that the_interface_didn't respond._now, whether that was to do with_my kernel_or the app itself, I don't_know, I was messing_with_different patches and things
<dolson> other than_that, I haven't had any issues_with any version of seq24
<siretart>_dolson:_if_you hadn't bad issues with_the old version, how about leaving_the old one_dapper, and putting a newer on in_dapper-backports?
<dolson>_siretart: that's fine with me. I_don't_know how to get stuff into_backports,_but_I asked j