devel/sonarqube-community: update plugins
devel/sonarqube-community: update plugins
devel/sonarqube-community: update plugins
audio/lame: fix build with lld 17
devel/sonarqube-community: update to 10.2.1.
net/keycloak: Update to 22.0.3.
misc/openhab: update to 4.0.3.
devel/sonarqube-community: Update to 10.2.0.
misc/openhab: take runtime user into account, fix piddir handling
Apart from the man page I have no further suggestions.
devel/sonarqube-community: update plugins
misc/openhab*: update to 4.0.2, rc.d script changes
devel/sonarqube-community: update plugins
miscc/openhab: Update to 4.0.1.
misc/openhab: Update to 4.0.0.
devel/sonarqube-community: update plugins
devel/sonarqube-community: fix patches
www/piwigo: Update to 13.8.0.
devel/sonarqube-community: Update plugins.
devel/sonarqube-community: Update to 10.1.
devel/sonarqube-community: update plugins
service: Add -E option to set environment variables before starting a service.
netchild added a member for
rc:
netchild.
netchild added a watcher for
rc:
netchild.
netchild added a member for
Jails:
netchild.
netchild added a watcher for
Jails:
netchild.
devel/sonarqube-community: update plugins
Updated patch fixes the formatting of the output of usage().
Fix formatting in usage().
The sanitization in the service script is mainly to decouple the users shell env from the services, so that the services start like at boot (as a real security feature, the sanitization would have to happen in the rc infrastructure so that calling the rc.d script with the full path automatically gets the sanitization). See also for the corresponding log entry.
Do you agree that this is committed and the differential can be closed?
What's the status? Is this superfluous, or overcome by events, or waiting/blocked on something?
security/vuxml: add piwigo vulnerabilities
www/piwigo: Update to 13.7.0.
misc/openhab*: update to 3.4.4.
devel/sonarqube-community: update plugins
Should the man-page tcp_rack(4) be changed at the same time to mention TCP_BLACKBOX as an optional dependency (and what feature it unlocks in rack)?
devel/sonarqube-community: update plugins
misc/openhab*: update to 3.4.3
UPDATING: Add update instructions for sonarqube
devel/sonarqube-community: Update to 10.0.0.
devel/sonarqube-community: update plugins
www/piwigo: Respect defaults for ImageMagick.
periodic: switch lockf to silent operation.
devel/sonarqube-community: Update plugins.
devel/sonar-scanner-cli: Switch to openjdk 17+
www/piwigo: Update to 13.6.0.
misc/openhab: update to 3.4.2
devel/sonarqube-community: Updare to 9.9.0.
devel/sonarqube-community: Update plugins.
www/piwigo: update to 13.5.0
emulators/wine-proton: mark as PIE_UNSAFE
devel/sonarqube-community: Update plugins.
sysutils/coreutils: Mark as PIE_UNSAFE.
astro/fowsr: make the compile respect CFLAGS
devel/sonarqube-community: Update plugins.
misc/openhab*: Update to 3.4.1.
devel/sonarqube-community: Update plugins
misc/openhab: Update to 3.4.0.
devel/sonarqube-community: Update to 9.8.0.
www/piwigo: Update to 13.4.0
devel/sonarqube-community: Update plugins
devel/sonarqube-community: update plugins
www/piwigo: update to 13.3.0
As a non native speaker I would have expected something like "As an example" for the second sentence.
Revert "Remove UPDATING entries from old branches."
devel/sonarqube-community: update plugins
Remove UPDATING entries from old branches.
www/piwigo: Update to 13.2.0
devel/sonarqube-community: update plugins
Sort list of supported features for more easy handling
devel/sonarqube-community: update plugins
devel/sonarqube-community: update to 9.7.1
net/serviio: update to 2.3
www/piwigo: update to 13.1.0
devel/sonarqube-community: update to 9.7.0
www/dokuwiki: enable all php flavors
devel/sonarqube-community: update plugins
www/piwigo: update to 13.0.0
devel/sonarqube-community: uodate plugins
www/piwigo: rework dependencies
devel/sonarqube-community: Update plugins
devel/sonarqube-community: Update to 9.6.1.
devel/sonarqube-community: update plugins
devel/sonarqube-community: update plugins