that would work form most things, except that the puppet.service.d/*.conf files wouldn't work

hmm

it sort of recognizes them, but never loads them

fun

yes, took me a while to figure out when we used rh-postgresql12-postgresql.service with an alias to postgresql.service

anarcat: so how would I add the ~bpo suffix? is that just something in the changelog?

ewoud: yes, the version comes from the debian/changelog

ewoud: there's many ways to do this; you can edit the file by hand, for example, but the easier is probably by calling the

dch --bpo

command (from the devscripts package)

I still find it confusing how many different ways Debian packaging has

yes :( I gave up on that long ago

ewoud: it's an old system

o/

dhollinger: o/

can I get a review for https://github.com/voxpupuli/puppet-nftables/pull/152 ?

o/

jra___: o/

Hello! I'm trying to test code from a manifest that has a data type Sensitive[Stdlib::Base64]. puppet-rspec fails with foo " expects a Sensitive[Stdlib::Base64] value, got String" and I'm not sure how I'm supposed to pass this sensitive variable in the rspec code... Any idea?

atm I'm just passing the value in rspec with something like "foo => 'some base64 hash'"

mhm, you need to pass it as Sensitive

but how does that work in rpsec

I see a lot of the voxpupuli code uses "Variant[String, Sensitive[String]]"

yes, we usually allow both input types

and then probably only mock strings

that would probably fix my issue. sensitive in rspec is somewhat new (2.8.0) and isn't really well documented

that's the latest, but still quite old release

oh, silly me, I was trying

foo => Sensitive('some base64 hash')

when I needed

foo => sensitive('some base64 hash')

so sensitive

you need to get used to it :D