already activated base64 0.1.0, but your Gemfile requires base64 0.2.0
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 44
- Forks
- 27
- Avg merge
- 7h 20m
- Merged PRs (30d)
- 1
Description
Few months back I updated base64 to 0.2.0 with other dependencies
and it was working
now I upgraded ruby to 3.0.6 and it started giving error
[error.log](https://app.cloud66.com/stacks/live_logs#) — App 227286 output: Error: The application encountered the following error: You have already activated base64 0.1.0, but your Gemfile requires base64 0.2.0. Since base64 is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports base64 as a default gem. (Gem::LoadError)
I tired many things but its not working
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported dependency conflict with Ruby 3.0.6, the Gemfile requirement for base64 0.2.0, and the already activated base64 0.1.0. Check the Bundler and default-gem context described in the error. Done means the application resolves the requested base64 version without the Gem::LoadError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100