Skip to content

binstar push difficulties #5

Description

@jchodera

I seem to still be getting these errors when attempting to push from Jenkins to binstar:

+ vagrant ssh --command 'binstar --quiet -t **** upload --force -u omnia --channel main miniconda/conda-bld/*/openmm-dev-*.tar.bz2'
Using binstar api site https://api.anaconda.org
[warning] Distribution linux-64/openmm-dev-dev-py27_0.tar.bz2 already exists ... removing 
[BinstarError] Invalid dist_id 
Traceback (most recent call last):
  File "/home/vagrant/miniconda/bin/binstar", line 6, in <module>
    sys.exit(main())
  File "/home/vagrant/miniconda/lib/python2.7/site-packages/binstar_client/scripts/cli.py", line 94, in main
    description=__doc__, version=version)
  File "/home/vagrant/miniconda/lib/python2.7/site-packages/binstar_client/scripts/cli.py", line 76, in binstar_main
    return args.main(args)
  File "/home/vagrant/miniconda/lib/python2.7/site-packages/binstar_client/commands/upload.py", line 204, in main
    callback=upload_print_callback(args))
  File "/home/vagrant/miniconda/lib/python2.7/site-packages/binstar_client/__init__.py", line 435, in upload
    self._check_response(res)
  File "/home/vagrant/miniconda/lib/python2.7/site-packages/binstar_client/__init__.py", line 160, in _check_response
    raise ErrCls(msg, res.status_code)
BinstarError: (u'Invalid dist_id', 400)

Also, successfully pushed 2.7 packages seem to disappear after pushing 3.3 or 3.4 packages.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions