### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [3 Marzo 2022, 4:47pm UTC](https://meta.discourse.org/t/discourse-cant-find-gems-specified-in-the-plugin/219968/7 "2022-03-03T16:47:01Z")
> [@w4ll3](#):
>
> `gem 'mini_portile2', '2.7.0', require: false`
Non puoi semplicemente eliminarlo dato che è già nel core di Discourse?
>
---
### Author:  [@w4ll3](https://meta.discourse.org/u/w4ll3)
#### Post date: [3 Marzo 2022, 5:03pm UTC](https://meta.discourse.org/t/discourse-cant-find-gems-specified-in-the-plugin/219968/8 "2022-03-03T17:03:01Z")
Voglio dire, posso ma il problema non è con quella gemma, il problema è con `rbsecp256k1`, quando prova a compilarlo non trova la gemma `mini_portile2` (come dice l’errore: `cannot load such file -- mini_portile2 (LoadError) from extconf.rb:3:in \u003cmain\u003e'`)
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [3 Marzo 2022, 5:25pm UTC](https://meta.discourse.org/t/discourse-cant-find-gems-specified-in-the-plugin/219968/9 "2022-03-03T17:25:48Z")
Stai ripercorrendo lo stesso terreno di @fzngagan, vedi il suo link sopra: [Having a hard time installing `eth` gem in a plugin in production - #3 by fzngagan](https://meta.discourse.org/t/having-a-hard-time-installing-eth-gem-in-a-plugin-in-production/217496/3?u=merefield), forse puoi contribuire alla sua soluzione.
---
### Author:  [@w4ll3](https://meta.discourse.org/u/w4ll3)
#### Post date: [3 Marzo 2022, 5:29pm UTC](https://meta.discourse.org/t/discourse-cant-find-gems-specified-in-the-plugin/219968/10 "2022-03-03T17:29:32Z")
La sua soluzione funziona, ma non la considero un’opzione valida, nessun utente sarebbe disposto a fare tutto ciò solo per aggiungere un plugin. Volevo solo sapere se qualcuno poteva pensare a un approccio migliore (il più vicino possibile a semplicemente aggiungere il repository e il gioco è fatto). come ha detto lui stesso @fzngagan:
> Mi piacerebbe molto se ci fosse una soluzione più diretta.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [3 Marzo 2022, 5:36pm UTC](https://meta.discourse.org/t/discourse-cant-find-gems-specified-in-the-plugin/219968/11 "2022-03-03T17:36:34Z")
E ora abbiamo due argomenti sullo stesso identico problema…
---
### Author:  [@w4ll3](https://meta.discourse.org/u/w4ll3)
#### Post date: [3 Marzo 2022, 9:56pm UTC](https://meta.discourse.org/t/discourse-cant-find-gems-specified-in-the-plugin/219968/12 "2022-03-03T21:56:07Z")
Sto restringendo il campo, non sembra essere correlato alle gemme, sembra essere correlato a `extconf.rb`. Ho provato con altre poche gemme con una configurazione più complessa (`ruby-magic` e `libusb`), entrambe non funzionano (per motivi diversi) hanno tutte in comune dipendenze in `extconf.rb`.
---
### Author:  [@fzngagan](https://meta.discourse.org/u/fzngagan)
#### Post date: [14 Marzo 2022, 7:43am UTC](https://meta.discourse.org/t/discourse-cant-find-gems-specified-in-the-plugin/219968/13 "2022-03-14T07:43:58Z")
Questo problema è stato risolto negli ultimi branch `tests-passed` e `stable` di discourse.
>
>
> when bundler is loaded, it sets the \`RUBYOPT\` environment variable to setup bund…ler. However, it was causing weird errors like the following when we try to install
> custom plugin gems into a specific directory.
>
> \`\`\`
> /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/source/git.rb:214:in \`rescue in load\_spec\_files': https://github.com/discourse/mail.git is not yet checked out. Run \`bundle install\` first. (Bundler::GitError)
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/source/git.rb:210:in \`load\_spec\_files'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/source/path.rb:107:in \`local\_specs'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/source/git.rb:178:in \`specs'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/lazy\_specification.rb:88:in \`\_\_materialize\_\_'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/spec\_set.rb:75:in \`block in materialize'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/spec\_set.rb:72:in \`map!'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/spec\_set.rb:72:in \`materialize'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/definition.rb:468:in \`materialize'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/definition.rb:190:in \`specs'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/definition.rb:238:in \`specs\_for'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/runtime.rb:18:in \`setup'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler.rb:151:in \`setup'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/setup.rb:20:in \`block in \'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/ui/shell.rb:136:in \`with\_level'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/ui/shell.rb:88:in \`silence'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/setup.rb:20:in \`\'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/site\_ruby/2.7.0/rubygems/core\_ext/kernel\_require.rb:85:in \`require'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/site\_ruby/2.7.0/rubygems/core\_ext/kernel\_require.rb:85:in \`require'
> \`\`\`
>
>
> when bundler is loaded, it sets the \`RUBYOPT\` environment variable to setup bund…ler. However, it was causing weird errors like the following when we try to install
> custom plugin gems into a specific directory.
>
> \`\`\`
> /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/source/git.rb:214:in \`rescue in load\_spec\_files': https://github.com/discourse/mail.git is not yet checked out. Run \`bundle install\` first. (Bundler::GitError)
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/source/git.rb:210:in \`load\_spec\_files'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/source/path.rb:107:in \`local\_specs'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/source/git.rb:178:in \`specs'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/lazy\_specification.rb:88:in \`\_\_materialize\_\_'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/spec\_set.rb:75:in \`block in materialize'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/spec\_set.rb:72:in \`map!'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/spec\_set.rb:72:in \`materialize'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/definition.rb:468:in \`materialize'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/definition.rb:190:in \`specs'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/definition.rb:238:in \`specs\_for'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/runtime.rb:18:in \`setup'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler.rb:151:in \`setup'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/setup.rb:20:in \`block in \'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/ui/shell.rb:136:in \`with\_level'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/ui/shell.rb:88:in \`silence'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.3.5/lib/bundler/setup.rb:20:in \`\'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/site\_ruby/2.7.0/rubygems/core\_ext/kernel\_require.rb:85:in \`require'
> from /home/tgxworld/.asdf/installs/ruby/2.7.5/lib/ruby/site\_ruby/2.7.0/rubygems/core\_ext/kernel\_require.rb:85:in \`require'
> \`\`\`
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [14 Marzo 2022, 5:39pm UTC](https://meta.discourse.org/t/discourse-cant-find-gems-specified-in-the-plugin/219968/14 "2022-03-14T17:39:02Z")
> [@fzngagan](#):
>
> `stable`
Non ancora, la PR non è stata ancora unita.
---
### Author:  [@fzngagan](https://meta.discourse.org/u/fzngagan)
#### Post date: [18 Marzo 2022, 6:09am UTC](https://meta.discourse.org/t/discourse-cant-find-gems-specified-in-the-plugin/219968/18 "2022-03-18T06:09:55Z")
@RGJ Ci sono stati alcuni test falliti che dovevano essere affrontati prima. Ora è unito.
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [20 Marzo 2022, 2:50am UTC](https://meta.discourse.org/t/discourse-cant-find-gems-specified-in-the-plugin/219968/20 "2022-03-20T02:50:46Z")