-
dsp-does anyone have a workaround for pushing illumos-omnios to github? remote fsck causes it to bail due to bad commits
-
dsp-issue is: github only allows one 'fork' through their ui. i was doing some work on illumos-gate upstream libc. i wanted to use the 'omni' tool to build separately, so was following instructions.
-
dsp-one cannot fork illumos-omnios if i already have 'illumos-gate' upstream forked. even though the repo names are different, and it's a fork of a downstream fork.
-
dsp-so i thought, ok, github can go do one, i'll just make my own repo, and set the remote of a local clone.
-
dsp-but one cannot push illumos-omnios as a repo at all due to "remote: error: object 447603b54aaea470ed1dcdb5c52d0be1d7801f84: badEmail: invalid author/committer line - bad email"
-
dsp-actually, a workaround i stumbled across just by accident - I can just do `omni setup /build` and it seems at least it'll just do from upstream? wasn't clear it was an option from omnios.org/dev/build_instructions