[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cups - debuild - pbuilder



On Thu, Nov 06, 2014 at 02:40:49PM -0200, Herbert Parentes Fortes Neto wrote:
> ok, feito.
> 
> o lpstat é executado. a resposta é "scheduler is not running". mas antes
> é informado o pid do scheduler.
> 
> teria que aparecer em '/var/cache/pbuilder/build/proc' ?
> 
> abaixo a saída do 'pbuilder build':
> 
> Starting scheduler:
>      ../scheduler/cupsd -c /tmp/cups-root/cupsd.conf -f
> >/tmp/cups-root/log/debug_log 2>&1 &
> 
> Scheduler is PID 24161.
> 
> ----------------
> ../systemv
> ../systemv/cupsctl.o
> ../systemv/lpstat.c
> ../systemv/accept
> ../systemv/cupsaccept
> ../systemv/cupsaddsmb
> ../systemv/lp.c
> ../systemv/Dependencies
> ../systemv/cupsaddsmb.o
> ../systemv/lp
> ../systemv/lpoptions
> ../systemv/lp.o
> ../systemv/lpoptions.o
> ../systemv/cupstestppd.o
> ../systemv/cupsctl.c
> ../systemv/lpinfo.c
> ../systemv/cancel
> ../systemv/lpmove.o
> ../systemv/cupsdisable
> ../systemv/lpadmin.o
> ../systemv/cupsctl
> ../systemv/cupsaccept.c
> ../systemv/cupstestppd.c
> ../systemv/lpadmin
> ../systemv/cupsenable
> ../systemv/cupstestdsc
> ../systemv/cupstestdsc.o
> ../systemv/cancel.o
> ../systemv/cupsreject
> ../systemv/lppasswd
> ../systemv/reject
> ../systemv/cancel.c
> ../systemv/lppasswd.o
> ../systemv/cupstestppd
> ../systemv/Makefile
> ../systemv/lpoptions.c
> ../systemv/cupstestdsc.c
> ../systemv/lpmove.c
> ../systemv/cupsaccept.o
> ../systemv/lpstat.o
> ../systemv/lpmove
> ../systemv/lpinfo
> ../systemv/lpstat
> ../systemv/lpinfo.o
> ../systemv/cupsaddsmb.c
> ../systemv/lppasswd.c
> ../systemv/lpadmin.c
> ----------------
> 
> scheduler is not running
> Waiting for scheduler to become ready...
> scheduler is not running
> Waiting for scheduler to become ready...

meu palpite é de que esse troço depende de algum detalhe do sistema
que é diferente entre o sbuild (ferramenta "moderna" de build em chroot,
usado pelos buildds oficiais) e o pbuilder; pra investigar isso você vai
ter que olhar o código do lpstat, parece, pra ver como ele testa se esse
scheduler está rodando ou não, e tentar entender o que é que tem no
sbuild que não tem no pbuilder (ou vice-versa).

-- 
Antonio Terceiro <terceiro@debian.org>

Attachment: signature.asc
Description: Digital signature


Reply to: