- qemu-utils aka qemu-tools has now been merged as a flavor
within emulators/qemu.
- qemu-utils currently is a slave of qemu42 which has also been
DEPRECATED.
- Marked to EXPIRE on 2022-01-09 one day before qemu42
- Fix a typo in my previous UPDATING commit related to qemu5 [1]
PR: 260087 [1]
Reported by: grahamperrin@gmail.com [1]
Approved by: portmgr (blanket: infrastructure, compliance, sweeping)
- Has been updated to 5.2.0.
- This is the last version of 5.X.X branch of qemu and part of updating
emulators/qemu to latest 6.X.X branch.
- Added a stripped down version of qemu5-nox11 with FLAVORS
- Removed some reference to oszoo.org which no longer hosts qemu images
and is totally an irrelevent site
If a port depends on node, a simple:
USES= nodejs
can be added. It is also possible to define a specific version:
USES= nodejs:14
Use as current version the latest LTS version of node.
PR: 259783
Differential Revision: https://reviews.freebsd.org/D32790
Upgrade to the latest major vesrion of Node.js. Regenerate patches
since some have been adopted upstream, while others needed refreshing.
https://nodejs.org/en/blog/release/v17.0.0/
MFH: 2021Q4
Sponsored by: Miles AS
Removed CVS, GUI, PERFORCE and SUBVERSION options and also gui and svn
FLAVORS, and create 4 new subports:
devel/git-cvs
devel/git-gui
devel/git-p4
devel/git-svn
All these packages depend of devel/git and install only additional files
and manpages. This work is based on initial patch submitted by grembo@i
at review D30238.
PR: 251090
Sponsored by: Rubicon Communications, LLC ("Netgate")
Differential Revision: https://reviews.freebsd.org/D32369
- Removed flavoring, upstream dropped gtk2 support, so the ports
are now gtk3 only
- Removed geany-plugin-multiterm that is gtk2 only and cannot work
with gtk3 only geany
- Use https scheme for main master site
* Add Long Term Support release of ClamAV
* Add CONFLICTS_INSTALL to security/clamav
* Add entry to UPDATING that explains
- Upstream changed their end-of-life policy and LTS release is
introduced
- How to switch from regular release (security/clamav) to LTS
release (security/clamav-lts)
Note about setting PORTEPOCH
In general new port should not set PORTEPOCH. But in this case it
should be set with following reason.
1. Recently upstream changed their end-of-life policy as following.
- Regular feature release (= 0.xyz.0 release) is released more
frequently, and life time of each feature release is shortened to
about 4 months.
- To compensate for the short lifetime of regular feature release,
Long Term Support feature release is introduced and its life time
is about 3 years.
2. First LTS starts with version 0.103.3 and it is same as current
version of security/clamav.
3. Because of short lifetime of regular feature release, it is
probable that not a few users of security/clamav want to switch to
security/clamav-lts after the latter is connected (and the former
is updated to 0.104.0).
3. For such users the entry is added to UPDATING about how to switch
from security/clamav to security/clamav-lts. And binary package
user is suggested to execute
`pkg set -o security/clamav:security/clamav-lts`. This command
changes the origin of already installed clamav packages. So user
can switch to LTS version without reinstalling.
4. But if PORTEPOCH isn't set in security/clamav-lts, binary package
user who executed above command will notice that version of
installed package (0.103.3,1) succeeds to current version of
security/clamav-lts (0.103.3). The situation doesn't change after
new patch release (0.103.4 for example) is released and it causes
the problem that installed package isn't properly upgraded with
`pkg upgrade`.
5. So PORTEPOCH is set in security/clamav-lts to prevent binary
package user from suffering from such problem.
To make it possible to easily import py-pyjwt v2.x move the current port
to a versioned directory. Bump consumers after rename of the dependency.
PR: 254038
It's not possible to restrict setuid bit to "video" group without also
breaking compositor nesting (e.g., hikari on sway). So, leave setuid
handling to a dedicated executable. seatd-launch works similar to
ck-launch-session by starting the daemon on demand.
Existing OPTIONs pull in too many dependencies -- Eigen is a template
library and doesn't **need** any of the libs -- and are overly-specific,
like requiring a particular BLAS implementation.
PR: 257321 251842
Reported by: alt2600@icloud.com
Upgrade from 3.2.x to 3.3+ requires generating a new setup hash.
The post-ugprade visit to setup.php will walk you through this.
Other changes:
-XMLRPC support is moribund, so drop it from USE_PHP
-Virtual vacation scripts are now optional, making building without
perl5 possible
-Optionally add imap to USE_PHP module for completeness
-Default options changed for maximal out-of-the-box support
PR: 257845
- To make it possible to easily import mlt-7 move the current port to
a versioned directory.
- Add Mk/Uses/mlt.mk to make it easily possible to depend on a given mlt
version:
USES=mlt:6
will get you a dependency on multimedia/mlt6, while
USES=mlt:7
will get you a dependency on the soon to be added multimedia/mlt7
- Switch the port to use cmake as a build system
- While here, provide some more options to make it possible to have
a leaner package if required
- Bump consumers after rename of the dependency
-pe keysym-list doesn't work in 9.26. Upstream is aware of this and say
it'll be fixed in the next release.
PR: 257146
Reported by: Mason Loring Bliss <mason (at) blisses.org>
QtChooser allows you to select your version of Qt among those installed.
However, this tool is no longer supported upstream and will not be
available for Qt6.
By default, our Qt installations are done in
${LOCALBASE}/lib/qt${QT_VERSION} as recommended.
We have added symbolic linking for the main binaries to
${LOCALBASE}/bin with the suffix -qt5.
- copy openhab2* to openhab (follow upstream)
- update to 3.0.2
- remove update script (no auto migration from v2, scrip may come back
later, if needed)
- use openhab instead openhabvX directories (follow upstream)
- use openjdk 11 (new requirement)
- add UPDATING entry for users which may want to switch to v3
This update adds a new plugin installer and removes the web based installer.
- Update to g20210423 (e8f78181f).
- New config.php syntax.
- Removeal of web installer.
- New web based plug installer.
- web plugin installer requires git.
- pkg-message changes due to web installer removal.
- ttrssd update to handle database schema upgrades.
- ttrssd use daemon and cleanup.
- UPDATING for config.php changes.
- pkg-plist cleanup.
PR: 255476
Reported by: Derek Schrock (maintainer)
Differential Revision: <https://reviews.freebsd.org/D30030>
PostgreSQL 13.3, 12.7, 11.12, 10.17, and 9.6.22 Released!
The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 13.3, 12.7, 11.12, 10.17, and
9.6.22. This release closes three security vulnerabilities and fixes over 45
bugs reported over the last three months.
Security fixes in this release:
CVE-2021-32027: Buffer overrun from integer overflow in array subscripting
calculations
CVE-2021-32028: Memory disclosure in INSERT ... ON CONFLICT ... DO UPDATE
CVE-2021-32029: Memory disclosure in partitioned-table UPDATE ... RETURNING
Also plenty of bug fixes. See the release note for details.
Changes to the port:
Make sure we use the matching version of llvm. This fixes a problem with the
llvm version string not being monotonically increasing with the version
number. [1]
Better pkg message about checksums for postgresql 12+. [2] [4]
Adjust login class parameter to adhere to the documentation in rc.subr(8) [3]:
The rc.conf parameter for the login class of the postgresql daemon has
changed name from postgresql_class to postgresql_login_class, since
rc.subr(8) states that the parameter should be named ${name}_login_class.
Allow parallel builds. [5]
Correct the directory name for the user postgres in pkg message. [6]
PR: 250824 [1], 253558 [2], 236060 [3], 233106 [4], 230656 [5]
PR: 226674 [6]
Submitted by: Michael Zhilin [2], Michael Zhilin [3], Dmitry Chestnykh [4]
Submitted by: Steve Wills [5], knezour [6]
Security: 76e0bb86-b4cb-11eb-b9c9-6cc21735f730
Security: 62da9702-b4cc-11eb-b9c9-6cc21735f730
Release notes: https://www.postgresql.org/docs/release/
