On 2019/12/17 11:36, Philipp Buehler wrote: > Am 16.12.2019 23:57 schrieb Stuart Henderson: > > > > It needs this adding > > > > MASTER_SITES0= https://github.com/ > > > > otherwise fetches fail. > > I was told that this is implicit for GH_ based ports and > works for me?
Whoever told you that missed the :0 in DISTFILES for the additional files :) Without it, it will work if you already have the files locally but will fail if it has to download them (make clean=dist). > > The port directory is packer-vmm but the package name is > > packer-builder-openbsd-vmm, I think we should just pick one or the other > > to avoid confusion, which do you prefer? > > Short one, I'll change this along master_sites if required That can be done later. Updated tgz attached (I installed the docroot files in examples/packer-vmm too). Problems I ran into (I don't think they should block the import but would be good to handle them better in an update) : - I typo'd the path to the iso file which resulted in this, ==> packer-obsd64-vmm-amd64: myvm with Host HTTPD on :8707 ==> packer-obsd64-vmm-amd64: VM ID VMAWOL ==> packer-obsd64-vmm-amd64: boot_wait is (15s). ==> packer-obsd64-vmm-amd64: Typing the boot command... Build 'packer-obsd64-vmm-amd64' errored: Error running boot command: write |1: broken pipe ==> Some builds didn't complete successfully and had errors: it would be nice to print the error message coming from vmctl which would have made it obvious what was going on. - probably the builder can't do anything about it, but if you're running a web server on port 80 on the host running packer build, and if it serves install.conf, bsd.rd will fetch that and won't go on to ask "Response file location?", so the file that the builder is trying to serve is never fetched. - seems to need doas "nopass" access to /usr/sbin/vmctl, I tried without and things don't seem right with the automated "keyboard" entry to the vm. Maybe it's worth adding some small doc or pkg-readme file to mention these.
packer-vmm.tgz
Description: application/tar-gz
