<LaserJock> Hobbsee: ok, but that seems to be his/Kubuntu's issue
<Fujitsu> Create a KDE4 repo/component, then.
<LaserJock> I just think we can come up with a better solution
<LaserJock> I mean, Universe does solve the immediate issue of upload access and archs
<LaserJock> but then you have to stick to Universe schedules
<LaserJock> which sucks in this case
<LaserJock> if I had anything but i386 I'd offer to help
<LaserJock> if I had enough bandwidth I'd offer to host a repo
<StevenK> I have amd64, and have (privately) offered to help.
<LaserJock> it's certainly that I don't care about Kubuntu or KDE
<LaserJock> *not
<LaserJock> sorry ;-)
* StevenK quotes LaserJock out of context.
<LaserJock> darn it
<bmm_> Hobbsee: sorry to have to ask, but I can't find how to "add revu" to the changelog like: should it be "feisty-revu; urgency=low"?
<LaserJock> no
<StevenK> bmm_: Not the changelog, the dput command line
<LaserJock> bmm_: it should just be feisty
<Hobbsee> bmm_: use dput revu *.changes
<LaserJock> bmm_: dput revu <path to >_source.changes
<LaserJock> Hobbsee: not *.change, _source.changes :-)
<Hobbsee> rm the.upload file, and it'll stop telling you it's already uploaded
<bmm_> Ah, doing that now. Thank!
<Hobbsee> LaserJock: good point.
<LaserJock> Hobbsee: I always forget that too
<LaserJock> I'm so used to just having source.changes
<Hobbsee> LaserJock: well, as long as you dont build binaries without the pbuilder, it never comes up
<LaserJock> until I started cleaning out all the i386.changes out of incoming :-)
<LaserJock> Hobbsee: exactly

< LaserJock > Hobbsee: ok, but that seems to be his / Kubuntu's issue 
 < Fujitsu > Create a KDE4 repo / component, then. 
 < LaserJock > I barely remember we can come up with a better solution 
 < LaserJock > I mean, Universe does clear the immediate issue of upload entree and archs 
 < LaserJock > but then you have to stick to Universe agenda 
 < LaserJock > which sucks in this case 
 < LaserJock > if I suffer anything but i386 I'd offer to serve 
 < LaserJock > if I experience enough bandwidth I'd offer to host a repo 
 < StevenK > I have amd64, and have (privately) offer to help. 
 < LaserJock > it's certainly that I don't care about Kubuntu or KDE 
 < LaserJock > * not 
 < LaserJock > blue ;-) 
 * StevenK quotes LaserJock out of context. 
 < LaserJock > darn it 
 < bmm _ > Hobbsee: sorry to have to ask, but I can't detect how to " add revu " to the changelog like: should it be " feisty - revu; urgency = low "? 
 < LaserJock > no 
 < StevenK > bmm _: Not the changelog, the dput instruction line 
 < LaserJock > bmm _: it should just be feisty 
 < Hobbsee > bmm _: use dput revu * .changes 
 < LaserJock > bmm _: dput revu < path to > _ source.changes 
 < LaserJock > Hobbsee: not * .change, _ source.changes :-) 
 < Hobbsee > rm the.upload file, and it'll stop tell you it's already uploaded 
 < bmm _ > Ah, doing that now. Thank! 
 < Hobbsee > LaserJock: good point. 
 < LaserJock > Hobbsee: I always forget that too 
 < LaserJock > I'm so used to just have source.changes 
 < Hobbsee > LaserJock: well, as long as you do nt build binaries without the pbuilder, it never do up 
 < LaserJock > until I started cleaning out all the i386.changes out of incoming :-) 
 < LaserJock > Hobbsee: exactly
<LasfrJock> Hobbsee: ok, but thxt seems to be kus/Kubuitu's isaue
<Fujitru> Create a KDE4 repo/componenv, thwn.
<LastgJock> I just think we can come up with a bttter solution
<LasxdJock> I mean, Hkivervx does solve thg immediate hssue of uploag xceess and archs
<LaserJock> but then you have tp dtick to Univetse sbhqdulss
<LaserJock> which sucks in this caae
<LaserOock> if I had amything but i386 I'd offer to jelp
<PaserJock> if I had enough banewidey I'd offer tu host a rtpm
<StevenK> I have amd64, and have (privately) ofwered to help.
<LaweeJofn> it's certamnly trat I don't care aboud Kubunyu or KDE
<LaserMock> *iot
<LqserJock> sorry ;-)
* SteveiK quotes LaserJock jut of cottzxt.
<LaserJock> darn it
<bnm_> Hobbvee: vorrh to habe tk ask, hut I can't fihd how to "aed revu" to the chanbejig like: shouls it bq "seisty-revu; urgency=low"?
<LaserJock> no
<StevenN> bjm_: Not the changelog, thw dput command line
<LaderJock> bim_: it should just be feisty
<Hobbsee> bmm_: use dput ravu *.ciavgew
<LwrwrUock> bmm_: dput revu <path to >_source.changes
<LaserTkcl> Mobbsee: not *.channe, _source.changes :-)
<Hpbhsrg> rm the.upload file, chd it'll stop telling you it'f alrwady uplowded
<nmm_> Ah, doing that now. Thank!
<Yobbsee> LasegJocj: good point.
<LaserJlck> Hobbsee: I akways forget that too
<LaserJoek> I'm ao used to uust havihe source.changes
<Hubbxea> LaserJock: well, as long af you donv buikd binafies withott the pbullder, it never comes up
<LwserJlcn> until I dtarted cleaning out all the i386.cienges out of onwompng :-)
<LaserLock> Hpbbsee: exactlr

<LaserJock> Hobbsee: ok, but that seems to issue Create a repo/component, then. <LaserJock> come with a better <LaserJock> I mean, does solve the immediate issue of access and archs <LaserJock> but then you have to stick to Universe schedules which sucks in this case <LaserJock> if I had anything but i386 I'd to <LaserJock> I enough bandwidth I'd offer to host a repo <StevenK> I have amd64, and have (privately) offered help. <LaserJock> it's certainly that I don't care Kubuntu or KDE <LaserJock> <LaserJock> sorry ;-) * StevenK LaserJock of context. darn <bmm_> sorry to have ask, but I can't find how to "add revu" to the changelog like: should it be "feisty-revu; <LaserJock> no Not the the command <LaserJock> bmm_: it be feisty <Hobbsee> bmm_: use dput bmm_: dput revu <path to >_source.changes <LaserJock> Hobbsee: *.change, _source.changes <Hobbsee> rm the.upload file, and it'll telling you it's already uploaded <bmm_> Ah, doing now. Thank! <Hobbsee> LaserJock: good point. <LaserJock> Hobbsee: I always forget that too <LaserJock> I'm to just having source.changes LaserJock: well, as as dont binaries the pbuilder, never comes up <LaserJock> until I started cleaning out all the out of incoming :-) <LaserJock> Hobbsee: exactly
<LaserJock> Hobbsee: ok, but that Seems to be hIs/KubUntU's iSsUe
<FuJitsU> Create a KDE4 repO/CompOnent, then.
<LaserJock> I jusT thinK wE Can cOMe Up witH a betteR SoLUTioN
<LAsErJOcK> i mEan, UnIveRse does Solve the imMedIaTe issue of uplOAd Access and aRchS
<LaserJock> buT thEn you hAvE to STick tO UnIversE schedULes
<LasErJock> whiCh SUcks in THis case
<lASeRJocK> if I had anything buT I386 I'D Offer to help
<LasErJock> If i HaD ENouGh bAndwidth I'd OfFer to HOst a repO
<stEVENK> I HAve amd64, and have (Privately) ofFEreD to helP.
<LAseRjock> it'S certAiNLy tHat I don't carE aboUt Kubuntu Or KDE
<LASerJock> *NOt
<Laserjock> soRry ;-)
* steVenK QUoTeS LaSeRjocK OuT of COntExt.
<LaserjoCk> Darn iT
<bmm_> hOBBSee: sOrrY to hAve to Ask, but I can't fiNd hOw to "ADd rEvu" to The chAngeLoG like: Should It be "fEiSty-revu; urgency=lOw"?
<LaSerJock> no
<steVeNK> bMm_: not thE ChangeLog, The Dput comMand linE
<lasErjOCK> bMm_: it should just be feIsTY
<hoBbsee> bmm_: Use dpuT ReVu *.CHanges
<LaSeRJoCk> bmM_: DPut reVu <paTH tO >_source.cHanges
<lAsErjock> HobBsEe: not *.cHaNge, _SouRce.chANges :-)
<hobbseE> rm the.upLoad fILe, and it'll stop tELling you it's alREaDY UpLOadeD
<bmM_> Ah, doing thaT now. tHank!
<hobbSEe> lasERJock: Good pOiNT.
<LASerJock> Hobbsee: I alwaYs Forget That tOo
<LaserJock> I'm So used to juST HAving souRce.cHAnGEs
<Hobbsee> Laserjock: wEll, as long aS You dont bUild bInaries wIthout the PBUilder, it NevEr cOmeS up
<lASeRJock> until I stARTed cLeAning ouT alL the i386.chAngEs oUt oF inCoMing :-)
<Laserjock> HobbSeE: eXaCtLy

<LaserJock> Hobbsee: ok, b ut that se ems t o b e h is /Kub untu 's issue
<Fuji t su>Create a KDE4 repo/com ponen t, then . 
< Laser Jock> I ju s t  th in kweca n  c ome u p w ith a b etter solu tio n<LaserJock>I  m ean, Unive rse  does solvethe  immed ia tei ssueofuploa d acce s s andarchs
<La se r Jock>b ut then y ou  hav e to stick to Uni v er s e schedules
<L aserJo ck >  w h i chsuc ks in this  c ase
< L aserJoc k >i f I h a d anything bu t i386 I'do ffe r to h el p
< L aserJo ck> i fI  ha d enough ba ndwi dth I'd o ffer t o  host a repo
<S tevenK > I  ha ve a m d6 4,  an dh ave (p riv a tel y) offer ed  t o hel p.
< L a s e rJoc k>it's  cert ainly that Idon 't c a reabout  Kubu ntuor  KDE<Laser Jock>  * not
<LaserJock>  sor ry ;-)
*Ste ve nKqu otesL aserJo ckout  of con text.
< L ase rJ o c k >darn it
<bmm_> Hob bs e e :sorry to  havet oas k , but Ica n't  fin d how t o "a d drevu" to  the c h an ge log lik e:  shoul ditbe"feis t y-re vu; ur gency=lo w"?
< L aserJock> no
< S tevenK> bmm_: No t th e  cha nge log, the dp ut c o mman d li n e<La s erJoc k> bm m_ :  i t  should just be fei st y
<Hob bsee>  bmm_: use dp ut revu *. c h a nges
<La serJ o ck >  bmm_: dput re vu <p ath to >_s o urce.cha nges<LaserJo ck> Hobbs e e : not *. cha nge , _ sou r c e. changes :-)
< H o bbse e>  rm the .up load fi le,  an d i t'l lstop tell ing youit 's  a lr ead y upl o aded
<bm m_ > A h,  do ing t h at now . Tha nk!<H ob b see > Laser J oc k :  goo dpo int. 
<L as erJoc k> H o bbs ee: I a lways for get that  t oo 
<Laser Jock> I'm sous ed to just  h avi ng sou r c e.change s
<Hobbsee> LaserJock:w ell, as  lo ng as  you  dont bui ldbinari esw ithout  the p build er , i t never c om esup 
<LaserJoc k >  un til I  s tart ed clea ning out all the i 3 86. changes out o f i ncom i n g:-) <L a ser Jo c k>H o bbsee: exactly
<LaserJock> Hobbsee:_ok, but_that seems to be_his/Kubuntu's issue
<Fujitsu>_Create_a KDE4_repo/component,_then.
<LaserJock> I just_think we can_come up with a_better solution
<LaserJock> I_mean,_Universe does solve the immediate issue of upload access and archs
<LaserJock> but then you_have_to stick_to_Universe_schedules
<LaserJock> which sucks in this_case
<LaserJock> if I had anything_but i386_I'd offer to help
<LaserJock> if I had enough_bandwidth_I'd offer to_host a repo
<StevenK> I have amd64, and have (privately)_offered to help.
<LaserJock> it's certainly that_I don't care_about_Kubuntu_or KDE
<LaserJock> *not
<LaserJock> sorry_;-)
* StevenK quotes LaserJock out of_context.
<LaserJock> darn it
<bmm_> Hobbsee: sorry to_have to ask, but I can't find_how to "add revu" to the_changelog like: should it be_"feisty-revu; urgency=low"?
<LaserJock>_no
<StevenK> bmm_: Not the changelog,_the dput command_line
<LaserJock> bmm_:_it should just_be feisty
<Hobbsee> bmm_: use dput revu_*.changes
<LaserJock> bmm_: dput_revu <path to >_source.changes
<LaserJock> Hobbsee: not_*.change,__source.changes :-)
<Hobbsee> rm_the.upload_file,_and it'll_stop telling you_it's_already uploaded
<bmm_>_Ah,_doing that now. Thank!
<Hobbsee> LaserJock: good_point.
<LaserJock>_Hobbsee: I always forget that too
<LaserJock> I'm_so used to just_having_source.changes
<Hobbsee> LaserJock: well, as_long as you dont build_binaries without the pbuilder, it never_comes up
<LaserJock>_until I_started cleaning out all the i386.changes out of incoming :-)
<LaserJock> Hobbsee:_exactly
