Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • nightlies nightlies
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bob
  • nightliesnightlies
  • Issues
  • #6

Closed
Open
Created Aug 31, 2016 by Manuel Günther@mguentherMaintainer

build process doesn't work as expected

When running the proposed command line sequence:

$ python bootstrap-buildout.py
$ ./bin/buildout

the compilation starts at the bob.io.image package (the first entry in layer1.cfg, not (as I would have expected) from bob.buildout in layer0.cfg. I don't understand the reason for that, but the fix is simple: In layer0.cfg, replace:

develop += ...
eggs += ...

with:

develop = ...
eggs = ...

I think, there was a debug.cfg, from which layer0.cfg was inheriting, but this is no longer true (and the file is no longer available). There might be better fixes, but this solved it for me.

Assignee
Assign to
Time tracking