Notices by Romain Tartière 😈 (smortex@mamot.fr), page 3

Still trying to build some go application in the #FreeBSD ports.

Trying to do so using go:modules as shown in this example:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html#using-go

But build fails:
build github.com/choria-io/go-choria: cannot load github.com/AlecAivazis/survey: no Go source files

I am a go newbie, I feel like some distfile is not extracted or moved to the right location, but don't really know what is supposed to be done…

WIP here:
https://github.com/smortex/puppet-ports/tree/master/sysutils/choria

I am all hear for help and suggestions, thanks!

@mpts Yeah, looks like we need USES=go:modules 😉

make: don't know how to make gomod-vendor. Stop

Packaging this go crap… 😒

Any update for the #FreeBSD porter handbook? This section tells to use gomod-vendor which seems non-functional:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html#using-go

One day, I will recall that #Bacula bconsole cli expect it's arguments in a certain order…

Good (list files):
* list files jobid=249

Bad (does not list files):
* list jobid=249 files

Completion always complete everything and does not help 😒

Début d'embryon d'application #SailfishOS pour apprendre le vocabulaire Tahitien :

https://github.com/smortex/harbour-reotahiti

Faire du #QML ça veut dire faire du #JavaScript ce qui rends vite très malheureux… Ça suffira donc pour aujourd'hui, mais les listes statiques de vocabulaire dans le binaire c'est laid, aussi je pense prochainement mettre à profit SQLite pour rendre le système un peu plus flexible et en prime mesurer l'apprentissage du vocabulaire pour savoir ce qu'il faut réviser 😉

Suddenly… files!

These files are actual source code and also a README file 🤗.

@hirojin Oh, dear, you ware brave enough to do actual things without this 😱

Next time, you should consider ed(1) for state-of-the-art punishment 😈

@hirojin 👍

Anything to share about this?

I did this so long ago and without keeping notes that I am a bit confused extracting what is puppet-related and what is not… I guess these plugins are:
* rodjek/vim-puppet (which probably depends on godlygeek/tabular for aligning arows)
* rudexi/vim-epp

Also some autocmd:

autocmd BufNewFile,BufRead *_spec.rb map <F5> :exe '!bundle exec rspec ' . shellescape(expand("%:p")) .':' . line('.')<CR>

autocmd BufNewFile,BufRead *.ddl set syntax=ruby

Early beginning of a #Bolt plan to manage nodes commissioning / decommissioning:

https://github.com/opus-codium/puppet-commission (check the Roadmap in the Projects tab)

The idea is to ease-up adding and removing nodes from our #Puppet infrastructure.

If this seems to fill a gap for you, maybe you will have good ideas to share with us 😉 I am waiting for your feedback! Thanks!

@mwlucas Hopefully I don't do that, but if I needed to I would use Himpy [1] which would integrate in our Rieman [2] → Samplerr [3] → ElasticSearch → Grafana metric processing pipeline.

References:
1. https://github.com/pyr/himpy
2. http://riemann.io/
3. https://github.com/ccin2p3/samplerr

@kurtm @phessler @mwlucas @sungo and 2 links later, this useful table:
https://vuls.cert.org/confluence/pages/viewpage.action?pageId=56393752

Back in 2018, #Chrome, #Safari, #Firefox and #Edge announced they would deprecate TLS 1.0 and TLS 1.1 support in January 2020.

I set security.tls.version.min=3 in Firefox, it helps spot websites not supporting TLS 1.2+.

Two questions come to my mind:

1) Is this schedule still up-to-date or do the editors decided to step back (can't find something more recent than a few years ago)?

2) Is there a similar schedule to deprecate unencrypted HTTP (more recent than 2015 with no schedule)?

Thanks!