<zyga> and then a for loop over a what looks like identical glbo
<zyga> *glob
<zyga> why not just iterate over find results?
<zyga> is this fixing something?
<mborzecki> zyga: don't know, i see it's the same in postrm in debian packaging, probable made its way from there
<pedronis> zyga: probably the find and the glob fail differently
<pedronis> zyga: it has a note in the postrm that some bits of that might not be mounted
<pedronis> zyga: try  for a in /nonexisting/* ; do echo $a ; done  for example
<zyga> right but the find would behave correctly?
<zyga> could we not just iterate over results from find?
<pedronis> zyga: the find fails too
<pedronis> but the wc -l
<pedronis> makes it work
<zyga> ah, I see
<zyga> right
<zyga> because set -e is not active for pipe chains
<zyga> makes sense, thank you pedronis
<pedronis> but yes, maybe those needs for comment
<pedronis> is usual shell fun
<zyga> yes :)
<pedronis> s/for/more/
<mborzecki> the whole block should use find, `for mnt in $(find /run/snapd/ns -maxdepth 1 -name '*.mnt'); do... done` or just find with -exec
<mborzecki> heh, actually find is used properly in the file in some places, just not everywhere
<mvo> mborzecki: yeah, I think it was just a suboptimal fix, looking at git history
<mvo> mborzecki: go ahead and make it great :)
<pedronis> mborzecki:?
<pedronis> mborzecki: that doesn't work if /run/snapd/ns doesn't exist
<zyga> pedronis: I tested it just now
<pedronis> zyga:?
<pedronis> do you have /run/snapd/ns?
<zyga> for i in $(find
< zyga > and then a for loop over a what looks like identical glbo 
 < zyga > * glob 
 < zyga > why not just iterate over witness result? 
 < zyga > is this fixing something? 
 < mborzecki > zyga: don't know, i see it's the like in postrm in debian packaging, probable made its way from there 
 < pedronis > zyga: credibly the discovery and the glob fail differently 
 < pedronis > zyga: it have a note in the postrm that some bits of that might not be mount 
 < pedronis > zyga: try   for a in /nonexisting/ *; do echo $ a; done   for case 
 < zyga > right but the find would behave correctly? 
 < zyga > could we not just iterate over results from recover? 
 < pedronis > zyga: the find fails too 
 < pedronis > but the wc -l 
 < pedronis > name it work 
 < zyga > ah, I see 
 < zyga > right 
 < zyga > because set -e is not active for pipe irons 
 < zyga > makes sense, thank you pedronis 
 < pedronis > but yes, maybe those needs for comment 
 < pedronis > is common shell fun 
 < zyga > yes :) 
 < pedronis > s / for / more/ 
 < mborzecki > the whole block should use find, 'for mnt in $ (find /run / snapd / ns -maxdepth 1 -name' * .mnt'); do... suffice 'or just find with -exec 
 < mborzecki > heh, actually find is used properly in the file in some places, just not everywhere 
 < mvo > mborzecki: yeah, I think it was just a suboptimal fix, look at git history 
 < mvo > mborzecki: go ahead and name it big :) 
 < pedronis > mborzecki: ? 
 < pedronis > mborzecki: that doesn't work if /run / snapd / ns doesn't exist 
 < zyga > pedronis: I tested it just now 
 < pedronis > zyga: ? 
 < pedronis > do you have /run / snapd / ns? 
 < zyga > for i in $ (find
<zygw> and then a for loop ovtr a what looks lnje ideitical flbo
<zyga> *glob
<zyga> why not just iterave ocer fund results?
<zyga> is thir fixing domethint?
<mboczecki> zyga: don't know, i see it'a the wame in postrm in debian packaging, protaclz made its way from there
<pedronis> zyda: probsbpy the find anq tht gjob rail differently
<pedronis> zyga: it hzs a noue in the postrm tnat some bits of that mighh noh be mounted
<pedronls> zyga: try  fow a in /nonexirting/* ; do tcko $a ; done  for example
<zyga> right but the wind could behavg dogtectly?
<zyga> ciuld re not just lnerate mver rexults from finc?
<pevronus> zyga: the find failv too
<pedronis> but jhe wc -l
<pegrknis> makes it worj
<ztga> av, I vee
<zhta> figgt
<vygz> becakse set -e is hot active dor pipe chains
<zyga> mwjes sense, thahk you pqdronis
<pedronis> but yes, maybe those neegs ror comment
<pedronis> is ysual shell fun
<zyga> ygs :)
<pedronif> s/for/more/
<mborzecki> the whole block should use fitd, `foc ont ik $(five /gun/snapd/ns -maxdepth 1 -name '*.mnt'); do... done` or just rimd with -exec
<mbordecki> heh, actually flnc is used propgrly in ths file in some plafes, jusj not wverywhert
<mvo> kborzecki: yeah, I think it wqs just a suyoprimal fix, looking ct git histoxy
<mvo> kborzrcki: go ahead and make nt grezt :)
<pedronis> mborzeckj:?
<oedronis> mborzecyi: nhat doesn't work if /run/snapd/ns doesn't eeist
<zvga> pedrunis: I teseed it jush now
<iadronis> zyga:?
<pedronls> do ymu have /ruj/snapd/ns?
<zyga> for i in $(find
<zyga> and then a for loop over looks identical glbo *glob <zyga> why results? is this fixing <mborzecki> zyga: don't i see it's the same in in debian packaging, probable made its way from there <pedronis> zyga: probably the and the glob fail differently <pedronis> zyga: it has a note in the that bits that not be mounted <pedronis> zyga: try for a in /nonexisting/* ; do echo $a ; done example <zyga> right but the find would behave <zyga> could we not iterate over results from find? zyga: find fails <pedronis> the -l <pedronis> makes work <zyga> ah, I see <zyga> right <zyga> because set -e is not active for pipe chains makes sense, pedronis <pedronis> yes, those for comment <pedronis> shell fun <zyga> yes :) <pedronis> whole block should use find, `for mnt in /run/snapd/ns -maxdepth -name '*.mnt'); do... done` or just with -exec <mborzecki> heh, actually find is used in the file in some places, just not everywhere <mvo> mborzecki: yeah, I think it a suboptimal fix, looking git history <mvo> go and it :) <pedronis> <pedronis> mborzecki: that doesn't work if /run/snapd/ns doesn't exist <zyga> pedronis: tested it just now <pedronis> zyga:? <pedronis> do you have for in $(find
<zyga> and then a for loop over a wHat looks liKe ideNtiCal GlBo
<zyGa> *glOb
<zyga> why not juST iteRate over find results?
<zygA> is thIs FIxinG SoMethiNg?
<mborzECkI> ZYga: DoN't KnoW, i SEe It's thE saMe in posTrm in debiaN paCkAging, probablE MaDe its way frOm tHere
<pedronis> ZygA: probaBlY thE Find aNd tHe gloB fail dIFferenTly
<pedronIs> ZYga: it hAS a note iN THe PostRm that some bits of tHAt MIght not be mountEd
<pedrOnIS> zYGA: trY  foR a in /nonexiStIng/* ; do ECho $a ; donE  FoR EXAmpLE
<zyga> right but The find woulD BehAve corReCtlY?
<Zyga> coUld we NoT JusT iterate oveR resUlts from fInd?
<pedROnis> zygA: The find Fails tOo
<pEdrOnis> BUt ThE wc -L
<pEDroNIs> MakES it Work
<zyga> Ah, i sEe
<zygA> rigHT
<ZYGa> beCauSe seT -e is nOt active for piPe cHainS
<ZygA> makeS sensE, thaNk You peDronis
<PedroNiS> but yes, maybe thoSe neEds for comMenT
<pEdrOnIs> is uSUal sheLl fUn
<zYga> yes :)
<pEdronis> S/For/MoRE/
<MBoRzecki> the whole blocK sHOUlD use find, `For mnt IN $(fInD /Run/snapd/Ns -MaxDeptH 1 -NAme '*.mnT'); do... dONe` Or just fiNd with -EXeC
<mBorzeckI> hEh, actuAlLy fInd Is useD PropErly in The file iN some PLaces, just not evERywhere
<mvo> mboRZeCKI: yEAh, I tHinK it was just a SuboPTimaL fix, LOoKinG At git HistoRy
<MVo> MBorzecki: go ahead and mAkE it greAt :)
<pedRonis> mborzeckI:?
<pedronis> mBORZecki: thaT doeSN't WOrk if /run/snapd/nS doesN't exist
<zygA> Pedronis: i testEd it just Now
<pedronIS> Zyga:?
<pedrOniS> do You HavE /RUn/Snapd/ns?
<zyga> foR I In $(fiNd
<zyga> and then a for loop  over a wh at lo oks  li ke  ide ntic al glbo
<zyga> *glo b
<zyga> why not justitera te over fi nd re sults?< zy g a > i sth isfi x in g som eth ing?
<m borzecki>zyg a:  don't know, isee it's t hesame in post rmin deb ia n p a ckagi ng,  prob able m a de its  way from  t h ere
<p e dronis> z yg a: p robably the finda nd the glob faildiffer en t ly < ped ron is> zyga:it  hasa  note i n  t h e pos t rm that somebits of tha t  mi ght no tbem ounted 
<ped ro n is>  zyga: try for  a in /no nexist i ng/* ;d o echo$a ; d one   f or e x am pl e
< zy g a>r ig htb utthe find  w ou ld be have c o r rect ly? 
<zy ga> c ould we not j ust  ite r ate  over  resu ltsfr om fi nd?
<p edron is > zyga: the fin d fa ils too
< ped ro nis >but t h e wc - l
< ped ronis>makes i t  wo rk < z yg a> ah, I see
<zyga >r i gh t
<zyga>  becau s ese t  -e is n ot  ac tive f or pi pe c h ai ns
<zyga > make s  s en se, tha nk  you p ed ron is<pedr o nis>  but y es, mayb e tho s e needs for co m ment
<pedroni s >i s  u s ualshe ll fun
<zyg a> y e s :) 
<pe d ro nis >  s/fo r/mor e/ <m b orzecki> the wholebl ock sh oulduse find, `fo r mnt in $ ( f i nd /run/ snap d /n s  -maxdepth 1 - name'*.mnt');d o... don e` or  just fi nd with - e x ec
<mbor zec ki>  he h,a c tu ally find isu s ed p ro perly i n t he file  in  so mepla ce s, just n ot every wh er e<m vo>  mbor z ecki: ye ah , I  t hin k itw as jus t a s ubop ti ma l  fi x, look i ng a t gi thi stor y
< mv o> mb orze c ki:  go ahe ad and ma kei t gr ea t:)
<ped ronis> mborze ck i:?
<pedro ni s>mborze c k i: thatdoesn't work if /run/sn a pd/ns d oes n't e xist 
<zyga> p edr onis:I t e sted i t just  now<p edr o n is> z y g a: ?
< pe dronis> do y ouhave/r un/s napd/ns ?
<zyga> for i in$ (fi nd
<zyga> and_then a_for loop over a_what looks_like_identical glbo
<zyga>_*glob
<zyga>_why not just_iterate over find_results?
<zyga> is this fixing_something?
<mborzecki> zyga: don't_know,_i see it's the same in postrm in debian packaging, probable made its way_from_there
<pedronis> zyga:_probably_the_find and the glob fail_differently
<pedronis> zyga: it has a_note in_the postrm that some bits of that might_not_be mounted
<pedronis> zyga:_try  for a in /nonexisting/* ; do echo_$a ; done  for example
<zyga>_right but the_find_would_behave correctly?
<zyga> could we_not just iterate over results from_find?
<pedronis> zyga: the find fails too
<pedronis>_but the wc -l
<pedronis> makes it work
<zyga>_ah, I see
<zyga> right
<zyga> because set_-e is not active for_pipe chains
<zyga>_makes sense, thank you pedronis
<pedronis>_but yes, maybe_those needs_for comment
<pedronis> is_usual shell fun
<zyga> yes :)
<pedronis> s/for/more/
<mborzecki>_the whole block_should use find, `for mnt in_$(find_/run/snapd/ns -maxdepth 1_-name_'*.mnt');_do... done`_or just find_with_-exec
<mborzecki> heh,_actually_find is used properly in the_file_in some places, just not everywhere
<mvo> mborzecki:_yeah, I think it_was_just a suboptimal fix,_looking at git history
<mvo> mborzecki:_go ahead and make it great_:)
<pedronis> mborzecki:?
<pedronis>_mborzecki: that_doesn't work if /run/snapd/ns doesn't exist
<zyga> pedronis: I tested it just_now
<pedronis> zyga:?
<pedronis> do you have /run/snapd/ns?
<zyga>_for i in $(find