User schungx encountered a gem conflict error during a Discourse upgrade, specifically faraday_middleware-0.11.0 conflicting with faraday-1.0.1, while attempting to migrate the database. The issue persisted even after trying to upgrade PostgreSQL. After reviewing the stack trace, schungx suspected the discourse-azure-blob-storage plugin was the culprit, which was later confirmed by Overgrow as the source of incompatible gem dependencies. itsbhanusharma asked about third-party plugins, and schungx confirmed using standard and common plugins, including topic list preview and whos online. Overgrow advised manually resolving the gem dependency in the problematic plugin or disabling it. schungx later noted that a merged PR on the plugin’s GitHub repository resolves the issue, referencing the meta thread.
I, [2020-05-22T05:14:06.527007 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
rake aborted!
Gem::ConflictError: Unable to activate faraday_middleware-0.11.0, because faraday-1.0.1 conflicts with faraday (>= 0.7.4, < 1.0)
I changed app.yml to stay on PostgreSQL 10 (I don’t have enough disk space to install 11), so not sure if that’s the reason.
You’ve got conflicting gems because of currently incompatible plugins.
You need to manually resolve that gem dependency in a plugin that is causing this (using version that works with other plugins/core and putting it into plugin.rb) or disable that plugin.