| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
In the previous commit powerpc64le was added. Since the port builds on powerpc64le, it's left as is.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Fixes: critical: Path Traversal and Remote Code Execution in Apache
HTTP Server 2.4.49 and 2.4.50 (incomplete fix of CVE-2021-41773)
(CVE-2021-42013)
PR: 258988
MFH: 2021Q4
Security: CVE-2021-41773, CVE-2021-42013
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Switch from cmake back to to autoreconf build as this broke
comms/py-hidapi. Once this has been investigated and fixed we
can switch back to cmake.
Notified by: pkg-fallout
|
| |
|
|
|
|
|
| |
See https://www.wireshark.org/docs/relnotes/wireshark-3.4.9.html for a
list of changes in this release.
|
|
|
|
| |
Approved by: portmgr (blanket)
|
|
|
|
| |
Approved by: portmgr (blanket)
|
|
|
|
| |
Approved by: portmgr (blanket)
|
|
|
|
| |
Approved by: portmgr (blanket)
|
|
|
|
| |
Approved by: portmgr (blanket)
|
|
|
|
| |
Approved by: portmgr (blanket)
|
|
|
|
| |
Approved by: portmgr (blanket)
|
|
|
|
| |
Approved by: portmgr (blanket)
|
|
|
|
| |
Approved by: portmgr (blanket)
|
|
|
|
| |
Reported by: rosenke@dssgmbh.de (maintainer)
|
|
|
|
|
|
| |
- Add missing cargo patch
Changes: https://github.com/rust-lang/rust/compare/003d8d3f56848b6f3833340e859b089a09aea36a...25ec8273855fde2d72ae877b397e054de5300e10
|
|
|
|
|
|
| |
- Switch to Mono 6.8
PR: 258981
|
|
|
|
|
|
| |
- Switch to Mono 6.8
PR: 258982
|
|
|
|
|
| |
PR: 249304
Reported by: martin@waschbuesch.de
|
|
|
|
|
|
|
|
|
| |
$ ffmpeg ... -c:v hevc_qsv ...
[AVHWDeviceContext @ 0x8062d0140] Error initializing an MFX session: -3.
Device creation failed: -1313558101.
PR: 258976
Reported by: Yuichiro NAITO
|
|
|
|
|
|
| |
The samples are not built, so right now this is a leaf port
that is only a library with no consumers; we'll see if it gets
picked up by something.
|
|
|
|
|
|
|
|
|
|
|
|
| |
While qt5-multimedia **works** with gstreamer-gl, it's unexpected,
and not listed as a dependency. Sabotage the detection of gstreamer-gl
by breaking the include path it looks for.
We might consider adding gstreamer-gl to the dependencies, to
get better overall GL support, but that's a more involved change.
PR: 245909
Reported by: Martin Birgmeier
|
|
|
|
|
|
|
|
|
|
|
| |
Release announcement is at
https://lists.x.org/archives/wayland-devel/2021-September/041989.html
We skip over a bunch of intermediates, a little more than a year
of updates.
PR: 258931
Approved by: manu (x11@)
|
|
|
|
| |
Approved by: portmgr (blanket)
|
|
|
|
| |
Approved by: portmgr (blanket)
|
|
|
|
| |
Approved by: portmgr blanket
|
|
|
|
| |
Reported by: portscout
|
|
|
|
|
|
|
|
|
| |
py-pbr is at version 5.5.0.
Build error:
py38-os-brick-5.0.0 depends on package: py38-pbr>=5.5.1 - not found
Approved by: portmgr (build fix blanket)
|
|
|
|
|
|
|
|
|
| |
The configure script uses pkg-config to find the libzmq lib.
It fixes the following error:
configure: error: octave zeromq package requires zeromq library
Approved by: portmgr (build fix blanket)
|
|
|
|
|
|
|
|
|
|
| |
The Bitwarden CLI is a powerful, full-featured command-line interface
(CLI) tool to access and manage a Bitwarden vault. The CLI is written
with TypeScript and Node.js and can be run on Windows, macOS, and Linux
distributions. This port is using the Linux binary thanks to the Linux
binary compatibility provided by FreeBSD.
WWW: https://github.com/bitwarden/cli
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
GitHub seemed to regenerate the tarball, which changed its hash and
size. The contents are the same.
PR: 258955
Reported by: mandree
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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.
|
|
|
|
| |
Reported by: portscout
|
|
|
|
| |
Reported by: portscout
|
|
|
|
|
| |
PR: 258967
Approved by: moritz@schmi.tt (maintainer)
|
| |
|
| |
|