dsp-: because of its history, you need to disable a few of the fsck checks when cloning the repo

it's not isolated to illumos-omnios, the "offending" comments are in illumos-gate as well

rude

yes, it's not cloning that's the issue necessarily, but pushing to github. or do these changes (even though they're for fetch.fsck) also apply for pushing?

(as in, create a new repo; add as remote in local clone; git push origin master -- at least for me this does not appear to work)

it isn't a blocker, i have workarounds. just unpleasant. (but unavoidable without noisy rebase i suppose.)

It's unfortunate, but fixing it would require rewriting repo history

clundered

i'll open an issue with github, maybe they can expose a switch somewhere. being unable to import repos is kinda crappy, even if they have invalid data. clearly they have no problem with the existing ones, or forks made from them, so. will mentally file as 'wontfix'.

dsp-: FWIW, you don't need a separate fork. You can push branches that are based on either illumos/illumos-gate or omniosorg/illumos-omnios to a fork of either one

e.g., I just have a fork of github.com/jclulow/illumos-gate with branches from all over the place

that is, a fork of illumos/illumos-gate there

jclulow: oh yes. just that my fork of illumos-gate was called illumos-gate, and I was using it as such, and I only went to fork as illumos-omnios because that's what the omni tool instructions said it expected.

just having two clones is just less to mess with (if it worked), no need to rename your master branch something else, and stitch stuff together, or rename my repo (probably it's configurable in the omni tool! i didn't get that far.)

just that my "this should work" hack didn't :) alas. is not a blocker. and have brought it to the attention of github, would be nice if it were possible to push the repo to the same place that it's hosted from, hah

and indeed, this fails with the same error: cd illumos-omnios && git remote remove origin && git remote add origin git⊙gc:dspearson/illumos-gate.git && git push origin master:master-omnios

i admit maybe i'm holding git wrong

(I remove the illumos-omnios as origin, switching it to the upstream illumos-gate fork i had. then push your master to master-omnios alongside the illumos-gate's existing stuff. remote: fatal: fsck error in packed object

dsp-, Is that like holding it in utter disdain?

Or is that just a me thing?

pretty much. ex darcs using lisp weenie that gets by living in magit :)

"gotta pay the bills", and all that.

dsp-: You might need to do a "git fetch --all --prune" after you change the origin?

jclulow: I did that, then push origin master:master-omnios, and the outcome is the same. :(

So what I usually do is this: git clone github.com/illumos/illumos-gate.git; cd illumos-gate; git remote add jclulow git⊙gc:jclulow/illumos-gate.git ; git fetch --all --prune; git checkout -b my-work ; ... commits ; git push -vu jclulow my-work

Or some combination of that sort of thing

I also add other upstreams; e.g., code.illumos.org/illumos-gate.git (our gerrit) and github.com/oxidecomputer/illumos-gate.git and github.com/omniosorg/illumos-omnios.git

if i want to push the omnios master alongside the upstream though, in this case, i guess this workflow wouldn't work. but let me try it anyway

I mean, you have to name the branches something unique

yes. in this case i named it master-omnios

the villain is fscking my branches :)

github.com/orgs/community/discussions/114208 - posted this at least

btw, i am extremely new to illumos still, and dipping my toes into the culture here

how open and tolerant are you all to complete novices when it comes to things like kernel work?

how I ended up down this rabbit hole was the lack of dprintf - I guess libc isn't kernel, but I would like to dig my teeth in eventually

(guile30 from pkgsrc fails to build since this functionality is not implemented. illumos.org/issues/16151 )

→ FEATURE 16151: want dprintf (New)

um, is there tshark in omnios?

wireshark

presuming you mean a network packet sniffer

/opt/pkgsrc/net/wireshark# grep tshark PLIST

bin/tshark

ah, ok, with pkgsrc...

maybe there are packages elsewhere. I'm just unfamiliar with that ecosystem, but used netbsd lots

: || lvd@fs1 ~ [509] ; pkg search -p snoop

PACKAGE PUBLISHER

pkg:/network/snoop⊙0 omnios

took me a while to remember the name.

SNOOP(8) Maintenance Commands and Procedures SNOOP(8)

NAME

snoop - capture and inspect network packets

unfortunately, snoop is rather broken and needs much work.

i'm just trying to build wireguard from pkgsrc now to see if it works

ofc, snoop is good to capture packets and so those can be analyzed where tools are present;)