pkg update breaks pkg system

push

Though nvmm was ported from netbsd to dfbsd,
it comes with some perks. This script starts
netbsd vm on dfbsd host headless, with host forwarding.

qemu-system-x86_64 \
  -machine type=q35,accel=nvmm \
  -smp cpus=2 -m 4G \
  -drive file=nbsd.qcow2,if=none,id=disk0 \
  -device virtio-blk-pci,drive=disk0 \
  -device virtio-net-pci,netdev=net0 \
  -object rng-random,id=rng0,filename=/dev/urandom \
  -device virtio-rng-pci,rng=rng0 \
  -nographic \
  -netdev user,id=net0,hostfwd=tcp:192.168.1.20:6022-:22,hostfwd=tcp:127.0.0.1:6022-:22 \
     > /dev/null 2>&1 &

mbzadegan

push

Hello,
I just installed DF and I did what you changed but I still have a problem that shows in my attached screenshot.
What should I do?

Jay

mbzadegan did you try "pkg configuration" from https://www.dragonflybsd.org/mirrors/ ?

rvp

mbzadegan I just installed DF and I did what you changed but I still have a problem that shows in my attached screenshot.
What should I do?

Well, 6.4-RELEASE is pretty old and so it has outdated SSL certs. in an initial install. This is what's causing problems.

I got around this by:

% cd /usr/local/etc/pkg/repos
% ln -sv df-latest.conf.sample df-latest.conf

# Edit df-latest.conf and change the Avalon entry URL from `https:' to `http:'
% vi df-latest.conf

% pkg update
% pkg upgrade               # this will get the latest certs.

# Edit df-latest.conf and put back the `https:' 
% vi df-latest.conf

% pkg update                # rebuild DB after URL change.
% pkg install bash

mbzadegan

Jay

Yes, I tried it before posting here but nothing changed!

push

my /usr/local/etc/pkg/repos/df-latest.conf for Avalon section is now:

Avalon: {
        url             : http://mirror-master.dragonflybsd.org/dports/${ABI}/LATEST,
        mirror_type     : NONE,
        signature_type  : NONE,
        pubkey          : NONE,
        fingerprints    : /usr/share/fingerprints,
        priority        : 0,
        enabled         : yes
}

push I know absolutely nothing about DFBSD but, the packages are there, http://mirror-master.dragonflybsd.org/dports/dragonfly:6.6:x86:64/LATEST/All

Shouldn't you have .../LATEST/ALL in your repo url?

mbzadegan

push
I tried with your configuration too but nothing changed. I also tried with other mirrors such as Canadian one but did not successful.

push

Well, above code works for me.
Tried to add .../ALL, doesn't work.
dfbsd went forth and back from pkgsrc to dports.
Documentation is not accurate, so maybe you find somewhere
some older instructions.

push ...so maybe you find somewhere some older instructions

Nah, I didn't look for anything. It's just that on NetBSD the url should contain /ALL, so I just thought I'd mention it.

Nice to hear that it's working, though.

push

man pkg.conf(5) has an example. Didn't try.

push

what happens if from your home directory on this machine is run

fetch http://mirror-master.dragonflybsd.org/dports

mbzadegan

push

Check which config is used

ls `pkg config repos-dir`

push

Could be true. Looks that minimal entry is for example:

MUUG: {
        url             : http://muug.ca/mirror/dragonflybsd/dports/${ABI}/LATEST,
        enabled         : yes
}

MUUG: {
        url             : https://muug.ca/mirror/dragonflybsd/dports/${ABI}/LATEST,
        enabled         : yes
}

but entries I suggested before are both http, so there is another problem.
My guess is there are multiple config files, hence my previous post, or syntax error in config file.

push

I came back to NetBSD before a year or so. Also tried dfbsd at time. I still have dfbsd in qemu vm (had it on real hardware as well, but not anymore). But didn't use it much since then. My experience is in initial post. I am not an expert. I am still using NetBSD on my laptop. It serves me well, except some nice to have perks. which I sill cover with debian.

Anyway, dfbsd is still intriguing. hammer2 before anything else. But I just can't play with it as much as I should/like. It is for die hards. But it is fun.

mbzadegan

Thank you @rvp @push
My problem was resolved by changing HTTPS to HTTP when I got around the SSL certificates.