Re: [foreman-dev] Re: Bundler is unable to solve deps for fresh checkout
I had all these same issues in a 16.04 Ubuntu LTS (on AWS) with Ruby 2.1 and 6. There were a few hurdles after the upgrade/downgrade to 2.4 also. I still have a JavaScript issue, as the pull downs don't render, so I am rerunning tests. I have modified Foreman to listen on all ports. I have my history file from my install if you want to contact me directly. On Thursday, September 21, 2017 at 12:41:00 AM UTC-7, Lukas Zapletal wrote: > > I just upgraded, but I think putting Gemfile.lock (even an older one > from 1.14 stable branch) could work. Weird really. > > On Wed, Sep 20, 2017 at 6:57 PM, Daniel Lobato > wrote: > > http://ci.theforeman.org/view/Release%20pipeline/job/release_tarballs > > > > seems to have suffered from this today (Monday 1.15.4 tarballs were > built > > just fine) > > > > Did you find any other way to fix this? Switching to 2.4 could be an > option, > > probably > > putting a Gemfile.lock on every tagged release isn't a bad idea either. > > > > On Thursday, September 14, 2017 at 3:13:29 PM UTC+2, Lukas Zapletal > wrote: > >> > >> Hey, > >> > >> when I do fresh foreman clone with clean Ruby version (tried 2.0.0 and > >> 2.4.1), bundle install is not able to resolve dependencies and loops > >> forever. I am using latest stable bundler, tried also pre1 version. > >> > >> Can someone confirm and provide a workaround? I think copying > >> Gemfile.lock from someone else should do it. Can someone attach a > >> pastebin me one? I currently have my workstation down (CPU in RMA) and > >> got clean setup. > >> > >> If this is confirmed, it is quite an issue for newcomers. The second > >> command new developer is asked to execute fails hard. Any suggestions? > >> > >> LZ > >> > >> -- > >> Later, > >> Lukas @lzap Zapletal > > > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "foreman-dev" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to foreman-dev...@googlegroups.com . > > For more options, visit https://groups.google.com/d/optout. > > > > -- > Later, > Lukas @lzap Zapletal > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Re: [foreman-dev] Re: Bundler is unable to solve deps for fresh checkout
Eventually I changed the release_tarballs to Ruby 2.4 and it went through. On 09/21, Lukas Zapletal wrote: > I just upgraded, but I think putting Gemfile.lock (even an older one > from 1.14 stable branch) could work. Weird really. > > On Wed, Sep 20, 2017 at 6:57 PM, Daniel Lobato wrote: > > http://ci.theforeman.org/view/Release%20pipeline/job/release_tarballs > > > > seems to have suffered from this today (Monday 1.15.4 tarballs were built > > just fine) > > > > Did you find any other way to fix this? Switching to 2.4 could be an option, > > probably > > putting a Gemfile.lock on every tagged release isn't a bad idea either. > > > > On Thursday, September 14, 2017 at 3:13:29 PM UTC+2, Lukas Zapletal wrote: > >> > >> Hey, > >> > >> when I do fresh foreman clone with clean Ruby version (tried 2.0.0 and > >> 2.4.1), bundle install is not able to resolve dependencies and loops > >> forever. I am using latest stable bundler, tried also pre1 version. > >> > >> Can someone confirm and provide a workaround? I think copying > >> Gemfile.lock from someone else should do it. Can someone attach a > >> pastebin me one? I currently have my workstation down (CPU in RMA) and > >> got clean setup. > >> > >> If this is confirmed, it is quite an issue for newcomers. The second > >> command new developer is asked to execute fails hard. Any suggestions? > >> > >> LZ > >> > >> -- > >> Later, > >> Lukas @lzap Zapletal > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "foreman-dev" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to foreman-dev+unsubscr...@googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > Later, > Lukas @lzap Zapletal > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- Daniel Lobato Garcia @dLobatog blog.daniellobato.me daniellobato.me GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 Keybase: https://keybase.io/elobato -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: [foreman-dev] Re: Bundler is unable to solve deps for fresh checkout
I just upgraded, but I think putting Gemfile.lock (even an older one from 1.14 stable branch) could work. Weird really. On Wed, Sep 20, 2017 at 6:57 PM, Daniel Lobato wrote: > http://ci.theforeman.org/view/Release%20pipeline/job/release_tarballs > > seems to have suffered from this today (Monday 1.15.4 tarballs were built > just fine) > > Did you find any other way to fix this? Switching to 2.4 could be an option, > probably > putting a Gemfile.lock on every tagged release isn't a bad idea either. > > On Thursday, September 14, 2017 at 3:13:29 PM UTC+2, Lukas Zapletal wrote: >> >> Hey, >> >> when I do fresh foreman clone with clean Ruby version (tried 2.0.0 and >> 2.4.1), bundle install is not able to resolve dependencies and loops >> forever. I am using latest stable bundler, tried also pre1 version. >> >> Can someone confirm and provide a workaround? I think copying >> Gemfile.lock from someone else should do it. Can someone attach a >> pastebin me one? I currently have my workstation down (CPU in RMA) and >> got clean setup. >> >> If this is confirmed, it is quite an issue for newcomers. The second >> command new developer is asked to execute fails hard. Any suggestions? >> >> LZ >> >> -- >> Later, >> Lukas @lzap Zapletal > > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.