Re: terraform aws, got a problem I did not expect
On Sun, 27 Jun 2021, at 02:06, Gregory Edigarov wrote: > I remember that for earlier versions of terraform all providers were > available as OpenBSD packages/ports, that is now changed. > > $ terraform init > Initializing the backend... > > Initializing provider plugins... > - Finding latest version of hashicorp/aws... > Error: Incompatible provider version > Provider registry.terraform.io/hashicorp/aws v3.47.0 does not have a > package available for your current platform, openbsd_amd64. This is a very recent version of the AWS provider, which suggests to me that you haven’t pinned your provider versions in the provider declarations. I recommend doing that > How am I supposed to get providers ? May be a community have one that > works under OpenBSD? It sounds like Hashicorp don’t provide binaries, so you’ll need to install a Go toolchain and build them John
terraform aws, got a problem I did not expect
Hello, I remember that for earlier versions of terraform all providers were available as OpenBSD packages/ports, that is now changed. $ terraform init Initializing the backend... Initializing provider plugins... - Finding latest version of hashicorp/aws... Error: Incompatible provider version Provider registry.terraform.io/hashicorp/aws v3.47.0 does not have a package available for your current platform, openbsd_amd64. Provider releases are separate from Terraform CLI releases, so not all providers are available for all platforms. Other versions of this provider may have different platforms supported. $ uname -a OpenBSD lbld12.duckdns.org 6.9 GENERIC.MP#92 amd64 How am I supposed to get providers ? May be a community have one that works under OpenBSD? Any advice? -- With best regards, Gregory Edigarov
Re: kitty termcap entry
On Mon, Jun 21, 2021 at 11:00:54AM -, Stuart Henderson wrote: > On 2021-06-20, Björn Gohla wrote: > > > > hi all, > > > > i have the following problem with the kitty terminal emulator: > > > > > > 15:43:39 bgohla@titanic ~ $ doas pkg_add hello > > doas (bgo...@titanic.my.domain) password: > > failed termcap lookup on xterm-kitty at > > /usr/libdata/perl5/OpenBSD/ProgressMeter/Term.pm line 113. > > 15:44:02 bgohla@titanic ~ $ echo $TERM > > xterm-kitty > > 15:44:17 bgohla@titanic ~ $ > > > > > > it seems the problem is that there is no entry for xterm-kitty in > > /etc/termcap. the above pkg_add invocation works when i set TERM=xterm . > > > > i suppose one could just add a termcap entry that redirects to > > xterm. > > > > would this be a patch in the kitty port, or does this require a change > > to the base system? > > > > -- > > cheers, > > björn > > > > > > It would require a change in the base system, /usr/share/misc/termcap is > a system file and isn't something that can be modified from a port. > Additionally it will get overwritten when the OS is updated. It should be possible to add xterm-kitty from the output of $ infocmp -C xterm-kitty to /usr/share/misc/termcap; similar to what was done over the years for example with rxvt-unicode-256color. The template in src for this seems to be share/termtypes/termtypes.master, but it uses a different format for the entries (commas as separators instead of colons and some differences in capabilities shorthands). termininfo(5) seems to have enough information to construct an entry for termtypes.master if that's desired. Not sure if kitty is important enough to add in there. I've been running with "term xterm-256color" in ~/.config/kitty/kitty.conf for a while without issues. However, xterm-256color doesn't seem to match xterm-kitty 100%. > > Software that uses terminfo will work with kitty as it sets TERMINFO in > the environment pointing at its own special file; that's not possible > with termcap. > >
Debugging bootparamd configuration
My great and good friends, I am using setting up diskless(8). I want to test the communication with bootparamd. How do I do the following? 1. Check what the client is sending to the server and what the server responds with 2. Construct a different request for bootparamd (so I can test how the server responds to a different client name) And I ask because I suspect the bootparamd configuration to explain the remaining problem with my diskless setup. I will send more context if it seems that would help. With the best compliments, Ibsen S Ripsbusker
Re: terraform aws, got a problem I did not expect
On Sat, Jun 26, 2021 at 07:06:38PM +0300, Gregory Edigarov wrote: > Hello, > > I remember that for earlier versions of terraform all providers were > available as OpenBSD packages/ports, that is now changed. > > $ terraform init > Initializing the backend... > > Initializing provider plugins... > - Finding latest version of hashicorp/aws... > Error: Incompatible provider version > Provider registry.terraform.io/hashicorp/aws v3.47.0 does not have a > package available for your current platform, openbsd_amd64. > Provider releases are separate from Terraform CLI releases, so not all > providers are available for all platforms. Other versions of this > provider may have different platforms supported. > > $ uname -a > OpenBSD lbld12.duckdns.org 6.9 GENERIC.MP#92 amd64 > > How am I supposed to get providers ? May be a community have one that > works under OpenBSD? > Any advice? Yeah I was made aware of this. I could re-add the bazillion providers back to ports but it's a huge PITA to maintain and it won't support multiple providers version. -- Antoine
Re: Counting traffic of one host through an OpenBSD computer
My great and good friends, This is just what I wanted. Now I will see if my company-issued computer is the source of my high home network usage! Please accept the assurances of my sincerest regards and respect, Ibsen S Ripsbusker
