| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Reported by: fallout
(cherry picked from commit b9434eb314ff9ae9402e32b61bf18c1fe06802cf)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Qt 6.7 is out with lots of large and small improvements for all of us
who like to have fun when building modern applications and user
experiences, focusing on the expansion of supported platforms and
industry standards. This makes code written with Qt more sustainable
and brings more value in Qt as a long-term investment.
www/qt6-webengine is now based on Chromium version 118.0.5993.220.
Announcement: https://www.qt.io/blog/qt-6.7-released
Release note: https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.7.0/release-note.md
PySide6: Update to 6.7.0
PySide6 and its related components have been updated alongside the Qt
release for compatibility. Older versions will not build with Qt 6.7.x.
Announcement: https://www.qt.io/blog/qt-for-python-release-6.7
PyQt6: Update to 6.7.0
Minor Makefile cleanups and simplification of MASTER_SITES in pyqt.mk.
As with PySide6, older versions of PyQt6 will not build with Qt 6.7.x.
Announcement: https://www.riverbankcomputing.com/news/PyQt_v6.7.0_Released
PR: 278658
Exp-run by: antoine
MFH: 2024Q2
Security: e79cc4e2-12d7-11ef-83d8-4ccc6adda413,
c6f03ea6-12de-11ef-83d8-4ccc6adda413
(cherry picked from commit bef8e408ff183386912e86b7c9aee21923d37a6f)
|
| |
|
|
|
| |
MFH: 2024Q2
(cherry picked from commit fce0cc32720e61042bc675152b116f9e61532e92)
|
| |
|
|
|
| |
MFH: 2024Q2
(cherry picked from commit a0676cbde9ff7029f5f0af1c50135be5e669d325)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
By popular demand as this port is used by net-mgmt/unifi8.
I couldn't find any information on the internet that the binary really
does something which requires AVX. For example this discussion:
https://github.com/turnkeylinux/tracker/issues/1724
(cherry picked from commit 1707c0aac83aaf892c07bfc05573d1efa8ec5724)
PR: 277990
Requested by: glebius@
|
| |
|
|
| |
(cherry picked from commit acced1578840c5907401bbeb02f5cbafe609114d)
|
| |
|
|
|
| |
MFH: 2024Q2
(cherry picked from commit 91f781afd4292e9a950618c4bfa03f756d120d35)
|
| |
|
|
|
| |
MFH: 2024Q2
(cherry picked from commit 32b284679a1954ef1e0c0d52c4741d00e36dc6e0)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
disabled
This port uses "%s" in some SQL queries where '%s' should have been
used. When the DQS (double-quoted string) misfeatures of SQLite3 is
disabled, these queries fail and cause the error "no such column: %s".
Change these queries to fix evolution.
PR: 278249
Approved by: fluffy (gnome)
MFH: 2024Q2
(cherry picked from commit 50154e657e63e12df3938dcd7dc15b7e340f5a6f)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
After upgrading snappy 1.1.0 -> 1.2.0, mongodb50 fails to start:
ld-elf.so.1: /usr/local/bin/mongod: Undefined symbol "_ZN6snappy8CompressEPKcmPNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEE"
Apparentally turning off LTO fixes this.
(cherry picked from commit 9220f0b1125626b100a823b801cec4d8362ec523)
PR: 278254
|
| |
|
|
|
| |
ChangeLog: https://github.com/tidyverse/dbplyr/releases/tag/v2.5.0
PR: 278242
|
| |
|
|
|
| |
Changes:
https://www.mongodb.com/docs/manual/release-notes/7.0/#7.0.8---april-3--2024
|
| |
|
|
|
|
| |
- Add MARIADB and MYSQL options
Changes: https://metacpan.org/dist/Test-mysqld/changes
|
| |
|
|
| |
Changes: https://arrow.apache.org/release/
|
| |
|
|
| |
Changes: https://arrow.apache.org/release/
|
| |
|
|
| |
Changes: https://arrow.apache.org/release/
|
| |
|
|
| |
Changes: https://arrow.apache.org/release/
|
| |
|
|
| |
py-setuptools should be used rather than PY_SETUPTOOLS
|
| |
|
|
| |
ahash crate
|
| |
|
|
|
|
|
|
|
| |
* Swtich from PORTVERSION to DISTVERSION
* Update WWW entry
* Use USES= localbase:ldflags helper
PR: 278226
Reviewed by: gahr (maintainer)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a new variable DBD_MYSQL, use that in *_DEPENDS and add mysql to USES
where required. DBD_MYSQL will automatically set the correct DBD dependency.
In cd16748194e2 databases/p5-DBD-mysql was updated to 5.x, in 5.x the
support for MariaDB was removed and only MySQL >= 8.0 is supported.
In the 4.x releases MariaDB is still supported, according to upstream 4.x
will still be supported for a while [1], so use that for now when we detect
that MYSQL_FLAVOUR is set to mariadb. databases/p5-DBD-mysql4 was added in
d95f49cb3b54.
DBD:MariaDB would be another alternative, but migrating to it might need
more analysis than just staying with the 4.x releases of p5-DBD-mysql. This
thread on the amavis-users mailing list has a very good summary [2] from
the author of DBD:MariaDB.
This includes ideas and suggestions from vvd and mat. Thanks!
[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277889#c17
[2] https://lists.amavis.org/pipermail/amavis-users/2024-March/006823.html
PR: 275100, 277889
Reviewed by: vvd, mat
Fixes: cd16748194e2
Differential Revision: https://reviews.freebsd.org/D44662
|
| |
|
|
|
|
|
| |
Remove settings specific to i386 that have been dead (= disabled
and unused) since this port was created.
Approved by: portmgr blanket
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on i386
When building against libc++ 18, several iostream classes now get
inlined into C++ binaries for efficiency. But because the mysql ports
use -malign-double on non-powerpc architectures, this causes an ABI
problem with libc++.so, which has not been built with that flag, at
least on i386. This can cause segfaults during the build of the port.
If it is not the architecture default, as it is on amd64, -malign-double
should not be used without recompiling basically the entire userspace
runtime. Quoting the gcc docs:
> Warning: if you use the -malign-double switch, structures containing
> the above types are aligned differently than the published application
> binary interface specifications for the x86-32 and are not binary
> compatible with structures in code compiled without that switch.
Hence, remove -malign-double from CXXFLAGS for these ports.
PR: 277896
Approved by: maintainer timeout (2 weeks)
MFH: 2024Q1
|
| |
|
|
|
|
|
| |
databases/p5-DBD-mysql4 added in 95f49cb3b54aa5c685fb3ea73aaf1be76af6111
PR: 277889 275100
Approved by: flo, arrowd (mentor, implicit)
|
| |
|
|
|
|
|
|
|
| |
databases/p5-DBD-mysql4
databases/p5-DBD-mysql4 added in 95f49cb3b54aa5c685fb3ea73aaf1be76af6111
PR: 277889 275100
Approved by: flo, arrowd (mentor, implicit)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Submitter becomes maintainer
Provides a data.table backend for 'dplyr'. The goal of 'dtplyr' is to allow you
to write 'dplyr' code that is automatically translated to the equivalent, but
usually much faster, data.table code.
WWW: https://dtplyr.tidyverse.org/
Differential Revision: https://reviews.freebsd.org/D43735
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- Submitter becomes maintainer
A 'dplyr' back end for databases that allows you to work with remote database
tables as if they are in-memory data frames. Basic features works with any
database that has a 'DBI' back end; more advanced features require 'SQL'
translation to be provided by the package author.
WWW: https://dbplyr.tidyverse.org/
Differential Revision: https://reviews.freebsd.org/D43735
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
In new branch 5.x upstream removed support of the MariaDB and MySQL 5.7
and earlier:
https://github.com/perl5-dbi/DBD-mysql/issues/405#issuecomment-1818501464
This break a lot of installations with MariaDB.
Also DBD-MariaDB (databases/p5-DBD-MariaDB) isn't compatable with
DBD-mysql and most of ports doesn't support it.
PR: 277889 275100
Approved by: flo, arrowd (mentor, implicit)
Differential Revision: https://reviews.freebsd.org/D44524
|
| |
|
|
| |
Changes: https://github.com/dbcli/mycli/blob/main/changelog.md
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Orchestrator is a replication topology manager for MySQL.
Features include:
* The topology and status of the replication tree is automatically detected
and monitored.
* Either a GUI, CLI or API can be used to check the status and perform
operations.
* Supports automatic failover of the master, and the replication tree can
be fixed when servers in the tree fail - either manually or automatically.
* It is not dependent on any specific version or flavor of MySQL (MySQL,
Percona Server, MariaDB or even MaxScale binlog servers).
* Orchestrator supports many different types of topologies, from a single
master -> slave to complex multi-layered replication trees consisting of
hundreds of servers.
* Orchestrator can make topology changes and will do so based on the state
at that moment; it does not require a configuration to be defined with what
corresponds to the database topology.
* The GUI is not only there to report the status - one of the cooler things
you can do is change replication just by doing a drag and drop in the web
interface (of course you can do this and much more through the CLI and API
as well).
|
| |
|
|
|
|
|
|
|
|
|
|
| |
While I'm here,
- remove conditionals regarding llvm16 build fix as port build fine
without it.
- add test target
ChangeLog: https://cran.r-project.org/web/packages/RSQLite/news/news.html
Differential Revision: https://reviews.freebsd.org/D44592
|
| |
|
|
|
| |
- Update service arg initialize to initial, to match upstream
documentation
|
| |
|
|
|
| |
Changes: https://github.com/geoalchemy/geoalchemy2/releases
https://geoalchemy-2.readthedocs.io/en/stable/changelog.html
|
| |
|
|
| |
Changes: https://github.com/okbob/plpgsql_check/releases
|
| | |
|
| | |
|
| |
|
|
|
| |
ChangeLog: https://github.com/collerek/ormar/releases/tag/0.20.0
PR: 278070
|
| |
|
|
| |
Release notes: https://github.com/dalibo/pg_activity/releases/tag/v3.5.1
|
| |
|
|
| |
PR: 278139
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Alway build with base system compiler. In 2018 Makefile was changed
so GCC is used with i386. It seems to be workaround of build error,
But now build succeeds without GCC on i386 and all supported FreeBSD
versions.
* Remove options for external lua library and related patches. On
April 2022 upstream made incompatible change of bundled lua library
to fix vulnerability. As a result build got failed when external lua
library is enabled. Upstream said in commit message of their
repository that they took codes from lua repository. So I kept the
options with marking as broken hoping breakage will be solved in the
future. But it is still broken after two years and doesn't seem to
change.
* Remove TRIB option. When it is enabled ruby script named
redis-trib.rb is installed. But it just prints warning message that
it is no longer available and redis-cli should be used instead, and
exit. So it isn't usefull anymore.
* Fix post-patch-JEMALLOC-on target so proper line is replaced.
* Pet portclippy.
|
| | |
|
| |
|
|
|
| |
setting maintainer email to Eugene as aligned in the email
conversation.
|
| |
|
|
|
| |
Add databases/valkey, High-performance data structure server that
primarily serves key/value workloads.
|
| |
|
|
|
| |
I've joined ruby team. So pass maintainership of my rubygem ports to
ruby@ so members can maintain them.
|
| |
|
|
| |
Changes: https://github.com/mongodb/mongo-php-driver/releases/
|
| |
|
|
|
|
|
| |
- Resolve 14.x build issue
- Do not force use of admin socket
- Fix RESTAPI support
- Bump PORTREVISION
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Fix in CegoAdmScreen::TableSet::TableSet constructor,
SysUsage field added to indicate correct usage
for system, temp and app files
- Patch added for transaction handling in CegoTransactionManager::doCommit
and CegoTableManager::deleteDataTableEntry.
Just for tuple state COMMITTED, a rollback entry must be created,
otherwise double tuple delete may occur.
For tuple state INSERTED, tuple state is just set to OBSOLETE,
for tuple state OBSOLETE and DELETED, nothing has to be done.
In CegoTableManager::doCommit, tuple state just has to be set
to COMMITTED in case of INSERTED tuples
- Elimination of a cout in CegoQueryCache::QueryCacheEntry::cleanCache
|
| | |
|
| |
|
|
| |
PR: 278075
|