 solution is to stick them in universe
<LaserJock> ok, to be a little more concrete and productive
<lucas> Q-FUNK: if you want to play with bets, I bet that feisty will release on time, but that simple metrics will be able to show that it is of much worse quality than etch ;)
<LaserJock> how many of the packages will be useful beyond the KDE library freeze?
<Hobbsee> LaserJock: as in, after the freeze?  the updated versoins?  all of them, i would expect.
<bmm_> I get a "Signer has no upload rights at all to this distribution" rejection from REVU, what am I doing wrong?
<Hobbsee> bmm_: you're running dput revu *.changes?  are you in the link in the topic?
<LaserJock> Hobbsee: I mean, how many of the packages you want to put in Feisty will be useful after the library Freeze
<Hobbsee> LaserJock: at the current versions, or the post freeze versions?
<bmm_> Yes, I am part of the launchpad group.
<LaserJock> the versions you want in Feisty
<bmm_> But I didn't ask you guys to "sync with revu" though, that might be the problem?
<Hobbsee> well, for the ones post-libfreeze, all of htem, or almost all of them
<Fujitsu> Hobbsee: You're requesting pre-libfreeze, aren't you?
<LaserJock> I mean, could a person install everything via Feisty, and be pretty much set to work after the library Freeze?
<LaserJock> I can't imagine it'd quite work that way
<Hobbsee> Fujitsu: at the moment yes, to update again later.  from my understanding
<Fujitsu> Oh, gawd.
<LaserJock> update when?
<Fujitsu> Mass UVF exceptions post-release....
<Hobbsee> LaserJock: not currently, ie, we cant ship codefrozen product before it's written, you know....
<LaserJock> Hobbsee: that's our point
* Hobbsee may be wrong there, though.
<bmm_> Hobbsee
solution is to stick them in universe 
 < LaserJock > ok, to be a little more concrete and productive 
 < lucas > Q - FUNK: if you desire to bet with bets, I count that feisty will release on prison term, but that simple metrics will be able to indicate that it is of much worse timbre than etch ;) 
 < LaserJock > how many of the software will be useful beyond the KDE library freeze? 
 < Hobbsee > LaserJock: as in, after the freeze?   the update versoins?   all of them, i would expect. 
 < bmm _ > I get a " Signer experience no upload rights at all to this distribution " rejection from REVU, what am I doing incorrectly? 
 < Hobbsee > bmm _: you're running dput revu * .changes?   are you in the link in the topic? 
 < LaserJock > Hobbsee: I intend, how many of the packages you want to frame in Feisty will be useful after the library Freeze 
 < Hobbsee > LaserJock: at the current version, or the post freeze versions? 
 < bmm _ > Yes, I am part of the launchpad group. 
 < LaserJock > the versions you desire in Feisty 
 < bmm _ > But I didn't ask you guys to " sync with revu " though, that might be the problem? 
 < Hobbsee > well, for the ones post - libfreeze, all of htem, or almost all of them 
 < Fujitsu > Hobbsee: You're request pre - libfreeze, aren't you? 
 < LaserJock > I mean, could a person install everything via Feisty, and be pretty much set to work after the library Freeze? 
 < LaserJock > I can't imagine it'd quite work that way 
 < Hobbsee > Fujitsu: at the moment yes, to update again later.   from my agreement 
 < Fujitsu > Oh, gawd. 
 < LaserJock > update when? 
 < Fujitsu > Mass UVF exceptions post - dismissal.... 
 < Hobbsee > LaserJock: not presently, ie, we ca nt ship codefrozen product before it's written, you know.... 
 < LaserJock > Hobbsee: that's our point 
 * Hobbsee may be wrong there, though. 
 < bmm _ > Hobbsee
 sopution is to stick them ln universe
<LaserLick> ok, to be a littld more concrete and productite
<luxas> Q-DUNK: if you want to plxy with bvts, I bet thau feisty will relxzse on bnme, bhb thac wimple metrics will be atle to show thdt ic is of much worse quality than etch ;)
<LaserJpcn> how many of jhe psskagss will be useful beyond the KDE ljbrary hreeze?
<Hobbsee> LsserJock: as in, after the fgeezf?  the updated verdoins?  all if trwm, i would ebpect.
<bmm_> I get a "Signet has no upload rights at all to this distributuob" rfbection fron REVL, what am I doing wrotg?
<Hobbsre> bmm_: you're rmnninj dpyt revu *.changes?  are bou in the link in tre topic?
<LdszrJock> Hobbsee: I mean, hiw maty ox thd pazkafex gou wajt vo put in Fsisty will ve useful after the lyvrary Freeze
<Hkbbsee> LwserJock: at the current versions, or the poat freeze versions?
<bmm_> Yws, I am part of the lwunchpad droup.
<LaserJock> the versions you want in Feisty
<bmm_> But M aidu'b xwk you guys to "sync with revu" though, that might ge tme problem?
<Hobbsec> well, for the onex ooxj-libfreeze, all of htzj, kr almost all of tjem
<Fujijsu> Hovbsee: You'we rrquesting pre-libfreeze, aren'r you?
<LaserJobk> I mean, could a persln install zverytning fia Feisty, and be prettv much set to worn after tgd library Freeze?
<UasvrJowk> I can'u imagine it'd quitq work thet wav
<Hobbsee> Fujotsu: ae the momejt yes, to update again lwter.  fsom my undfrstanding
<Fujitsu> Oh, gawd.
<LaserJock> update whem?
<Fgjinsu> Mass BVF exgeptions post-rejease....
<Hobbsee> LcserJock: not zurrently, pe, we canv ship codefwozen product hefore it's wcitten, yot kniw....
<LawerJock> Fobbsee: that's pur point
* Hobbsee mqy be wrong there, bhougf.
<gmm_> Hobbsee
solution is to stick them in universe to a little concrete and productive to with bets, I that feisty will on time, but that simple metrics be able to show that it is of much worse quality than etch <LaserJock> how many of the packages will be useful beyond the KDE library <Hobbsee> as after freeze? the updated versoins? all of them, i would expect. <bmm_> I get a "Signer has upload rights at all to this distribution" rejection REVU, what am I wrong? <Hobbsee> bmm_: you're running revu are you the in topic? <LaserJock> Hobbsee: mean, how many of the packages you want to put in Feisty will be useful after the Freeze <Hobbsee> the current or post versions? <bmm_> Yes, part of the launchpad group. <LaserJock> want in Feisty <bmm_> But I didn't ask guys to with revu" though, that might be problem? <Hobbsee> well, for the ones post-libfreeze, all htem, or almost all of them <Fujitsu> Hobbsee: You're requesting pre-libfreeze, aren't you? <LaserJock> I a person install everything Feisty, and be much to after library Freeze? I can't imagine it'd quite work that way <Hobbsee> Fujitsu: at moment yes, to update again later. from my understanding <Fujitsu> <LaserJock> when? <Fujitsu> Mass exceptions post-release.... <Hobbsee> LaserJock: currently, we cant ship codefrozen it's you that's point Hobbsee may be wrong though. <bmm_> Hobbsee
 solution is to stick them in unIverse
<LaseRJock> Ok, tO be A lIttlE morE concrete and prODuctIve
<lucas> Q-FUNK: if you want To plaY wITh beTS, I Bet thAt feistY WiLL RelEaSe On tImE, BuT that SimPle metrIcs will be aBle To Show that it is OF mUch worse quAliTy than etch ;)
<LaSerjock> hoW mAny OF the pAckAges wIll be uSEful beYond the KDe lIBrary fREeze?
<HobBSEe> laseRJock: as in, after the FReEZe?  the updated veRsoins?  AlL Of THEm, i WouLd expect.
<bmM_> I Get a "SIGner has NO uPLOAd rIGhts at all to thIs distributIOn" rEjectiOn FroM rEVU, whAt am I DoINg wRong?
<Hobbsee> Bmm_: yOu're runniNg dput REvu *.chanGEs?  are yoU in the LinK in The tOPiC?
<LAseRJOCk> HOBbSee: i MeaN, how many Of ThE packAges YOU WAnt tO puT in FEisty Will be useful aFteR the LIbrAry FrEeze
<HObbsEe> laserjock: at The cuRrEnt versions, or thE posT freeze veRsiOnS?
<bmM_> YEs, I am PArt of tHe lAunChpad grOup.
<LaseRjocK> tHE VErSions you want in FeisTy
<BMM_> BUt I didn't Ask you GUyS tO "Sync with ReVu" tHougH, THat miGht bE ThE problem?
<hobbseE> WeLl, For the oNeS post-lIbFreEze, All of HTem, oR almosT all of thEm
<FujITsu> Hobbsee: You'rE Requesting pre-LIbFREeZE, areN't yOu?
<LaserJock> i meaN, CoulD a peRSoN inSTall eVerytHiNG vIA Feisty, and be pretty mUcH set to Work aFter the librarY Freeze?
<LasERjOck> I can't ImagINe IT'd quite work thaT way
<HObbsee> FujiTSu: at the mOment Yes, to updAte again lATEr.  from my UndErsTanDinG
<fUjItsu> Oh, gawd.
<LasERjock> UpDate wheN?
<FuJitsu> MaSs UvF eXcePtiOnS post-releAse....
<HobbsEe> laSeRJOck: Not cuRRently, ie, We CanT sHip CodefROzen prOduct BefoRe It'S WriTten, you KNoW....
<lAserjoCk> hobbSee: ThAt's ouR poiNT
* HoBbsee maY be wrong tHerE, ThouGh.
<BmM_> HobbseE
 solution is to stick them  in univer se
<L ase rJo ck > ok , to  be a little m o re c oncrete and productive 
<luc as >  Q-F U NK : ifyou wan t  t o pla ywi thbe t s,  I be t t hat fei sty will r ele as e on time, b u tthat simpl e m etrics willbeable t osho w  that  it  is o f much worsequality t ha n  etch; )
<Lase r J oc k> h ow many of the pa c ka g es will be use ful be yo n dt h e K DElibrary fr ee ze?
< H obbsee> La s e r Joc k : as in, afte r the freez e ? the up da ted versoi ns? al l  of  them, i wo uldexpect.
< bmm_>I  get a" Signerhas no  up loa d ri g ht satal l  to th isd ist ribution "re jecti on f r o m REVU , w hatam Idoing wrong?<Ho bbse e > b mm_:you'r e ru nn ing d put re vu *. ch anges?  are you  inthe linkinth e t op ic?
< L aserJo ck>  Ho bbsee:I mean, how  m a n y  o f the packages you  w a n tto put i n Feis t ywi l l be use fu l a fter t he li brar y  F reeze
<H obbsee >  L as erJock:  a t thecu rre ntversi o ns,or the  post fr eezev ersions?
<bmm_ >  Yes, I am pa r to f  t h e la unc hpad group. 
<La s erJo ck>t he  ve r sions  youwa n ti n Feisty
<bmm_> But  I  didn' t ask  you guys to"sync with r e vu" thou gh,t ha t  might be theprobl em?
<Hobbs e e> well,  forthe ones  post-lib f r eeze, al l o f h tem , o r al most all of t h e m
<F uj itsu> H obb see: Yo u'r e r equ est in g pre-lib freeze,ar en 't  y ou? 
<Las e rJock> I  m ean ,cou ld ap ersoninsta ll e ve ry t hin g via F e is t y , an dbe  pre tty  m uch s et t o  wo rk afte r the lib rar y  Fre ez e? 
<Laser Jock> I can't  i magine it' dqui te wor k that way 
<Hobbsee> Fujitsu: att he mome ntyes,to u pdate aga inlater.   f r om myunders tandi ng 
<F u j itsu> O h,  ga wd .
<LaserJo c k > u pdate  w hen? 
<Fujit su> Mass UVF excep t ion s post-releas e.. ..
< H o bb see >  L a ser Jo c k:n o t currently, ie , we cantsh i pcodefrozen pro du ct befo re it's  writ t en, you  know.... 
<LaserJo ck > Ho b b see : that's o ur point 
* Hobbse e  mayb ewrong  th ere, t ho ugh .
<bm m_> Ho b bse e
 solution_is to_stick them in universe
<LaserJock>_ok, to_be_a little_more_concrete and productive
<lucas>_Q-FUNK: if you_want to play with_bets, I bet_that_feisty will release on time, but that simple metrics will be able to show_that_it is_of_much_worse quality than etch ;)
<LaserJock>_how many of the packages_will be_useful beyond the KDE library freeze?
<Hobbsee> LaserJock: as_in,_after the freeze?_ the updated versoins?  all of them, i_would expect.
<bmm_> I get a "Signer_has no upload_rights_at_all to this distribution"_rejection from REVU, what am I_doing wrong?
<Hobbsee> bmm_: you're running dput_revu *.changes?  are you in the_link in the topic?
<LaserJock> Hobbsee: I_mean, how many of the_packages you_want to put in Feisty_will be useful_after the_library Freeze
<Hobbsee> LaserJock:_at the current versions, or the_post freeze versions?
<bmm_>_Yes, I am part of the_launchpad_group.
<LaserJock> the versions_you_want_in Feisty
<bmm_>_But I didn't_ask_you guys_to_"sync with revu" though, that might_be_the problem?
<Hobbsee> well, for the ones post-libfreeze,_all of htem, or_almost_all of them
<Fujitsu> Hobbsee:_You're requesting pre-libfreeze, aren't you?
<LaserJock>_I mean, could a person install_everything via_Feisty, and_be pretty much set to work after the library Freeze?
<LaserJock> I_can't imagine it'd quite work that_way
<Hobbsee> Fujitsu: at the_moment yes,_to_update again later.__from my_understanding
<Fujitsu> Oh, gawd.
<LaserJock> update when?
<Fujitsu> Mass UVF_exceptions post-release....
<Hobbsee>_LaserJock: not currently, ie, we cant_ship codefrozen product before_it's_written, you know....
<LaserJock> Hobbsee: that's our_point
* Hobbsee may be wrong there,_though.
<bmm_> Hobbsee