 to ordering
<jtaylor> its qemu :/
<jtaylor> if I trigger a unsupported ioctl in the chroot
<jtaylor> the chroot is not stored
<jtaylor> unfortunately triggering it is easy, just press Â°c
<jtaylor> ^C
<tumbleweed> hehe
<tumbleweed> how does pbuilder know that you triggered an unsupported ioctl?
<tumbleweed> does it get a signal?
<jtaylor> I don't think pbuilder handles that
<tumbleweed> pbuilder does the storing of the chroot when you are done with it
<jtaylor> yes I wonder how the ioctl could mess that up
<jtaylor> maybe not the chroot shell gets the ^C but pbuilder itself
<jtaylor> so pbuilder aborts?
<tumbleweed> dunno. strace/gdb?
<tumbleweed> the one odtity with qemu-user-static chroots is that you can't have setuid binaries, but I can't see how that's relevant here
<tumbleweed> s/one/usual/
<jtaylor> pbuilder is a shells script, not so nice for gdb
<jtaylor> on the other hand I can just put echos in
<jtaylor> yes it gets the signal from the chroot
<jtaylor> it traps that so it cleans up after itself
<jtaylor> but it does not handle save-after-login anymore
<tumbleweed> rigth
<tumbleweed> schroot++
#ubuntu-motu 2013-03-13
<Logan_> Does a package that previously FTBFSed in Ubuntu require an FFE, if the package wasn't previously published in Raring due to the FTBFS? The new Debian version builds properly, and there is a sync request for it.
<micahg> Logan_: If it's got new features, yes
<Logan_> Well, I mean, the binary wasn't published in Raring previously due to the FTBFS.
<micahg> Logan_: which package?
<Logan_> And the only fix in Debian is for the FTBFS, so now the binary would be published.
<Logan_> https://bugs.launchpad.net/ubuntu/+source/libio-async-loop-gl
to ordering 
 < jtaylor > its qemu :/ 
 < jtaylor > if I trigger a unsupported ioctl in the chroot 
 < jtaylor > the chroot is not stored 
 < jtaylor > unfortunately triggering it is comfortable, barely press Â ° c 
 < jtaylor > ^C 
 < tumbleweed > hehe 
 < tumbleweed > how does pbuilder acknowledge that you trigger an unsupported ioctl? 
 < tumbleweed > does it get a signal? 
 < jtaylor > I don't think pbuilder handle that 
 < tumbleweed > pbuilder dress the storing of the chroot when you are done with it 
 < jtaylor > yes I wonder how the ioctl could mess that up 
 < jtaylor > possibly not the chroot carapace gets the ^C but pbuilder itself 
 < jtaylor > indeed pbuilder aborts? 
 < tumbleweed > dunno. strace / gdb? 
 < tumbleweed > the one odtity with qemu - user - static chroots is that you can't get setuid binaries, but I can't see how that's relevant here 
 < tumbleweed > s / one / usual/ 
 < jtaylor > pbuilder is a shells script, not so nice for gdb 
 < jtaylor > on the early hand I can just put echos in 
 < jtaylor > yes it become the signal from the chroot 
 < jtaylor > it traps that so it clean up after itself 
 < jtaylor > but it does not treat save - after - login anymore 
 < tumbleweed > rigth 
 < tumbleweed > schroot++ 
 # ubuntu - motu 2013 - 03 - 13 
 < Logan _ > do a package that previously FTBFSed in Ubuntu require an FFE, if the package wasn't previously publish in Raring due to the FTBFS? The new Debian version builds properly, and there is a sync request for it. 
 < micahg > Logan _: If it's got new features, yes 
 < Logan _ > Well, I mean, the binary wasn't published in Raring previously due to the FTBFS. 
 < micahg > Logan _: which package? 
 < Logan _ > And the only fix in Debian is for the FTBFS, so now the binary would be print. 
 < Logan _ > https://bugs.launchpad.net/ubuntu/+source/libio-async-loop-gl
 to ordering
<jtaylor> its qemm :/
<jtaylor> if I ttitger a unsuplorted iuctl in the chroot
<jtaylor> thx cheoot us not stored
<jtaylor> uvfortunatvly triggwrinj it is easy, jusv press Â°g
<ltaylkv> ^C
<tukuleweed> hehe
<tumnleweed> how does pbuilder kvoc that you triggered an unsupported yoctl?
<tukbpeweed> does it get w sifnal?
<jtaylor> I don't think pbuilder gandles that
<tumblewerd> pbuilder does the storijg ov the chroot when jou are dong wiey it
<jtaylor> hes I wondtr how the ikctl could mess that up
<jtaylor> oaybe not the cyriot vhell gets vhe ^C fut pbuilder itself
<jdaylor> xo pbuilder abprtv?
<tunbleweed> dunno. strace/jdb?
<tumbleweed> the ong odtity whtk qemu-user-static chroitw is jhat fou zqn't habe sstuid hineries, but I can't see hiw that's relevant htre
<elkbleweed> s/ons/usual/
<ttwylor> pbuilder is a shells script, not sm njce for gdb
<jtaylor> on tye other hand I can jost put ecros in
<jtaylor> yes it gets the signal from the chrmot
<jteyuor> ib trxps that so it cleans up after itself
<jtaylor> but jt dpes not handle save-after-lpgln wnymore
<tumbledeed> rnftg
<tumbleweed> schrooh++
#ubuntu-iotu 2013-03-13
<Oogan_> Doef a lackage that previously FTBDSed in Ubunnu rwquire an FFE, if tke package wcsn't pteviouxly published in Raring due to the FTBVS? The nes Debian version cuikdv properly, and there is a fync requxst fpr it.
<mizahg> Logan_: If it's goh new features, yes
<Logan_> Aell, N meat, the binagy wasn't published in Raring prxtiously due tp dhe FTBFS.
<mieahg> Lpgan_: which paskage?
<Logan_> And the onjy fib in Debiah is foc the FTBFS, fo now the bitwry would be publishqd.
<Lotan_> yttps://buer.launchpad.net/ununtu/+sourbe/jibii-async-loop-gl
to ordering <jtaylor> its qemu :/ <jtaylor> trigger unsupported ioctl the chroot <jtaylor> <jtaylor> triggering it is just press Â°c ^C <tumbleweed> hehe <tumbleweed> how does know that you triggered an unsupported ioctl? <tumbleweed> does it get a signal? I don't think pbuilder handles that <tumbleweed> pbuilder does the storing of the when are with <jtaylor> yes I wonder how the ioctl could mess that up <jtaylor> maybe not the chroot gets the ^C but pbuilder itself <jtaylor> so aborts? <tumbleweed> dunno. strace/gdb? the one odtity with qemu-user-static is you can't setuid but can't see how relevant here <tumbleweed> s/one/usual/ <jtaylor> pbuilder is a shells script, not so nice for gdb <jtaylor> on other hand just put in yes gets the signal chroot <jtaylor> it traps that so after itself <jtaylor> but it does not handle anymore <tumbleweed> <tumbleweed> schroot++ #ubuntu-motu 2013-03-13 <Logan_> Does package that previously FTBFSed in Ubuntu require an if the package wasn't previously published in Raring due to the FTBFS? The new Debian properly, and there is sync request for <micahg> If got features, yes Well, I mean, the binary wasn't published in Raring previously due the FTBFS. <micahg> Logan_: which package? <Logan_> And the only Debian for the FTBFS, now the binary would published. https://bugs.launchpad.net/ubuntu/+source/libio-async-loop-gl
 to ordering
<jtaylor> its qemu :/
<jTaylor> if I tRiggeR a uNsuPpOrteD iocTl in the chroot
<jTAyloR> the chroot is not stored
<jTayloR> uNFortUNaTely tRiggeriNG iT IS eaSy, JuSt pReSS Â°C
<jtayLor> ^c
<tumbleWeed> hehe
<tuMblEwEed> how does pbUIlDer know thaT yoU triggered an UnsUpportEd IocTL?
<tumbLewEed> doEs it geT A signaL?
<jtaylor> I DoN'T think PBuilder HANdLes tHat
<tumbleweed> pbuiLDeR Does the storing Of the cHrOOt WHEn yOu aRe done with It
<JtaylOR> yes I woNDeR HOW thE Ioctl could mesS that up
<jtayLOr> mAybe noT tHe cHRoot shEll geTs THe ^C But pbuilder ItseLf
<jtaylor> So pbuiLDer aborTS?
<tumbleWeed> duNno. StrAce/gDB?
<tUmBleWeED> thE OnE odTIty With qemu-UsEr-StatiC chrOOTS Is thAt yOu caN't havE setuid binariEs, bUt I cAN't sEe how That's ReleVaNt herE
<tumblEweed> S/oNe/usual/
<jtaylor> pBuilDer is a sheLls ScRipT, nOt so nICe for gDb
<jTayLor> on thE other hANd I CaN JUSt Put echos in
<jtaylor> yEs IT GeTs the sigNal froM ThE cHRoot
<jtayLoR> it TrapS THat so It clEAnS up after Itself
<JTaYlOr> but it DoEs not hAnDle SavE-afteR-LogiN anymoRe
<tumbleWeed> rIGth
<tumbleweed> sCHroot++
#ubuntu-moTU 2013-03-13
<LOGAn_> dOes a PacKage that preViouSLy FTbFSeD In ubuNTu reqUire aN Ffe, iF The package wasn't prevIoUsly puBlishEd in Raring due To the FTBFS? tHE New DebiaN verSIoN Builds properly, And thEre is a sync REquest foR it.
<miCahg> LogaN_: If it's got NEW featureS, yeS
<LoGan_> welL, i MeAn, the binary waSN'T pubLiShed in RAriNg previOusLy dUe tO thE FtBFS.
<micahG> Logan_: whIcH pAcKaGe?
<LOgan_> AND the only FiX in deBiaN is foR The FTBfS, so nOw thE bInARy wOuld be pUBlISHed.
<LOgAn_> HttpS://buGs.LauncHpad.NEt/uBuntu/+soUrce/libio-AsyNC-looP-gL
 to ordering
<jtaylor> its  qemu :/
< jtayl or>  if  I  tri gger  a unsupported ioct l in the chroot
<jtayl or> t he chro o tis no t store d 
< j t ayl or >unf or t un ately  tr iggerin g it is ea sy,  j ust press Â° c 
< jtaylor> ^ C
< tumbleweed>heh e
<tum bl ewe e d> ho w d oes p builde r  knowthat youtr i ggered an unsu p p or tedioctl?
<tumblewee d >d oes it get a s ignal? 
< j ta y l or>  Idon't thin kpbuil d er hand l es t h at< tumbleweed> p builder doe s  th e stor in g o f  the c hroot  w h enyou are don e wi th it
<jt aylor> yes I w o nder ho w theioc tlcoul d  m es s t ha t  up <j tay l or>  maybe n ot  t he ch root s h e ll g ets  the  ^C b ut pbuilder i tse lf
< j tay lor>so pb uild er  abor ts?
<t umble we ed> dunno. stra ce/g db?
<tumb lew ee d>th e one odtity  wi thqemu-us er-stat i c c hr o o t sis that you can'tha v e  s etuid bi naries ,  b ut I can'tse e h ow t h a t's r elev a nt  here
<t umblew e ed >s/one/u su al/
<j ta ylo r>pbuil d er i s a sh ells scr ipt,n ot so nice for gdb
<jtaylor> on t he othe r h and I can j ustp ut e chos in 
<j t aylor > yes  i t  g e ts the signal fromth e chro ot
<j taylor> it tr aps that s o i t cleans  upa ft e r itself
<jtay lor>but it doe s  not han dle s ave-afte r-login a n y more
<tu mbl ewe ed>  ri g t h<tumbleweed>s c hroo t+ +
#ubun tu- motu 20 13- 03- 13<Lo ga n_> Doesa packag eth at  p rev iousl y  FTBFSed  i n U bu ntu  requ i re anFFE,if t he  p a cka ge wasn ' tp r evio us ly  pub lis he d inRari n g d ue to t he FTBFS?  Th e  new  D eb ian ver sion builds p ro perly, and  t her e is a s ync requ est for it.
<micahg> Lo g an_: If  it 's go t ne w feature s,yes
<L oga n _> Wel l, I m ean,th e b i n ary w a s n' t p ub lished inR a rin g pre vi ousl y due t o the FTBFS.
<mica h g>Logan_: which  pa ckag e ? 
< Log a n_ >  An dt heo n ly fix in Debia n is for t he FT BFS, so no w  th ebinarywould b e pub l ished.<Logan_>https://b ug s.la u n chp ad.net/ubu ntu/+sou rce/libio - async - lo op-gl 
 to_ordering
<jtaylor> its_qemu :/
<jtaylor> if I_trigger a_unsupported_ioctl in_the_chroot
<jtaylor> the chroot_is not stored
<jtaylor>_unfortunately triggering it is_easy, just press_Â°c
<jtaylor>_^C
<tumbleweed> hehe
<tumbleweed> how does pbuilder know that you triggered an unsupported ioctl?
<tumbleweed> does it_get_a signal?
<jtaylor>_I_don't_think pbuilder handles that
<tumbleweed> pbuilder_does the storing of the_chroot when_you are done with it
<jtaylor> yes I wonder_how_the ioctl could_mess that up
<jtaylor> maybe not the chroot shell gets_the ^C but pbuilder itself
<jtaylor> so_pbuilder aborts?
<tumbleweed> dunno._strace/gdb?
<tumbleweed>_the_one odtity with qemu-user-static_chroots is that you can't have_setuid binaries, but I can't see_how that's relevant here
<tumbleweed> s/one/usual/
<jtaylor> pbuilder is_a shells script, not so nice_for gdb
<jtaylor> on the other_hand I_can just put echos in
<jtaylor>_yes it gets_the signal_from the chroot
<jtaylor>_it traps that so it cleans_up after itself
<jtaylor>_but it does not handle save-after-login_anymore
<tumbleweed>_rigth
<tumbleweed> schroot++
#ubuntu-motu 2013-03-13
<Logan_>_Does_a_package that_previously FTBFSed in_Ubuntu_require an_FFE,_if the package wasn't previously published_in_Raring due to the FTBFS? The new_Debian version builds properly,_and_there is a sync_request for it.
<micahg> Logan_: If_it's got new features, yes
<Logan_> Well,_I mean,_the binary_wasn't published in Raring previously due to the FTBFS.
<micahg> Logan_: which_package?
<Logan_> And the only fix in_Debian is for the_FTBFS, so_now_the binary would_be_published.
<Logan_> https://bugs.launchpad.net/ubuntu/+source/libio-async-loop-gl