Bug 242864 - databases/mariadb104-server v11.3R Make fails with py37 vs 36 setuptools conflict
Summary: databases/mariadb104-server v11.3R Make fails with py37 vs 36 setuptools con...
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: Bernard Spil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-24 17:44 UTC by fidhleir99
Modified: 2023-04-10 12:31 UTC (History)
2 users (show)

See Also:
w.schwarzenfeld: maintainer-feedback? (brnrd)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fidhleir99 2019-12-24 17:44:12 UTC
===>  Installing for py37-setuptools-41.4.0_1
===>  Checking if py37-setuptools is already installed
===>   Registering installation for py37-setuptools-41.4.0_1 as automatic
Installing py37-setuptools-41.4.0_1...
pkg-static: py37-setuptools-41.4.0_1 conflicts with py36-setuptools-41.2.0 (installs files into the same place).  Problematic file: /usr/local/bin/easy_install
*** Error code 70
Stop.
make[7]: stopped in /usr/ports/devel/py-setuptools
*** Error code 1
Stop.
make[6]: stopped in /usr/ports/devel/py-Jinja2
*** Error code 1
Stop.
make[5]: stopped in /usr/ports/devel/py-Jinja2
*** Error code 1
Stop.
make[4]: stopped in /usr/ports/textproc/py-sphinx
*** Error code 1
Stop.
Comment 1 Bernard Spil freebsd_committer freebsd_triage 2019-12-25 11:36:16 UTC
Hi,

Can you please provide your MariaDB config (`make showconfig`) and other (e.g. /etc/make.conf) settings?
Comment 2 fidhleir99 2019-12-31 12:09:14 UTC
(In reply to Bernard Spil from comment #1)

I don't have an active make.conf file.  I generally choose defaults, if I can, to maximise the likelihood of a lot of QA having been done.  That doesn't always save me, of course.

Apropos makeconfig:  thinking OQGRAPH offered more than it does, I turned it on, as reflected here.  And, not being interested in GSSAPI, I *thought* I turned it off, but, oddly, that's not reflected here.

===> The following configuration options are available for mariadb104-server-10.4.11:
     CONNECT_EXTRA=on: Enable ODBC and XML in CONNECT engine
     DOCS=on: Build and/or install documentation
     WSREP=on: Build wsrep clustering
====> Optional page compression
     LZ4=on: LZ4 compression support
     LZO=off: LZO compression support
     SNAPPY=off: Snappy compression library support
     ZSTD=off: Zstandard compression support (RocksDB only)
====> Optional MariaDB storage engines
     INNOBASE=on: InnoDB default engine
     MROONGA=on: Mroonga Full Text Search engine
     OQGRAPH=on: Open Query Graph Computation engine
     ROCKSDB=off: RocksDB LSM engine (Alpha)
     SPHINX=on: SphinxSE engine
     SPIDER=on: Partitioning and XA-transactions engine
     TOKUDB=off: Fractal tree index tree data structure engine
====> Optional Mroonga features
     ZMQ=off: ZeroMQ support
     MSGPACK=off: MsgPack support
====> GSSAPI Security API support: you have to select exactly one of them
     GSSAPI_BASE=on: GSSAPI support via base system (needs Kerberos)
     GSSAPI_HEIMDAL=off: GSSAPI support via security/heimdal
     GSSAPI_MIT=off: GSSAPI support via security/krb5
     GSSAPI_NONE=off: Disable GSSAPI support
===> Use 'make config' to modify these settings
Comment 3 Bernard Spil freebsd_committer freebsd_triage 2020-07-11 20:31:04 UTC
Is this still a problem?

Closing on 2020-08-01 otherwise
Comment 4 Bernard Spil freebsd_committer freebsd_triage 2023-04-10 12:31:29 UTC
MariaDB 10.4 is deprecated, use newer versions of the port