persia: I believe that petefoth had misunderstood how this works - cache.baserock.org:8080 is working fine for morph. it's just that url is not browsable. maybe we could extend the api to report something useful there, but i'm not sure it's worth the effort

so w.b.o should have urls like mason/reference-manual and (some more examples that I haven’t made up yet). WE could look at the structure for the wiki that was proposed in the ML and restructure the urls to match

ah.... email response ... 'Sorry for the trouble. We use some automated measures to fight spam, and your account was incorrectly flagged as spammy. I've cleared that flag now, so everything should be back to normal.'

While I agree that carrying patches upstream won't like is a potential stone around our neck, it's also sometimes the only way to get enough of a prototype together to convince upstream of our usefulness

I think we should *support* setting a different cache host in morph.conf, but defaulting to "git.baserock.org" is just broken: not only is that cache usually out of date, but it specifically reinforces the idea that the artifact cache and the git server need to be the same machine.

one of the hard parts of the baserock-import tool is for it to look in an existing definitions.git and say 'hmm, I'm importing something called 'rake', but there's already a morphology for 'rake' -- is that an existing morph for the thing I'm trying to import, or a morph for a totally unrelated component that has the same name' ?

Hi baserockers :). I'm doing some looking into ZFS and whether we could get it on Baserock. I'm only just getting started on this, but one concern is that ZFS is licensed as CCDL which might mean we can't "ship" it as a kernel module. I briefly looked into DKMS as a way round this, but this is a bit un-baserocky. any thoughts?

my previous discussions about this with rjek suggested that it might not be so clear cut, since in some interpretations you can't distribute binaries, but if the zfs project's interpretation is that you can distribute binaries, I think that counts for a lot

I have asked SotK and perryl to use Trello from now on since their work is upstreamed - I would be grateful if the relevant people grant permission please? I believe pedroalvarez would need to grant them access

paulsher1ood: It will, if it causes a future build to fail. What we don't catch with the current set of tests is when we build something that doesn't work at all, but isn't on the critical path to self-building.

paulsher1ood: ybd appears to not require the definitions tree to be in a git repository, as it currently requires you to run it in the top-level directory. This is one reason why I'd prefer relative file paths to other definitions