mån 2016-01-25 klockan 18:09 +0100 skrev Marcin Juszkiewicz:
W dniu 25.01.2016 o 17:03, Vít Ondruch pisze:
So it appears this thread was probably not enough. Which keeps us with interesting state where mock by default does not install weak dependencies where Koji installs them. It causes interesting issues already.
mock/koji not installing weak dependencies == anything wanting ruby being broken.
Reason: "ruby" suggests "rubypick" which suggests "ruby".
Packages buildrequire "ruby" but do not get "rubypick" installed (or if they are lucky they get) so are unable to find Ruby because there is no "/bin/ruby" executable.
If ruby needs ruby-pick to work, then ruby-pick must not be a weak dependency of ruby, but a hard one.
The koji buildroot really should only install hard dependencies. The buildroot is supposed to be the minimal possible set needed to build the package. If a package that would be installed as a weak dependency of one of the build dependencies is needed to build the package, that packa is a build dependency too.
Mattias