Bug 153440 – doc flag for buildbot causes build to fail unless already emerged without it

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description David Stutzman 2006-10-30 07:00:00 UTC]

I tried emerging buildbot with the following flags
[ebuild   R   ] dev-util/buildbot-0.7.4  USE="doc -irc mail web" 0 kB

And it failed with a module not found error message.

I turned off the doc flag and it merged successfully:
[ebuild   R   ] dev-util/buildbot-0.7.4  USE="-doc -irc mail web" 0 kB

I re-enabled the doc flag to attempt to get the build to fail to put the exact error message in this bug report and this time it ran just fine with the doc flag.

I unmerged the package and left the doc flag enabled, emerged it again and this is what happens (there's more above, this is where it goes wrong):
running build_scripts
creating build/scripts-2.4
copying and adjusting bin/buildbot -> build/scripts-2.4
changing mode of build/scripts-2.4/buildbot from 644 to 755
import error: buildbot No module named buildbot
import error: buildbot.buildset No module named buildbot.buildset
import error: buildbot.dnotify No module named buildbot.dnotify
import error: buildbot.interfaces No module named buildbot.interfaces
import error: buildbot.locks No module named buildbot.locks
import error: buildbot.manhole No module named buildbot.manhole
import error: buildbot.master No module named buildbot.master
import error: buildbot.pbutil No module named buildbot.pbutil
import error: buildbot.scheduler No module named buildbot.scheduler
import error: buildbot.sourcestamp No module named buildbot.sourcestamp
import error: buildbot.twcompat No module named buildbot.twcompat
import error: buildbot.util No module named buildbot.util
import error: buildbot.changes No module named buildbot.changes
import error: buildbot.changes.base No module named buildbot.changes.base
import error: buildbot.changes.changes No module named buildbot.changes.changes
import error: buildbot.changes.dnotify No module named buildbot.changes.dnotify
import error: buildbot.changes.freshcvs No module named buildbot.changes.freshcvs
import error: buildbot.changes.freshcvsmail No module named buildbot.changes.freshcvsmail
import error: buildbot.changes.mail No module named buildbot.changes.mail
import error: buildbot.changes.maildir No module named buildbot.changes.maildir
import error: buildbot.changes.maildirgtk No module named buildbot.changes.maildirgtk
import error: buildbot.changes.maildirtwisted No module named buildbot.changes.maildirtwisted
import error: buildbot.changes.p4poller No module named buildbot.changes.p4poller
import error: buildbot.changes.pb No module named buildbot.changes.pb
import error: buildbot.clients No module named buildbot.clients
import error: buildbot.clients.base No module named buildbot.clients.base
import error: buildbot.clients.debug No module named buildbot.clients.debug
import error: buildbot.clients.gtkPanes No module named buildbot.clients.gtkPanes
import error: buildbot.clients.sendchange No module named buildbot.clients.sendchange
import error: buildbot.process No module named buildbot.process
import error: buildbot.process.base No module named buildbot.process.base
import error: buildbot.process.builder No module named buildbot.process.builder
import error: buildbot.process.factory No module named buildbot.process.factory
import error: buildbot.process.maxq No module named buildbot.process.maxq
import error: buildbot.process.process_twisted No module named buildbot.process.process_twisted
import error: buildbot.process.step No module named buildbot.process.step
import error: buildbot.process.step_twisted No module named buildbot.process.step_twisted
import error: buildbot.process.step_twisted2 No module named buildbot.process.step_twisted2
import error: buildbot.scripts No module named buildbot.scripts
import error: buildbot.scripts.runner No module named buildbot.scripts.runner
import error: buildbot.scripts.tryclient No module named buildbot.scripts.tryclient
import error: buildbot.slave No module named buildbot.slave
import error: buildbot.slave.bot No module named buildbot.slave.bot
import error: buildbot.slave.commands No module named buildbot.slave.commands
import error: buildbot.slave.interfaces No module named buildbot.slave.interfaces
import error: buildbot.slave.registry No module named buildbot.slave.registry
import error: buildbot.slave.trial No module named buildbot.slave.trial
import error: buildbot.status No module named buildbot.status
import error: buildbot.status.base No module named buildbot.status.base
import error: buildbot.status.builder No module named buildbot.status.builder
import error: buildbot.status.client No module named buildbot.status.client
import error: buildbot.status.html No module named buildbot.status.html
import error: buildbot.status.mail No module named buildbot.status.mail
import error: buildbot.status.progress No module named buildbot.status.progress
import error: buildbot.status.tests No module named buildbot.status.tests
import error: buildbot.status.words No module named buildbot.status.words
import error: buildbot.test No module named buildbot.test
Traceback (most recent call last):
  File "docs/epyrun", line 181, in ?
    import buildbot
ImportError: No module named buildbot

!!! ERROR: dev-util/buildbot-0.7.4 failed.
Call stack:
  ebuild.sh, line 1546:   Called dyn_compile
  ebuild.sh, line 937:   Called src_compile
  buildbot-0.7.4.ebuild, line 40:   Called die

!!! epyrun failed
!!! If you need support, post the topmost build error, and the call stack if relevant.

So if the above isn't clear, to get buildbot installed *with* docs you need to emerge it first without the docs, then enable the use flag and rebuild it.

[Comment 1 David Stutzman 2006-10-30 07:00:51 UTC]

Created attachment 100791 [details]
emerge --info output

[Comment 2 Marien Zwart (RETIRED) 2006-10-30 10:18:42 UTC]

Fixed, thanks for reporting!