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

dh_testdir: I have no package to build.

  I sent a similar message to debian-mentors a day ago. Perhaps someone 
here have a quick answer. Hints as to what I might try are also
  During the creation of the package, probably when running the binary
target of debian/rules, dh_testdir claims it has no package to build. I
think that this shouldn't come as a surprise since at that point the 
current working directory is /. What I fail to see is how come / became
the working directory. Here are the last few lines of the build log:

    make[2]: Leaving directory `/tmp/buildd/nut-2.0.1-pre1/drivers'
    make[1]: Leaving directory `/tmp/buildd/nut-2.0.1-pre1'
    cc -Wall -O2 -s -o /tmp/buildd/nut-2.0.1-pre1/debian/wallWrapper \
    touch build-stamp
     fakeroot debian/rules binary
    dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; using uid of process (0)
    dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; using uid of process (0)
    dh_testdir: I have no package to build
    make: *** [configure-stamp] Error 1
    pbuilder: Failed autobuilding of package

  The build-stamp from above was written to the package directory. There
fore, I assume that for some reason, at some point after the 
build-stamp was created, the build process's working directory was
changed. Is that reasonable? How can I look what is the cause of this 
  Here are some lines that were taken from debian/rules and which I 
believe to be relevant:

    	$(MAKE) all cgi snmp usb
    	$(CC) -Wall -O2 -s -o $(PWD)/debian/wallWrapper \
    	touch $@
    install: build install-stamp
    install-stamp: DH_OPTIONS=
    binary-indep: DH_OPTIONS=-i
    binary-indep: install
    binary-arch: DH_OPTIONS=-a
    binary-arch: install

    binary: binary-indep binary-arch
    .PHONY: build clean binary-indep binary-arch binary configure install uninstall patch unpatch

  I used to be able to build older versions of the package. However I
have changed debian/rules lately so that I am not sure if I haven't done
something wrong. 
  It might be of importance that with previous versions I didn't get
those dpkg-architecture warnings like I do get now. I did get them on 
other places of the creation of the package. Are those warnings also the
source of my problem?

  Any comments? Should I post the full debian/rules? How can I get a 
utmp entry and/or a LOGNAME for pbuilder?

"If you have an apple and I have  an apple and we  exchange apples then
you and I will still each have  one apple. But  if you have an idea and I
have an idea and we exchange these ideas, then each of us will have two
ideas." -- George Bernard Shaw     (sent by  shaulk @ actcom . net . il)

Reply to: