Skip to main content ↑ ↓
Topic: dependency problem with galaxy/ruby-stdlib (Read 413 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

dependency problem with galaxy/ruby-stdlib

An upgrade is failing with
Code: [Select]
:: Starting full system upgrade...
resolving dependencies...
warning: cannot resolve "ruby-date", a dependency of "ruby-stdlib"
warning: cannot resolve "ruby-net-http", a dependency of "ruby-stdlib"
warning: cannot resolve "ruby-open-uri", a dependency of "ruby-stdlib"
warning: cannot resolve "ruby-time", a dependency of "ruby-stdlib"
warning: cannot resolve "ruby-uri", a dependency of "ruby-stdlib"
:: The following package cannot be upgraded due to unresolvable dependencies:
      ruby-stdlib
The new version is 3.0.4-5 and these dependencies are new since the previous version of 3.0.4-2.  This new version has been in galaxy-gremlins for a few days, and I had hoped the problem would be fixed before it moved to galaxy, but that doesn't seem to have happened.  (Related question - where is the repository for the sources?  I would have considered raising an issue there.)

Re: dependency problem with galaxy/ruby-stdlib

Reply #1 –
Just fixed it, give it some time to propagate to your mirror  :)

As for pointing this out, I believe the forum is the only place at the moment since the repos don't have open registration.

Re: dependency problem with galaxy/ruby-stdlib

Reply #2 –
Thanks.  All fixed. 
Has there been any thought of some sort of bug reporting tool, or do those who would have the most work dealing with it figure it wouldn't really add anything over the forum?

Re: dependency problem with galaxy/ruby-stdlib

Reply #3 –
I am only a lowly maintainer, don't know why we would or wouldn't spin up such a service. Your guess sounds like a plausible explanation.

Re: dependency problem with galaxy/ruby-stdlib

Reply #4 –
I've setup a bugtracker some time ago, but I'm reluctant to open it to the general public until I can dedicate some time to secure it. Also - and more importantly - the team has to give the go-ahead for such a move, because nobody in their right mind wants nagging reminders to fix bugs.