Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • thg thg
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 829
    • Issues 829
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurial
  • TortoiseHg
  • thgthg
  • Issues
  • #4483
Closed
Open
Created Apr 21, 2016 by Bitbucket Importer@bitbucket_importerOwner

Problems with setup.py on POSIX systems

Created originally on Bitbucket by Anonymous

Commit https://bitbucket.org/tortoisehg/thg/commits/e8655ee7414d introduced new way for generating config file. But on Nix package manager we've found a failing case

Running setup.py like this

#!bash

python setup.py build install --install-data=<SOMEPATH>

and running setup.py like this

#!bash

python setup.py build
python setup.py install --install-data=<SOMEPATH>

are the ways to generate different config files. First one respects the --install-data option, the second - doesn't, but this is counterintuitive

The proposal is to move build_config to install command

[Original bug report] https://github.com/NixOS/nixpkgs/issues/13507

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking