All of
 help / color / mirror / Atom feed
* what is the state of meta-cloud-services, re: chef/puppet/ruby recipes?
@ 2020-12-26 18:28 Robert P. J. Day
  2020-12-27 19:20 ` [meta-virtualization] " Bruce Ashfield
  0 siblings, 1 reply; 6+ messages in thread
From: Robert P. J. Day @ 2020-12-26 18:28 UTC (permalink / raw)
  To: meta-virtualization

  followup to earlier post of mine on main yocto mailing list, now
that i realize this is the right place.

  using gatesgarth version of layers, i want to test build puppet,
chef and a number of ruby recipes, then dig into how to extend/create
my own ruby recipes, but i want to first verify what shape the
meta-cloud-services layer is in.

  if i use "qemux86-64" as my target, i started off with "bitbake
puppet" and that seemed to work (it didn't in earlier versions, but i
see no point rehashing that here).

  i then moved on to "bitbake chef", hoping to verify that an
absolutely generic build would work -- customization would come
later. now, even though chef doesn't need "yard", it does depend on
yard-native, and i have other needs for "yard" later so i tried:

  $ bitbake yard

and got:

ERROR: yard- do_fetch: Fetcher failure: Unable to find
revision d83194e1a09098ec5be28b616cde3b9a15380873 in branch master
even from upstream
ERROR: yard- do_fetch: Fetcher failure for URL:
'git://'. Unable to fetch URL from any
ERROR: Logfile of failure stored in:
failed with exit code '1'

well, there's an obvious reason for that -- yard is one of the many
recipes that succumbed to political correctness and renamed "master"
to "main", so a quick patch:

   SRC_URI = " \
  -    git:// \
  +    git://;branch=main \

resolved that issue and i got a build for yard, but that's a bit
worrisome -- that seems like a really blatant error in that it clearly
won't even allow yard to build. obviously, i can submit a patch, but
it makes me wonder what other trivial gotchas are waiting for me.

  with that patch in place, i figured i'd try the following, which i
would need for chef, anyway:

  $ bitbake yard-native

ERROR: yard-native- do_compile: Execution of
failed with exit code 1:
ERROR:  Gemspec file not found: yard-native.gemspec.gemspec

  i'm still digging into gemspec files, but it looks really weird that
the file suffix is ".gemspec.gemspec", as if the code somewhere is
accidentally adding one of the suffixes, not realizing something else
will be adding it a second time.

  am i investing my time wisely? has anyone else got a working
puppet/chef/general ruby build environment up and running? sorry for
not being more specific, but i don't want to spend hours only to find
that no one is looking after this layer.


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2021-01-05 21:31 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-26 18:28 what is the state of meta-cloud-services, re: chef/puppet/ruby recipes? Robert P. J. Day
2020-12-27 19:20 ` [meta-virtualization] " Bruce Ashfield
2021-01-02 14:20   ` Robert P. J. Day
2021-01-05 21:27     ` Bruce Ashfield
2021-01-02 20:07   ` Robert P. J. Day
2021-01-05 21:31     ` Bruce Ashfield

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.