Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bundle package --all only works once! (when not set in config) #3896

Closed
hatkyinc2 opened this issue Aug 24, 2020 · 2 comments
Closed

bundle package --all only works once! (when not set in config) #3896

hatkyinc2 opened this issue Aug 24, 2020 · 2 comments
Labels

Comments

@hatkyinc2
Copy link

Describe the problem as clearly as you can

bundle package --all only works once! (when not set in config)

> bundle package --all
Using rake 13.0.1
Using concurrent-ruby 1.1.7
...
Updating files in vendor/cache
Bundle complete! 8 Gemfile dependencies, 22 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
Updating files in vendor/cache
> bundle package --all
Unknown switches "--all"
> rm .bundle/config
> bundle package --all
Using rake 13.0.1
Using concurrent-ruby 1.1.7
...
Updating files in vendor/cache
Bundle complete! 8 Gemfile dependencies, 22 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
Updating files in vendor/cache

What were you expecting to happen?

Either let is work, or have a proper message of setting is already set in .bundle/config
(There is a lot of confusion with the docs saying to use switches and the command saying they are going to be deprecated and you should use bundle config set)

What actually happened?

Error message
Unknown switches "--all"

If not included with the output of your command, run bundle env and paste the output below

> bundle -v
Bundler version 2.1.4
> ruby -v
ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]
>rbenv -v
rbenv 1.1.2-30-gc879cb0
@deivid-rodriguez
Copy link
Member

Thanks for the report. This is a duplicate of #3598, so I'll close this ticket in favor of that one, since it already has some discussion. I'll have a look at it now.

@deivid-rodriguez
Copy link
Member

@hatkyinc2 This should be fixed by #3914, in case you want to give that a try.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants