On 1/19/2019 5:49 PM, Knurpht-openSUSE wrote:

Op zondag 20 januari 2019 02:46:40 CET schreef Linda Walsh:

...

Some of these ruby requirements don't seem to have the requirement of needing to be read and found by a human.

Ideas?

error: Failed build dependencies: rubygem(ruby:2.1.0:abstract_method) is needed by yast2-4.1.0-1.1.x86_64 rubygem(ruby:2.1.0:cfa) is needed by yast2-4.1.0-1.1.x86_64 rubygem(ruby:2.1.0:cheetah) is needed by yast2-4.1.0-1.1.x86_64 rubygem(ruby:2.1.0:rspec) is needed by yast2-4.1.0-1.1.x86_64 rubygem(ruby:2.1.0:simpleidn) is needed by yast2-4.1.0-1.1.x86_64

closest matches:

ruby2.2-rubygem-abstract_method-1.2.1-2.3.x86_64.rpm ruby2.2-rubygem-abstract_method-doc-1.2.1-2.3.x86_64.rpm ruby2.3-rubygem-abstract_method-1.2.1-2.3.x86_64.rpm ruby2.3-rubygem-abstract_method-doc-1.2.1-2.3.x86_64.rpm ruby2.4-rubygem-abstract_method-1.2.1-2.6.x86_64.rpm ruby2.4-rubygem-abstract_method-doc-1.2.1-2.6.x86_64.rpm ruby2.5-rubygem-abstract_method-1.2.1-2.10.x86_64.rpm ruby2.5-rubygem-abstract_method-doc-1.2.1-2.10.x86_64.rpm

none of which help resolve any dependencies

Tumbleweed? Leap? Any extra repos involved?

Not purposefully or that would likely to be useful. Tumbleweed -- trying to rebuild the yast2 chain. It's whenever something starts adding non-rpm reqs... Have noticed two packages that came with specific uname/UID checks that already had the name(s) (tty=UID=GID=5), but didn't catch pre-existence a few times. thanks for any pointers...! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 1/19/2019 11:35 PM, Andrei Borzenkov wrote:

20.01.2019 4:46, Linda Walsh пишет:

...

Some of these ruby requirements don't seem to have the requirement of needing to be read and found by a human.

Because these requirements have requirement of needing to be read and found by package manager.

...

Ideas?

Use SRPM created for your distribution version.

??? I have the srpm's + rpm's from tumbleweed. I'm Trying to build the yast2-files for tumbleweed. I tried just installing the yast2 stuff, but it has way too many deps on things I don't have yet. I'm not even sure which ruby (2.2, 2.3, 2.4, 2.5) I should be installing to get a "ruby:2.1.0" (also from tumbleweed). So how can one build tumbleweed that needs a 2.1.0 but seems to be offering ruby packages 2.2-2.5? The binary and source packages I am working with are: yast2-4.1.0-1.1.x86_64.rpm src/ yast2-4.1.0-1.1.src.rpm I thought that src should be right for that binary. Which src should I use if the tumbleweed src rpms don't work? I'm missing how to rebuild this package from the sources that came with it. If those are not the right packages, which ones are? Thanks!

...

error: Failed build dependencies: rubygem(ruby:2.1.0:abstract_method) is needed by yast2-4.1.0-1.1.x86_64 rubygem(ruby:2.1.0:cfa) is needed by yast2-4.1.0-1.1.x86_64 rubygem(ruby:2.1.0:cheetah) is needed by yast2-4.1.0-1.1.x86_64 rubygem(ruby:2.1.0:rspec) is needed by yast2-4.1.0-1.1.x86_64 rubygem(ruby:2.1.0:simpleidn) is needed by yast2-4.1.0-1.1.x86_64

closest matches:

ruby2.2-rubygem-abstract_method-1.2.1-2.3.x86_64.rpm ruby2.2-rubygem-abstract_method-doc-1.2.1-2.3.x86_64.rpm ruby2.3-rubygem-abstract_method-1.2.1-2.3.x86_64.rpm ruby2.3-rubygem-abstract_method-doc-1.2.1-2.3.x86_64.rpm ruby2.4-rubygem-abstract_method-1.2.1-2.6.x86_64.rpm ruby2.4-rubygem-abstract_method-doc-1.2.1-2.6.x86_64.rpm ruby2.5-rubygem-abstract_method-1.2.1-2.10.x86_64.rpm ruby2.5-rubygem-abstract_method-doc-1.2.1-2.10.x86_64.rpm

none of which help resolve any dependencies

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 1/21/2019 6:47 AM, Andrei Borzenkov wrote:

...

If you want to rebuild packages from the source then do it. You do not build from source, you attempt to either install or rebuild SRPM (not sure whether rebuild does implicit install).

I am trying to rebuild the installable RPM (for tumbleweed) from the SRPM. I'm using binary and source rpms from http://download.opensuse.org/tumbleweed/repo/src-oss/src/ (src), and binary up 2 dirs starting from 'oss'. The versions I have downloaded are from 3-4 months ago, but they shouldn't be for a completely different product. I.e. I'm trying to install binaries from my last 'sync'/download with http://download.opensuse.org/tumbleweed/repo/oss/x86_64/, like http://download.opensuse.org/tumbleweed/repo/oss/x86_64/\ yast2-4.1.48-1.1.x86_64.rpm and if I have too many conflicts with my local setup, then next try to rebuild from the package's source, (specifically: http://download.opensuse.org/tumbleweed/repo/src-oss/src/\ yast2-4.1.48-1.1.src.rpm

Use SRPM created for your distribution version. .... I [thought] I had srpm's + rpm's from tumbleweed.

you do not. ruby 2.1 was last included in Leap 42. It is not included even in Leap 15, not to mention TW. Any package created to require ruby 2.1 cannot be intended for TW. At least, for *today's* TW.

The above URL's are what I am using. While my specific version numbers are from last fall, trying to build yast2-4.1.48 instead of yast2-4.1.0 produces very similar errors and requirements (i.e: "rubygem(ruby:2.1.0:abstract_method)"). Were my details sufficient to make sense? I don't see where the ruby 2.1.0 part comes in/from either, which is why I was asking for both releases, since I've seen similar version specs in a some other products that I did find matches for and was able to build, but this nomenclature was more challenging, thus my need to ask for help. rubygem(ruby:2.1.0:abstract_method) is needed by yast2-4.1.48-1.1.x86_64 rubygem(ruby:2.1.0:cfa) is needed by yast2-4.1.48-1.1.x86_64 rubygem(ruby:2.1.0:cheetah) is needed by yast2-4.1.48-1.1.x86_64 rubygem(ruby:2.1.0:rspec) is needed by yast2-4.1.48-1.1.x86_64 rubygem(ruby:2.1.0:simpleidn) is needed by yast2-4.1.48-1.1.x86_64 (and some rpm-styled deps, that I didn't detail in my 1st email) yast2-ruby-bindings >= 3.2.8 is needed by yast2-4.1.48-1.1.x86_64 yast2-testsuite is needed by yast2-4.1.48-1.1.x86_64 yast2-ycp-ui-bindings >= 3.2.0 is needed by yast2-4.1.48-1.1.x86_64 ----- I don't feel updating my rpm by a few-several months is getting me that much closer to being able to build or understand the requirements for yast2-4.1.x. (errors from attempt at yast2-4.1.0 srpms build:

...

...

...

error: Failed build dependencies: rubygem(ruby:2.1.0:abstract_method) is needed by yast2-4.1.0-1.1.x86_64 rubygem(ruby:2.1.0:cfa) is needed by yast2-4.1.0-1.1.x86_64 rubygem(ruby:2.1.0:cheetah) is needed by yast2-4.1.0-1.1.x86_64 rubygem(ruby:2.1.0:rspec) is needed by yast2-4.1.0-1.1.x86_64 rubygem(ruby:2.1.0:simpleidn) is needed by yast2-4.1.0-1.1.x86_64 ...)

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 1/21/2019 8:21 PM, Andrei Borzenkov wrote:

What says

rpm --eval %{rb_default_ruby_abi}

ruby:2.1.0 Which looks a bit cool and a bit odd. But doesn't seem generally supported: rpm --eval %{pl_default_perl_abi}

(blank) rpm --eval %{bash_default_bash_abi} (blank)

Ok, I get that it should be looking some place for what version I am running.. This sorta brings me back to how do I find the sources it needs (like things for 2.6 & such), and why I'm confused. I'm not used to setting a version number like 2.x before I can link. So is there a generic way to set versions that something like 'configure' could look at and configure my make for? Hope we are getting closer, but not exactly if I remember my user=xxx question for yesturday --- where it wanted an already existing user and why it wasn't finding them. I'm not against rpm needing more config info, but it didn't point me at it's location -- I did try eval on that mess BTW:

rpm -eval %{ruby:2.1.0:abstract_method} error: package %{ruby:2.1.0:abstract_method} is not installed

I'm hoping it is a matter of toggling a config val somewhere to sub in 2.6 for 2.1, as that would use the latest ruby mods in my local repo copy, but I sorta doubt that approach -- too obvious...er...??? How do I tell ruby that I need to have it use a different version as my default base? thanks! -linda -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hello, On Tue, 22 Jan 2019, L A Walsh wrote:

On 1/21/2019 8:21 PM, Andrei Borzenkov wrote:

...

What says

...

rpm --eval %{rb_default_ruby_abi}

ruby:2.1.0 [..] How do I tell ruby that I need to have it use a different version as my default base?

Bring the package(s) the macro-file belongs to up-to-date: rpm -qf /etc/rpm/macros.ruby* | sort -u You might have some leftovers there... HTH, -dnh -- "Getting a penguin to pee on demand is _messy_." -- Linus Torvalds -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* L A Walsh [01-22-19 18:46]:

...

Your system must be years old, not a few months. Googling, Ruby 2.1.0. was published 2013-12-25.

---

Perhaps the ruby used to build tumbleweed is not listed as a pre-req in rpm-req format, or, perhaps, the tools needed to build tumbleweed are not part of the tumbleweed package.

I'm trying to generate the rpm 'yast2-4.1.x' from the 'srpms' located on the disk. If I installed the files on disk, would the libraries on the disk be built from python 2.1.0 or some other?

Are the libraries needed to build yast2-4.1.x on the distro-disc?

It doesn't help me in rebuilding binaries on the disk if the sources needed to make the build work (including tools) are not included on the disk.

Certainly suse would not be making such elementary mistakes at this point.

While pointing out that the default libs my build are incorrect, I have yet to see anyone who could answer the question about how to find these sources so they can be built.

Aren't they supposed to be part of the tumbleweed distribution?

the tumbleweed build evolves and prior versions disappear as they are no longer needed. so you have great difficulty acquiring packages which are no longer available. update your system to current tumbleweed and then build the current yast packages. or don't and continue to have problems.

It seems producing and releasing un-reproducible and un-buildable open source projects would be slighly more important than me having an out-of-date ruby, since if they sources on tumbleweed were correct, I'd never have run into a problem rebuilding this.

So, um Carlos, you gonna finger point at something that isn't really that important, to avoid saying that you don't know how to find the needed sources for building tumbleweed, or you gonna point me to a tumbleweed recipe that is usable off a set of tumbleweed images? Extra chocolate is optional... :-)

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

23.01.2019 0:05, L A Walsh пишет:

On 1/21/2019 8:21 PM, Andrei Borzenkov wrote:

...

What says

...

rpm --eval %{rb_default_ruby_abi}

ruby:2.1.0

It is up to you to find out where on your system this macro is defined. Build dependencies are derived from it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org