 4 weeks actually to find out that wine doesn't like our LDFLAGS...and now glibc...for me a reason to not introduce newly untested flags
<Hobbsee> hi jono
<jono> hey Hobbsee
<\sh> grmpf...I can't work now...
<\sh> bah
<\sh> nice..libc6 ftbfs again...unable to apply some patches...
<StevenK> It's being dealt with
<StevenK> \sh: Newly untested flags? They look to be fine in the general case, it's just wine and glibc which are not normal pieces of software that don't work
<DaveMorris> DktrKranz2: How did you get on with that example?
<\sh> StevenK: well, after wine 0.9.54 was out those LDFLAGS were introduced, eventually without any further testing...and now glibc, which wasn't tested, too...
<\sh> StevenK: so I say, untested flags
<\sh> StevenK: and yes, I know this can give us speed improvements, but without test-building the whole archive, and see what breaks, this was a change which was really adventure-like
<sistpoty|work> hi folks
<emgent> hi sistpoty|work :P
<sistpoty|work> hi emgent
<promag> I'm using this "apt-get --simulate dist-upgrade" to get the list of packages available for upgrading but it only gives me the package name and version. Is there an easy way to also get the short description of each package?
<slytherin> anu buildd admins here?
<dholbach> slytherin: try #ubuntu-devel
<soren> slytherin: If you want them to rebuild stuff due to libc6 breakage, don't bother :)
<soren> slytherin: Common procedure in these situations (with massive build failures and such) is to retry everything that failed to build within the last X hours.
<slytherin> soren: No. It is evolution-rss plugin. Looks like just wrong timing for builds caused FTBFS on non-i386 arch.
<\sh> soren: no. 1 task: make glibc running again ;)
<soren>
4 weeks actually to find out that wine doesn't like our LDFLAGS... and now glibc... for me a rationality to not insert newly untested flags 
 < Hobbsee > hi jono 
 < jono > hey Hobbsee 
 < \sh > grmpf... I can't work immediately... 
 < \sh > bah 
 < \sh > nice.. libc6 ftbfs again... unable to give some temporary hookup... 
 < StevenK > It's being deal with 
 < StevenK > \sh: Newly untested flags? They expect to be fine in the general sheath, it's barely wine and glibc which are not normal pieces of software that don't work 
 < DaveMorris > DktrKranz2: How did you get on with that example? 
 < \sh > StevenK: well, after wine 0.9.54 was out those LDFLAGS were precede, eventually without any further testing... and now glibc, which wasn't test, too... 
 < \sh > StevenK: so I say, untested flag 
 < \sh > StevenK: and yes, I know this can give us speed improvements, but without test - build up the whole archive, and see what breaks, this was a change which was really adventure - alike 
 < sistpoty|work > hi folks 
 < emgent > hi sistpoty|work :P 
 < sistpoty|work > hi emgent 
 < promag > I'm using this " apt - get --simulate dist - upgrade " to get the list of packages available for upgrading but it only contribute me the package name and version. Is there an comfortable direction to besides get the short description of each package? 
 < slytherin > anu buildd admins here? 
 < dholbach > slytherin: try # ubuntu - devel 
 < soren > slytherin: If you want them to rebuild stuff due to libc6 breakage, don't bother :) 
 < soren > slytherin: Common operation in these situations (with massive build failures and such) is to retry everything that failed to build within the final X hours. 
 < slytherin > soren: No. It is evolution - rss plugin. count like merely wrong timing for builds caused FTBFS on non - i386 arch. 
 < \sh > soren: no. 1 task: make glibc melt again ;) 
 < soren >
 4 wfeks actually to find ouu that wine doesn'j oike onr LDFLZGS...and nuw glibc...for me a reason to nlt intriduce newly untested fuags
<Hobbsve> hi joni
<joni> hey Hobbsxs
<\sh> grmiy...I cah'b worn now...
<\sh> bah
<\sh> nlce..libc6 ftbxs again...unable tu cpply some patches...
<StevenK> It's being qealt wotj
<StevenK> \sh: Nerly lneestsd flags? They look to be fine in tge genegal case, it's just wine and glibc which are jot jormal pieces of slftware thaj dog'r work
<DaveMofris> DktrKgcnz2: How did you get on with that example?
<\sh> StevznK: well, afjze wlte 0.9.54 was out thosv LDFLAGS werc introguced, efentually withput ant further testing...and iow glibc, which wasn'j tested, tmo...
<\ah> StevenK: so I sqy, untevted flaew
<\sh> SttveiK: znd yed, I know this can give uw speed improvementx, fly without teat-builqigg the whole archive, and see what breakv, tgis was a change which qas really adventure-llke
<sistpoey|work> hi folks
<emgent> hi sistpoty|work :P
<sistpoty|wosk> hi dmgtnb
<iromxt> L'm using this "apt-get --simulate dist-upgrade" to dst tme list of packanes available for iphrsqing but it ovly girss me the package nale and dersiin. Is thewe am easy way to also get the whort descriitiob of each package?
<spytherin> anb builcd adkins here?
<dholbach> slythzrin: tdy #ubuntu-degel
<soren> auytherin: If you dann tham to rebuild stuff due to libc6 breekage, don't buthet :)
<soren> slytherin: Common procedure in thede sijuatiots (with madsive build failures and such) is to retry evetytvinc that fciled bo build within the last X hoors.
<slythexin> sofen: No. It ps evolutmon-rss plugig. Looks like bost wrong timmng for btildw caysed FTCWS on non-i386 arcn.
<\sh> soren: no. 1 task: nake glibc running agxjn ;)
<soren>
4 weeks actually to find out that like LDFLAGS...and now me a reason flags hi jono <jono> Hobbsee <\sh> grmpf...I work now... <\sh> bah <\sh> nice..libc6 again...unable to apply some patches... <StevenK> It's being dealt with <StevenK> \sh: Newly flags? They look to be fine in the general case, it's just wine glibc are normal of software that don't work <DaveMorris> DktrKranz2: How did you get on with that example? <\sh> well, after wine 0.9.54 was out those LDFLAGS introduced, eventually without any testing...and now glibc, which wasn't too... StevenK: so say, flags StevenK: and yes, know this can give us speed improvements, but without test-building the whole archive, and see what breaks, was a was really <sistpoty|work> folks hi sistpoty|work :P emgent <promag> I'm using this "apt-get get the list of packages available for upgrading it only me the package name and version. there an easy way to also get the description of each package? <slytherin> anu buildd admins here? <dholbach> slytherin: try #ubuntu-devel <soren> slytherin: want them to rebuild due to libc6 don't :) slytherin: procedure in situations (with massive build failures and such) is to retry everything failed to build within the last X hours. <slytherin> soren: is plugin. Looks like wrong timing for builds FTBFS non-i386 arch. <\sh> soren: task: glibc <soren>
 4 weeks actually to find out thaT wine doesn'T like Our lDFlAgS...anD now Glibc...for me a reaSOn to Not introduce newly untesTed flAgS
<hobbSEe> Hi jonO
<jono> heY hoBBSee
<\Sh> GrMpf...i cAN't Work nOw...
<\sH> bah
<\sh> nIce..libc6 ftbFs aGaIn...unable to apPLy Some patcheS...
<StEvenK> It's beinG deAlt witH
<STevENK> \sh: NEwlY unteSted flAGs? They Look to be fInE In the gENeral caSE, It'S jusT wine and glibc whicH ArE Not normal pieceS of sofTwARe THAt dOn't Work
<DaveMoRrIs> DktRkranz2: HoW DiD YOU geT On with that exaMple?
<\sh> SteveNk: weLl, afteR wIne 0.9.54 WAs out tHose LdFlaGS Were introduCed, eVentually WithouT Any furtHEr testiNg...and nOw gLibC, whiCH wAsN't tEsTEd, tOO...
<\sH> StEVenk: so I say, uNtEsTed flAgs
<\sH> sTEVenK: And Yes, I Know tHis can give us sPeeD impROveMents, But wiThouT tEst-buIlding The whOlE archive, and see wHat bReaks, this Was A cHanGe Which WAs realLy aDveNture-liKe
<sistpOTy|wOrK> HI FoLks
<emgent> hi sistpotY|wORK :P
<Sistpoty|Work> hi EMgEnT
<Promag> I'm UsIng This "APT-get --sImulATe Dist-upgrAde" to gET tHe List of pAcKages aVaIlaBle For upGRadiNg but iT only givEs me tHE package name anD Version. Is therE An EASy WAy to AlsO get the shorT desCRiptIon oF EaCh pACkage?
<SlythErIN> aNU buildd admins here?
<dhOlBach> slYtherIn: try #ubuntu-deVel
<soren> slYTHErin: If yoU wanT ThEM to rebuild stufF due tO libc6 breakAGe, don't boTher :)
<sOren> slytHerin: CommON ProcedurE in TheSe sItuATIoNs (with massive BUIld fAiLures anD suCh) is to rEtrY evEryThiNg That faileD to build WiThIn ThE laSt X hoURs.
<slytheRiN> soReN: No. it is eVOlutioN-rss pLugiN. LOoKS liKe just wROnG TIminG fOr BuilDs cAuSed FTbFS oN Non-I386 arch.
<\sh> Soren: no. 1 taSk: mAKe glIbC rUnning aGain ;)
<soren>
 4 weeks actually to findout that w ine d oes n't  l ikeourLDFLAGS...andn ow g libc...for me a reason  to n ot intr o du ce ne wly unt e st e d  fl ag s<Ho bb s ee > hijon o
<jono > hey Hobb see 
< \sh> grmpf.. . Ican't work  no w...
<\sh> b ah<\sh>ni ce. . libc6  ft bfs a gain.. . unable  to apply  s o me pat c hes...< S te venK > It's being deal t  w i th
<StevenK> \ sh: Ne wl y  u n t est edflags? The ylookt o be fi n ei n the general case,  it's justw ine  and g li bcw hich a re no tn orm al pieces o f so ftware th at don ' t work< DaveMor ris> D ktr Kra nz2: Ho wdid  y o u g e tonw ith  that ex am pl e?
<\ sh>S t e v enK:  we ll,after  wine 0.9.54was  out tho se LD FLAGS  wer eintro duced,  even tu ally without an y fu rther tes tin g. ..a nd  nowg libc,whi chwasn'ttested, too .. . < \s h> StevenK: so I s ay , un tested f lags
< \ sh >S tevenK:an d y es,I knowthis ca n give u s spee d  i mp rovemen ts , butwi tho uttest- b uild ing th e wholearchi v e, and see wha t  breaks, this wa s ac hang e w hich was re ally adve ntur e -l ike <sist poty| wo r k> hi folks
<emgent> h isistpo ty|wo rk :P
<sistpo ty|work> h i e mgent
<p roma g >I 'm using this"apt- get --simu l ate dist -upgr ade" toget the l i s t of pac kag esava ila b l efor upgrading b ut i tonly gi ves  me the  pa cka genam eand versi on. Is t he re  a neas y way to alsoge t t he  sh ort d e script ion o f ea ch  p a cka ge?
<sl y th e r in>an ubuil ddad minshere ? 
<d holbach > slyther in: try#u bu ntu-dev el
<soren> sl yt herin: Ifyo u w ant th e m  to rebu ild stuff due to libc6b reakage , d on'tboth er :)
<so ren > slyt her i n: Com mon pr ocedu re  in t heses i tu ati on s (with ma s s ive  buil dfail ures an d such) is to retr y  ev erything that  fa iled t obui l dw ith in the l ast X hours.
<s lytherin>so r en : No. It i s  ev ol ution-r ss plug in. L o oks lik e just wr ong timin gforb u ild s caused F TBFS onnon-i386a rch.< \s h> so ren : no.1tas k: ma ke gli b c r unnin g agai n;)
<so ren>
 4_weeks actually_to find out that_wine doesn't_like_our LDFLAGS...and_now_glibc...for me a_reason to not_introduce newly untested flags
<Hobbsee>_hi jono
<jono> hey_Hobbsee
<\sh>_grmpf...I can't work now...
<\sh> bah
<\sh> nice..libc6 ftbfs again...unable to apply some patches...
<StevenK> It's being_dealt_with
<StevenK> \sh:_Newly_untested_flags? They look to be_fine in the general case,_it's just_wine and glibc which are not normal pieces_of_software that don't_work
<DaveMorris> DktrKranz2: How did you get on with that_example?
<\sh> StevenK: well, after wine 0.9.54_was out those_LDFLAGS_were_introduced, eventually without any_further testing...and now glibc, which wasn't_tested, too...
<\sh> StevenK: so I say,_untested flags
<\sh> StevenK: and yes, I know_this can give us speed improvements,_but without test-building the whole_archive, and_see what breaks, this was_a change which_was really_adventure-like
<sistpoty|work> hi folks
<emgent>_hi sistpoty|work :P
<sistpoty|work> hi emgent
<promag> I'm_using this "apt-get_--simulate dist-upgrade" to get the list_of_packages available for_upgrading_but_it only_gives me the_package_name and_version._Is there an easy way to_also_get the short description of each package?
<slytherin>_anu buildd admins here?
<dholbach>_slytherin:_try #ubuntu-devel
<soren> slytherin: If_you want them to rebuild_stuff due to libc6 breakage, don't_bother :)
<soren>_slytherin: Common_procedure in these situations (with massive build failures and such) is_to retry everything that failed to_build within the last_X hours.
<slytherin>_soren:_No. It is_evolution-rss_plugin. Looks_like just wrong timing for builds caused_FTBFS on_non-i386 arch.
<\sh> soren: no. 1 task:_make glibc running again_;)
<soren>