alling python-gnomekeyring is very much a workaround. The problem is that python-keyring needs to support this kind of thing better
<tumbleweed> it supports the use of an unencrypted(?) keyring without gnome / kde keyyrings, but only just
<EvilPhoenix> is there still a possibility of submitting something for review for the natty repos, or did they freeze adding additional packages to the repos?
<geser> EvilPhoenix: no new packages for natty as we are in FeatureFreeze
<EvilPhoenix> geser:  any possibility of submitting something for future inclusion?
<EvilPhoenix> or maybe submitting something for the lucid or maverick repos?
<ScottK> EvilPhoenix: If it's a package you're really interested in, you might try to get it into Debian and then it will automatically be in the next Ubuntu release.
<EvilPhoenix> ScottK:  yeah, Debian's packaging thing is evil, because everything's packaged for Ubuntu (from what I hear, Ubuntu packages aren't backwards-compatible with Debian's packages)
<EvilPhoenix> ScottK:  also, where would I start if i wanted to get it into debian?
<ScottK> EvilPhoenix: We're a derivative of Debian, so this is what you'd expect.
<EvilPhoenix> indeed
<ScottK> EvilPhoenix: Start at mentors.debian.net.
<geser> btw is the ApplicationReviewBoard running? didn't follow it
<ScottK> It is.  I believe they actually accepted one package.
<Laney> check extras.ubuntu.com
<acarpine> Hi omniscient people! I'm fixing several.desktop files of several packages
<acarpine> I believe I should submit my changes to the upstream projects, but what's the right process to do it?
<acarpine> 1) File a new bug in Ubuntu 2) Send a patch there 3) Forward the patch to debian
<acarpine> or 1) File a new bug in Debian 2) Send a patch there
<acarpine> and the wait the automatic sync to have the bug fixed in Ubuntu...
<ScottK> It depends on the severity of the issue.  If it's minor, I'd
alling python - gnomekeyring is very much a workaround. The problem is that python - keyring needs to support this kind of matter dependable 
 < tumbleweed > it supports the use of an unencrypted (?) keyring without gnome / kde keyyrings, but merely precisely 
 < EvilPhoenix > is there still a possibility of relegate something for review for the natty repos, or did they freeze adding extra software to the repos? 
 < geser > EvilPhoenix: no new software for natty as we are in FeatureFreeze 
 < EvilPhoenix > geser:   any possibility of submitting something for future inclusion body? 
 < EvilPhoenix > or maybe submitting something for the crystalline or maverick repos? 
 < ScottK > EvilPhoenix: If it's a package you're really concerned in, you might try to get it into Debian and then it will automatically be in the adjacent Ubuntu release. 
 < EvilPhoenix > ScottK:   yeah, Debian's packaging matter is evil, because everything's box for Ubuntu (from what I hear, Ubuntu packages aren't backwards - compatible with Debian's packages) 
 < EvilPhoenix > ScottK:   also, where would I start if i want to get it into debian? 
 < ScottK > EvilPhoenix: We're a derivative of Debian, so this is what you'd expect. 
 < EvilPhoenix > indeed 
 < ScottK > EvilPhoenix: Start at mentors.debian.net. 
 < geser > btw is the ApplicationReviewBoard running? didn't succeed it 
 < ScottK > It is.   I believe they actually accepted one package. 
 < Laney > check extras.ubuntu.com 
 < acarpine > Hi omniscient people! I'm fixing several.desktop files of several packages 
 < acarpine > I believe I should present my changes to the upstream projects, but what's the proper summons to do it? 
 < acarpine > 1) File a newfangled bug in Ubuntu 2) Send a patch there 3) Forward the patch to debian 
 < acarpine > or 1) charge a new bug in Debian 2) Send a patch there 
 < acarpine > and the wait the automatic sync to have the bug fixed in Ubuntu... 
 < ScottK > It depends on the severity of the issue.   If it's minor, I'd
alllng python-gnomekeyring ir very much a workarouid. The lroblem ks that python-keyring needs vo sypporu this kind of thine better
<tlmbleweed> it wypports thx use of an unskcrypcev(?) keyring withoot gnome / kda keyyrings, bud unpy just
<EvilPhoenix> is there still a possibollty of submittyng xjmetgpnn for review for the natty repos, or did they freeze sdding additional packages to hhe repos?
<geser> EvipPhoenix: no new packages for natty as we are in FeztureFreeze
<EvilPhoenix> geser:  avy poxsibility if suhkitting somxthing for future lmclusimn?
<EvilPnoenix> or maybc subkitring something for thx lucid or maverick tepos?
<ScottN> ZvilPhoenix: If it's a paxkage you'se rdqllh ihtxreated ij, yku might tdy to get ir into Debian and tneg it will autojaticajlr be in the next Ubuntu release.
<EvilPhoetix> ScottK:  yeah, Debian's pqckaging thing is evip, because everything's packaged for Ubuntu (from what I hear, Ubunvu paejages qrfn't backwards-compatible with Debian's packages)
<QbikPmoenix> ScottK:  ajso, where wpupd Y start if i danted to get it into debiaj?
<ScottK> EvilPhoenix: Wt're a derivative of Debian, so thus is what yjy'd expect.
<EvilPhoennx> indeed
<ScoctK> EvolPhornix: Start at mentors.deyian.nef.
<geser> btw ls the ApluicationReviewBoxrd rgnning? didn't follow it
<ScoteK> It is.  I bzlieve tfey sctualjy acceptef one package.
<Laney> check extrcs.ubuttu.com
<acaroine> Hi omniscient people! I'm fiemng several.dexkdop files oy seveval packages
<acawpine> I believg I shoulb submkt my chanfes to vhe upstream projects, but ahat's the rijht procefs ti do it?
<acarokne> 1) File a nee bug in Lbbntu 2) Sene a patch there 3) Fprwxdd the patch to devian
<acarpine> or 1) Fkle a nxw bud in Debian 2) Vend a ostch ghere
<acarpike> xnd yhe wait the automathc sgnc to have the bub nixed in Obuntu...
<ScoetK> It dependx on the severity lf thx issux.  If ot's minor, I'd
alling python-gnomekeyring is very much a workaround. is python-keyring needs support this kind supports use of an keyring without gnome kde keyyrings, but only just <EvilPhoenix> there still a possibility of submitting something for review for the natty repos, did they freeze adding additional packages to the repos? <geser> EvilPhoenix: no new for as are FeatureFreeze <EvilPhoenix> geser: any possibility of submitting something for future inclusion? <EvilPhoenix> or maybe submitting something the lucid or maverick repos? <ScottK> EvilPhoenix: If a package you're really in, you might try to it Debian and it automatically in the next release. <EvilPhoenix> ScottK: yeah, Debian's packaging thing is evil, because everything's packaged for Ubuntu (from what I Ubuntu packages with Debian's <EvilPhoenix> also, would I start wanted to get it into debian? a derivative of Debian, so this is what expect. <EvilPhoenix> <ScottK> EvilPhoenix: Start at mentors.debian.net. <geser> is the ApplicationReviewBoard running? didn't follow it <ScottK> is. I believe they actually accepted one package. <Laney> check extras.ubuntu.com <acarpine> Hi omniscient people! several.desktop files of several <acarpine> I believe should my to upstream projects, what's the right process to do it? <acarpine> 1) File a bug in Ubuntu 2) Send a patch there 3) Forward to <acarpine> or 1) a new bug in 2) a patch there <acarpine> wait automatic the fixed Ubuntu... <ScottK> It depends the severity of the issue. it's minor, I'd
alling python-gnomekeyring iS very much a WorkaRouNd. THe ProbLem iS that python-keyRIng nEeds to support this kind oF thinG bETter
<TUmBleweEd> it supPOrTS The UsE oF an UnENcRypteD(?) keYring wiThout gnome / Kde KeYyrings, but onLY jUst
<EvilPhoEniX> is there stilL a pOssibiLiTy oF SubmiTtiNg somEthing FOr reviEw for the nAtTY repos, OR did theY FReEze aDding additional paCKaGEs to the repos?
<geSer> EviLPHOeNIX: no New Packages foR nAtty aS We are in fEaTUREFrEEze
<EvilPhoeniX> geser:  any poSSibIlity oF sUbmITting sOmethInG For Future incluSion?
<evilPhoenIx> or maYBe submiTTing somEthing For The LuciD Or MaVerIcK RepOS?
<SCotTk> EvIlPhoeniX: IF iT's a paCkagE YOU'Re reAllY intErestEd in, you might tRy tO get IT inTo DebIan anD theN iT will AutomaTicalLy Be in the next UbunTu reLease.
<EvilphoEnIx> SCoTtK:  yeAH, DebiaN's pAckAging thIng is evIL, beCaUSE EvErything's packaged fOr uBUnTu (from whAt I heaR, ubUnTU packageS aRen'T bacKWArds-cOmpaTIbLe with DeBian's pACkAgEs)
<EvilPHoEnix> ScOtTK:  aLso, Where WOuld i start If i wanteD to geT It into debian?
<ScOTtK> EvilPhoeniX: we'RE A dERivaTivE of Debian, so This IS whaT you'D ExPecT.
<evilPHoeniX> iNDeED
<ScottK> EvilPhoenix: STaRt at meNtors.Debian.net.
<geseR> btw is the APPLIcationREvieWboARd running? didn't FolloW it
<ScottK> IT Is.  I belieVe theY actuallY accepted ONE package.
<lanEy> cHecK exTRAs.Ubuntu.com
<acarPINe> Hi OmNiscienT peOple! I'm fIxiNg sEveRal.DeSktop fileS of severAl PaCkAgEs
<aCarpiNE> I believE I ShoUlD suBmit mY ChangeS to thE upsTrEaM ProJects, buT WhAT'S the RiGhT proCesS tO do it?
<AcarPIne> 1) file a neW bug in UbuNtu 2) sEnd a PaTcH there 3) FOrward the patcH tO debian
<acaRpIne> Or 1) File A NEw bug in DEbian 2) Send a patch there
<acaRPine> and The Wait tHe auTomatic syNc tO have tHe bUG fixed In UbunTu...
<ScoTtk> It DEPends ON ThE seVeRity of the iSSUe.  IF it's mInOr, I'd
alling python-gnomekeyring  is very m uch a  wo rka ro und.  The  problem is th a t py thon-keyring needs tosuppo rt this ki nd of  thingb et t e r
< tu mb lew ee d >it su ppo rts the  use of an  un en crypted(?) k e yr ing withou t g nome / kde k eyy rings,  b uto nly j ust 
<Evi lPhoen i x> isthere sti ll a poss i bilityo f  s ubmi tting something f o rr eview for thenattyre p os , ordid  they free ze  addi n g addit i on a l pac k ages to the r epos?
<gese r > E vilPho en ix: no new  pack ag e s f or natty as  weare in Fe atureF r eeze
<E v ilPhoen ix> ge ser : anyp os si bil it y  of su bmi t tin g someth in gfor f utur e i n clus ion ?
<E vilPh oenix> or may besubm i tti ng so methi ng f or  thelucidor ma ve rick repos?
<Sc ottK > EvilPho eni x:  If  i t's a packag e y ou' re real ly inte r est ed i n ,you might try to g et i tinto Deb ian an d  t he n  it will  a uto mati c a lly b e in th e next U buntur el ea se.
<Ev il Phoeni x>  Sc ott K:  y e ah,Debian 's packa gingt hing is evil,b ecause everyt h in g ' sp acka ged  for Ubuntu  (fr o m wh at I he ar, Ubunt u pac ka g es aren't backwards-co mp atible  with  Debian's pac kages)
<Ev i l P hoenix>Scot t K:  also, where w ouldI start if i wanted  to g et it in to debian ? <ScottK>  Ev ilP hoe nix : We 're a derivat i v e of  D ebian,sothis is  wh atyou 'dex pect.
<Ev ilPhoeni x>  i nd ee d
< Scott K > EvilPh oe nix :Sta rt at mentor s.deb ian. ne t. <ge ser> bt w  i s theAp pl icat ion Re viewB oard run ning? d idn't fol low it
< Sc ot tK> Itis.  I believ ethey actua ll y a ccepte d one pack age.
<Laney> check extr a s.ubunt u.c om
<a carp ine> Hi o mni scient  pe o ple! I 'm fix ing s ev era l . deskt o p  f ile sof several p ack ages<a carp ine> Ibelieve I should s u bmi t my changestotheu p st rea m  p r oje ct s , b u t  what's the rig ht process  t o  d o it?
<aca r pin e>  1) Fil e a new  bugi n Ubunt u 2) Send  a patchth ere3 )  Fo rward thepatch to  debian
< a carpi n e>  or 1 ) F ile ane w b ug in  Debia n  2)  Send  a pat ch  there 
<aca rp ine> and  the wait the automatic  syncto ha vethe bug f ixe d  in  Ubuntu.. .
<S cottK> Itdep end s onthe sever ityo fthe issue .  I f  it's min o r,  I' d 
alling python-gnomekeyring_is very_much a workaround. The_problem is_that_python-keyring needs_to_support this kind_of thing better
<tumbleweed>_it supports the use_of an unencrypted(?)_keyring_without gnome / kde keyyrings, but only just
<EvilPhoenix> is there still a possibility of_submitting_something for_review_for_the natty repos, or did_they freeze adding additional packages_to the_repos?
<geser> EvilPhoenix: no new packages for natty as_we_are in FeatureFreeze
<EvilPhoenix>_geser:  any possibility of submitting something for future_inclusion?
<EvilPhoenix> or maybe submitting something for_the lucid or_maverick_repos?
<ScottK>_EvilPhoenix: If it's a_package you're really interested in, you_might try to get it into_Debian and then it will automatically be_in the next Ubuntu release.
<EvilPhoenix> ScottK:_ yeah, Debian's packaging thing_is evil,_because everything's packaged for Ubuntu_(from what I_hear, Ubuntu_packages aren't backwards-compatible_with Debian's packages)
<EvilPhoenix> ScottK:  also,_where would I_start if i wanted to get_it_into debian?
<ScottK> EvilPhoenix:_We're_a_derivative of_Debian, so this_is_what you'd_expect.
<EvilPhoenix>_indeed
<ScottK> EvilPhoenix: Start at mentors.debian.net.
<geser> btw_is_the ApplicationReviewBoard running? didn't follow it
<ScottK> It_is.  I believe_they_actually accepted one package.
<Laney>_check extras.ubuntu.com
<acarpine> Hi omniscient people!_I'm fixing several.desktop files of several_packages
<acarpine> I_believe I_should submit my changes to the upstream projects, but what's the_right process to do it?
<acarpine> 1)_File a new bug_in Ubuntu_2)_Send a patch_there_3) Forward_the patch to debian
<acarpine> or 1) File_a new_bug in Debian 2) Send a_patch there
<acarpine> and the_wait_the automatic sync to have the_bug fixed in Ubuntu...
<ScottK> It depends_on the severity of the_issue.__If it's minor, I'd