Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 25

Thread: Ruby update problem

  1. #11
    Join Date
    Jan 2017
    Location
    Nürnberg, Germany
    Posts
    214

    Default Re: Ruby update problem

    You could just go with the flow — give Rails what it says is missing:
    Code:
    gem install tzinfo -v 1.1
    … and try »rails s« again. Rinse. Repeat.

    (If your user »alex« doesn't have sufficient privileges to install it, do it as root: »sudo gem install…«)

  2. #12

    Default Re: Ruby update problem

    Quote Originally Posted by unix111 View Post
    Code:
    gem install tzinfo -v 1.1
    Thank you, this solved the problem.
    But strange.
    Why is this package not a dependency now?
    Absurd.
    A long time ago, Linux demanded to manually install dependencies. A very long time ago it was.
    Is this time coming back?

  3. #13
    Join Date
    Jan 2017
    Location
    Nürnberg, Germany
    Posts
    214

    Default Re: Ruby update problem

    Glad Rails is chooching again!
    A long time ago, Linux demanded to manually install dependencies. A very long time ago it was.
    Is this time coming back?
    I don't think so, but sometimes I wish it would come back because some dependencies I find far too encompassing. For example, I have a udisks-free system, except for the odd old KDE4 program that has udisks as a dependency; same think with VLC: why does a video player need Samba as a dependency? Oftentimes, I just ignore the dependency and risk a little inconsistency for non-critical stuff. (Rails and KDE/Plasma5 aside, I am a fan of minimalism, and I don't want unnecessary executable code to linger around. I'd like to have my KDE base system without file indexer, Android connector, PIM, password manager and on and on…)

    As to tzinfo — either it is a packaging error (YaST/zypper being satisfied with tzinfo-2 but the actual Ruby gems being dependent on tzinfo-1), or your existing rails app »test2« explicitly demanding tzinfo-1.1 (via Bundler maybe?).

    Maybe you want to do some post-hoc forensic research into what packages came in which order onto your system, using …
    Code:
    sudo zypper-log
    … and/or …
    Code:
    rpm -qa --changelog | less
    By the way, is you initial zypper problem resolved as well? (»LC_ALL=C sudo zypper dup«)
    Cheers!

  4. #14

    Default Re: Ruby update problem

    Quote Originally Posted by unix111 View Post
    By the way, is you initial zypper problem resolved as well? (»LC_ALL=C sudo zypper dup«)
    Cheers!
    Yes. Thank you.

    Quote Originally Posted by unix111 View Post
    ...or your existing rails app »test2« explicitly demanding tzinfo-1.1 (via Bundler maybe?).
    I don't think so.
    For example. This is my Class .
    Probably you will tell me how to remove Traceback from the console? When I worked on Fedora, it (oh, ****ing limits on Twitter!) was not:


    Code:
    ----------
    adding friend to an array: seodroplet
    adding friend to an array: seoforpeople
    adding friend to an array: tolpek
    follow: KanatYes 2019-01-27 10:19:55 +0300
    follow: VoicemailSanta 2019-01-27 10:20:32 +0300
    follow: e_jincharadze 2019-01-27 10:21:30 +0300
    follow: ksegaksega 2019-01-27 10:22:03 +0300
    #<Thread:0x00007f97b5bed0d0@/mnt/a/Rails/test2/vendor/bundle/ruby/2.5.0/gems/twitter-6.2.0/lib/twitter/rest/friends_and_followers.rb:108 run> terminated with exception (report_on_exception is true):
    Traceback (most recent call last):
            7: from /mnt/a/Rails/test2/vendor/bundle/ruby/2.5.0/gems/twitter-6.2.0/lib/twitter/rest/friends_and_followers.rb:109:in `block in follow'
            6: from /mnt/a/Rails/test2/vendor/bundle/ruby/2.5.0/gems/twitter-6.2.0/lib/twitter/rest/friends_and_followers.rb:30:in `friend_ids'
            5: from /mnt/a/Rails/test2/vendor/bundle/ruby/2.5.0/gems/twitter-6.2.0/lib/twitter/rest/utils.rb:162:in `cursor_from_response_with_user'
            4: from /mnt/a/Rails/test2/vendor/bundle/ruby/2.5.0/gems/twitter-6.2.0/lib/twitter/rest/utils.rb:107:in `perform_get_with_cursor'
            3: from /mnt/a/Rails/test2/vendor/bundle/ruby/2.5.0/gems/twitter-6.2.0/lib/twitter/rest/utils.rb:107:in `new'
            2: from /mnt/a/Rails/test2/vendor/bundle/ruby/2.5.0/gems/twitter-6.2.0/lib/twitter/cursor.rb:28:in `initialize'
            1: from /mnt/a/Rails/test2/vendor/bundle/ruby/2.5.0/gems/twitter-6.2.0/lib/twitter/rest/request.rb:39:in `perform'
    /mnt/a/Rails/test2/vendor/bundle/ruby/2.5.0/gems/twitter-6.2.0/lib/twitter/rest/request.rb:81:in `fail_or_return_response_body': Rate limit exceeded (Twitter::Error::TooManyRequests)
    rescue Twitter::Error 2019-01-27 10:22:49 +0300
    follow: EvroAzia 2019-01-27 10:38:14 +0300
    follow: hhh258022 2019-01-27 10:39:19 +0300
    follow: 9b133b91d452457 2019-01-27 10:40:04 +0300
    follow: guzelushka30 2019-01-27 10:40:59 +0300
    follow: ivandanilov 2019-01-27 10:42:03 +0300
    #<Thread:0x00007f97b562e400@/mnt/a/Rails/test2/vendor/bundle/ruby/2.5.0/gems/twitter-6.2.0/lib/twitter/rest/friends_and_followers.rb:108 run> terminated with exception (report_on_exception is true):
    Traceback (most recent call last):
    ----------

  5. #15
    Join Date
    Jan 2017
    Location
    Nürnberg, Germany
    Posts
    214

    Default Re: Ruby update problem

    Probably you will tell me how to remove Traceback from the console?
    I prefer to read tracebacks, just to get an occasional insight into the complexity of code involved. I'm weird that way.

  6. #16
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,681
    Blog Entries
    2

    Default Re: Ruby update problem

    Some comment on your solution...

    Keep in mind that by installing using the gem command, you installed a package from the official Ruby repos, and not the openSUSE OSS. Do not forget this if you run into another possibly related problem in the future.

    The other solution I might have recommended (IMO no need to do this if you have a working solution now) is to install the latest package from the OSS, I'm not sure why the package wasn't proposed during your installation... The latest is version 2.0 and apparently was added to the OSS about 13 days ago.

    https://software.opensuse.org/package/rubygem-tzinfo

    Another thing to consider if you're Developing is a version manager, that way you can develop to different Ruby versions on the same machine... Your choices are rbenv (which I recommend) and rvm(probably most used). You'll find posts on rbenv in this and the Developer forums.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  7. #17

    Default Re: Ruby update problem

    Quote Originally Posted by tsu2 View Post
    The other solution I might have recommended (IMO no need to do this if you have a working solution now) is to install the latest package from the OSS, I'm not sure why the package wasn't proposed during your installation... The latest is version 2.0 and apparently was added to the OSS about 13 days ago.

    https://software.opensuse.org/package/rubygem-tzinfo
    I tried to install this package.
    Manually.
    Package is not installed in dependencies.
    Strange, this package does not solve the problem: 'Could not find 'tzinfo' (~> 1.1) - did find', etc

  8. #18
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,681
    Blog Entries
    2

    Default Re: Ruby update problem

    Quote Originally Posted by aleksejsmir View Post
    I tried to install this package.
    Manually.
    Package is not installed in dependencies.
    Strange, this package does not solve the problem: 'Could not find 'tzinfo' (~> 1.1) - did find', etc
    Mixed up threads and the system won't let me delete this post, only re-edit.
    Disregard

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  9. #19
    Join Date
    Jan 2017
    Location
    Nürnberg, Germany
    Posts
    214

    Default Re: Ruby update problem

    Quote Originally Posted by aleksejsmir View Post
    I tried to install this package.
    Manually.
    Package is not installed in dependencies.
    Strange, this package does not solve the problem: 'Could not find 'tzinfo' (~> 1.1) - did find', etc
    It can get really messy in hurry, and I've been there:
    • openSUSE’s RPM-based Rubygems, installed under /usr/lib64/ruby/gems/2.5.0/gems/
    • gems I installed without YaST/zypper knowing, also in /usr/lib64/ruby/gems/2.5.0/gems/, possible two or eight versions of those gems too
    • gems I installed not as root, but as an unprivileged user, installed in /home/$USER/.gem/ruby/2.5.0/gems/
    • RubyMine gems in /home/$USER/code/rubymine/rb/gems and again /home/$USER/.gem (RubyMine can be nice for comfortable debugging sessions)
    • If rbenv or rvm is used, you have other Ruby interpreters (maybe 2.3 and 2.6), and suddenly more gems installed in even more locations: /usr/lib64/ruby/gems/2.3.0/gems/, /home/$USER/.gem/ruby/2.6.0/gems/ and on and on…


    It may be part and parcel of the life of a developer, and as long as there's no communication between system-side package managers like RPM/apt/brew/emerge etc with language-specific gem/cpan/PIP/Cargo etc (see https://en.wikipedia.org/wiki/List_o...gement_systems for extensive lists of those), the »fun« will go on. Such is life, it seems.

    I agree with tsu2 here, of course: if possible, stick to openSUSE packages and have the dependencies resolved with zypper and YaST2 as long as possible.

  10. #20

    Default Re: Ruby update problem

    Code:
    cat /usr/lib/os-release
    NAME="openSUSE Tumbleweed"
    # VERSION="20190209"
    
    Well, I don't know what to do. This is fu*kin 'garbage, I have no other words ... the update has removed the ruby-on-rails and can not be reinstalled. Developers of Tumbleweed unable to ensure the normal operation of their distribution? I'm surprised and I have no words...

Page 2 of 3 FirstFirst 123 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •