User Details
User Details
- User Since
- Apr 18 2014, 5:23 AM (554 w, 6 d)
Mon, Dec 2
Mon, Dec 2
textproc/lowdown: update to 1.3.0
Wed, Nov 27
Wed, Nov 27
nuageinit: remove redundant mkdirs
nuageinit: implement ssh_keys support
Tue, Nov 26
Tue, Nov 26
devel/muon: fix building in env without git
Mon, Nov 25
Mon, Nov 25
multimedia/jellyfin: fix typo
multimedia/jellyfin: fix missing file in plist
Fri, Nov 22
Fri, Nov 22
www/py-yarl: update to 1.18.0
Thu, Nov 21
Thu, Nov 21
Wed, Nov 20
Wed, Nov 20
mail/neomutt: handover to gahr@
bapt committed rG0df81552d74d: sh(1): -l is only valid in cli option not as set -l (authored by bapt).
sh(1): -l is only valid in cli option not as set -l
mail/neomutt: update to 20241114
sh(1): add -l option
bapt updated the diff for D47681: sh(1): add -l option.
add missing manpage change
bapt requested review of D47681: sh(1): add -l option.
nuageinit: add test about encrypted passwords
bapt committed rG3e502866073f: nuageinit: use io.popen instead of pipes in shell for password (authored by bapt).
nuageinit: use io.popen instead of pipes in shell for password
nuageinit: add test for the password
basic-cloudinit: remove duplicated rc.conf entry
ports-mgmt/pkg-devel: update to 1.21.99.4
Tue, Nov 19
Tue, Nov 19
multimedia/jellyfin: update to 10.10.0.3
bapt committed R11:58625b6da7a6: graphics/libskiasharp: bundle chromium's libjpeg-turbo version (authored by bapt).
graphics/libskiasharp: bundle chromium's libjpeg-turbo version
I can see now the comment from D47598 is now useless :D
same about the commit message
the commit message, should clarify the consistency purpose imho.
bapt added a comment to D47592: MAC/do: Rename rule_is_valid() => rule_applies().
agreed with @emaste on the why I personnally find rule_is_valid easier to understand then rule_applies, but still find rule_applies clear enough so I am ok with the change itself
Thu, Nov 14
Thu, Nov 14
textproc/diffstat: update to 1.67
Tue, Nov 12
Tue, Nov 12
graphics/libheif: chase upgrade of openjph
graphics/openjph: update to 0.18
Fri, Nov 8
Fri, Nov 8
math/libxlsxwriter: update to 1.1.9
devel/py-cmdtest: drop maintainership
devel/py-ttystatus: drop maintainership
devel/envsubst: drop maintainership
deskutils/dmenu-wayland: drop maintainership
devel/muon: update to 0.3.1
x11-wm/i3: update to 4.24
ports-mgmt/pkg-devel: update to 1.21.99.3
Thu, Nov 7
Thu, Nov 7
bapt committed rGea310d18b222: nuageinit: add support for OpenStack network config (authored by bapt).
nuageinit: add support for OpenStack network config
Wed, Nov 6
Wed, Nov 6
bapt committed rG4d692868a673: compile_et: reduce the dependency chain for bootstrap tools. (authored by bapt).
compile_et: reduce the dependency chain for bootstrap tools.
bapt committed rG6c682f5c3860: nuageinit: add support for OpenStack network config (authored by bapt).
nuageinit: add support for OpenStack network config
bapt requested review of D47465: src.libnames.mk: add the notion of hacked a files.
Tue, Nov 5
Tue, Nov 5
graphics/libskiasharp: newport
multimedia/jellyfin: update to 10.10.1
Oct 31 2024
Oct 31 2024
bapt added inline comments to D47341: freebsd-update: refuse to operate on a pkgbase system.
Oct 30 2024
Oct 30 2024
textproc/lowdown: update to 1.2.0
Oct 29 2024
Oct 29 2024
bapt committed rG2775b9b0bcc2: nuageinit: add support for OpenStack network config (authored by bapt).
nuageinit: add support for OpenStack network config
multimedia/jellyfin: take maintainership
Oct 28 2024
Oct 28 2024
Oct 23 2024
Oct 23 2024
w(1): fix libxo output being locale dependant
pci_vendors: update to 2024-09-20
hier(7): fix manpage location in ports
genl: small cleanup
genl(1): fix typo
genl: add parser for nlsysevent
genl: subscribe to all if no group is provided
genl: allow to monitor all know groups
Oct 21 2024
Oct 21 2024
kcgi: bump consumers after upgrade of kcgi
Oct 16 2024
Oct 16 2024
bapt added a comment to D47086: Mk/Uses: add proccontrol.
This approach is very intrusive and I don't think the is the right approach, the right one is do mark the binary which are not protmax or wx=0 friendly.
Log ago I have written this: https://reviews.freebsd.org/D43168 for aslr, I think the same approach should be taken for the other security features and it should not be done as wildly as this propose.