Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
Not every system has getopt_long_only.
|
|
Bump PKGREVISION.
|
|
Fix man page installation path.
Clean up some pkglint.
Bump PKGREVISION.
|
|
Successor ntopng is already in pkgsrc.
Ok adam@
|
|
Bump PKGREVISION
|
|
Last release from 2011, no upstream activity since 2012, does not build
in any bulk builds I could find.
|
|
Last release from 2004, no upstream activity, does not build on NetBSD 9+
and most other platforms
|
|
Should fix build on NetBSD<9.99.17
|
|
|
|
CVE-2022-0907 CVE-2022-0909
bump PKGREVISION again...
|
|
|
|
This is tiff-4.3.0nb1.
|
|
|
|
This fixes a security bug where TLS certs are not verified properly.
|
|
|
|
|
|
This needs major work, it doesn't have anything to do with cal3d's
tarball (I guess broken with the last update of cal3d, a year ago)
|
|
|
|
tries to use directory before it exists
blib/lib/auto/share/dist/Padre-Plugin-XS/locale isn't a directory at /usr/pkg/lib/perl5/vendor_perl/5.34.0/Locale/Msgfmt.pm line 21
|
|
|
|
|
|
Does not build, and the openafs package has a newer version
|
|
|
|
NetBSD has a base system fuse_opt.h with an error. see
http://mail-index.netbsd.org/tech-userlevel/2022/03/23/msg013349.html
Pull pkgsrc's FUSE buildlink3.mk to make sure we link with the right header
cVS: ----------------------------------------------------------------------
|
|
This includes two fixes submitted upstream:
https://github.com/LinearTapeFileSystem/ltfs/pull/346
https://github.com/LinearTapeFileSystem/ltfs/pull/345
While there, update the message about NetBSD requirement to drop
informations about now unsupported releases, and require NetBSD >= 8.0
|
|
a result of running mkpatches after 'make configure'.
|
|
|
|
Using upstream patch.
This bug was reported by Danilo Ramos of Eideticom, Inc. It has
lain in wait 13 years before being found! The bug was introduced
in zlib 1.2.2.2, with the addition of the Z_FIXED option. That
option forces the use of fixed Huffman codes. For rare inputs with
a large number of distant matches, the pending buffer into which
the compressed data is written can overwrite the distance symbol
table which it overlays. That results in corrupted output due to
invalid distances, and can result in out-of-bound accesses,
crashing the application.
The fix here combines the distance buffer and literal/length
buffers into a single symbol buffer. Now three bytes of pending
buffer space are opened up for each literal or length/distance
pair consumed, instead of the previous two bytes. This assures
that the pending buffer cannot overwrite the symbol table, since
the maximum fixed code compressed length/distance is 31 bits, and
since there are four bytes of pending space for every three bytes
of symbol space.
Bump PKGREVISION.
Fix some pkglint while here.
|
|
|
|
This sets the working directory to / before issuing commands to Gitea.
Fix from the pgsql script; it addresses the following issue when
managing Gitea:
# /etc/rc.d/gitea restart
Stopping gitea.
sh: Cannot determine current working directory
Starting gitea.
sh: Cannot determine current working directory
(and then Gitea not starting again)
Bumps PKGREVISION.
During freeze, but leaf package AFAICT.
Tested on NetBSD/amd64.
|
|
|
|
This is a micro-update; upstream change are minor/bugfixes. (And,
upstream has a track record of micro updates not breaking anything.)
|
|
|
|
|
|
|
|
|
|
Bump PKGREVISION.
Fix some pkglint while here.
|
|
it gives a different file every day or so
|
|
The new release of nushell, 0.60.0 has major breaking changes and currently
does not build on NetBSD.
Making it build again is over my head.
|
|
|
|
Security update - from upstream's release nites:
Changes in 3.1.13
~~~~~~~~~~~~~~~~~
* FIX: CVE-2021-31439
* FIX: CVE-2022-23121
* FIX: CVE-2022-23123
* FIX: CVE-2022-23122
* FIX: CVE-2022-23125
* FIX: CVE-2022-23124
* FIX: CVE-2022-0194
* FIX: afpd: make a variable declaration a definition
* UPD: Remove bundled libevent
|
|
|
|
Don't bother listing specific supported platforms, as this changes from
release to release, and gets out of date quickly.
|
|
|
|
|
|
Changes since 21.4.4:
Python packages that declare 2.7 as an incompatible Python version no
longer need to provide a rationale for this since it is common knowledge
that Python 2.7 is old and therefore unsupported by many modern
packages.
|
|
|
|
|