Re: State of mail/postfix-sasl for older FreeBSD
From: Jeremy Chadwick via freebsd-ports Subject: State of mail/postfix-sasl for older FreeBSD Date: Tue, 11 May 2021 13:51:26 + > That said: I see mail/postfix-sasl as orphaned, but no mail/postfix35-sasl > stub port. I submmitted following bug report. Bug 255809 mail/postfix35: Flavorize https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255809 Attatched patch flavorizes mail/postfix35 and add ldap_sasl and sasl flovors which correspond to mail/postfix-ldap-sasl and mail/postfix-sasl. > Understand that there's a large percentage of FreeBSD users who do not > want to deal with poudrier and its nonsense just to get something as > basic as SASL support in their MTA. Stub ports are important for this > very reason. In this case poudriere has nothing to do with the problem. Whatever tool you use you can't build slave port of mail/postfix35 because there isn't such one. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: `make makesum` fails with lang/pyton-doc-html
From: Yasuhiro Kimura
Subject: Re: `make makesum` fails with lang/pyton-doc-html
Date: Tue, 11 May 2021 11:34:47 +0900 (JST)
> I modified Danilo' patch as following and confirmed `make makesum`
> works as is expected with it.
>
> --
> diff --git a/lang/python-doc-html/Makefile b/lang/python-doc-html/Makefile
> index 48c696c08995..6b0e9d5fadc5 100644
> --- a/lang/python-doc-html/Makefile
> +++ b/lang/python-doc-html/Makefile
> @@ -3,7 +3,7 @@
> PORTNAME=python-doc-${DOCFORMAT}
> PORTVERSION= ${PYTHON_PORTVERSION}
> CATEGORIES= lang python
> -MASTER_SITES=PYTHON/ftp/python/doc/${PORTVERSION} \
> +MASTER_SITES?= PYTHON/ftp/python/doc/${PORTVERSION} \
> PYTHON/ftp/python/doc/current
> DISTNAME=python-${PORTVERSION}-docs-${DOCFORMAT}
> DIST_SUBDIR= python
> @@ -38,7 +38,7 @@ _VERS!= ${MAKE} -V _PYTHON_VERSIONS:O
>
> all_python_versions:
> .for v in ${_VERS}
> - @${MAKE} -V PYTHON_PORTVERSION DEFAULT_VERSIONS=python=${v}
> + @${MAKE} -C ${PORTSDIR}/lang/python${v:S/.//} -V PYTHON_PORTVERSION
> .endfor
>
> .if make(makesum)
> @@ -54,6 +54,7 @@ DISTFILES+=
> python-${v}-docs-${f}${EXTRACT_SUFX}:${v:S/./x/g},DEFAULT
> .endfor
> .endfor
> MASTER_SITES+= PYTHON/ftp/python/doc/current
> +.export MASTER_SITES
> .endif
>
> pre-install:
> --
>
> But I found another issue. If I execute `make makesum`, distinfo of
> python 2.7 document archive files changes.
>
> --
> yasu@rolling-vm-freebsd2[1511]% pwd
> /usr/ports/lang/python-doc-html
> yasu@rolling-vm-freebsd2[1512]% make makesum
> ===> python-doc-html-3.9.4 depends on file: /usr/local/sbin/pkg - found
> ===> Fetching all distfiles required by python-doc-html-3.9.4 for building
> yasu@rolling-vm-freebsd2[1513]% git diff
> diff --git a/lang/python-doc-html/distinfo b/lang/python-doc-html/distinfo
> index ba5ecf5b1a03..4f5ebc4b4501 100644
> --- a/lang/python-doc-html/distinfo
> +++ b/lang/python-doc-html/distinfo
> @@ -1,12 +1,12 @@
> -TIMESTAMP = 1618020033
> -SHA256 (python/python-2.7.18-docs-html.tar.bz2) =
> 3d05142817615e77cec99f686dca58289bbfe008af22f94a93262e8663db81c7
> -SIZE (python/python-2.7.18-docs-html.tar.bz2) = 4732851
> -SHA256 (python/python-2.7.18-docs-pdf-a4.tar.bz2) =
> ead357695e43c824ae1a83dd6cd3b4a47215658f3fa20111726ff7ef16a16dd2
> -SIZE (python/python-2.7.18-docs-pdf-a4.tar.bz2) = 11455585
> -SHA256 (python/python-2.7.18-docs-pdf-letter.tar.bz2) =
> 0e1259b379982ceb623f25af9a15ab3d9fcd054b5efcb9d5c173404f7b80048a
> -SIZE (python/python-2.7.18-docs-pdf-letter.tar.bz2) = 11455989
> -SHA256 (python/python-2.7.18-docs-text.tar.bz2) =
> c2396b36632ecdefa3fbf9f73c80641c315e8d4a515da5e6616f4450e0ca74ff
> -SIZE (python/python-2.7.18-docs-text.tar.bz2) = 1633624
> +TIMESTAMP = 1620699906
> +SHA256 (python/python-2.7.18-docs-html.tar.bz2) =
> 20445e9a571cacdd350f702f0980e4dc559b6ff81f1d69affe9b0a862fef2f0e
> +SIZE (python/python-2.7.18-docs-html.tar.bz2) = 4634932
> +SHA256 (python/python-2.7.18-docs-pdf-a4.tar.bz2) =
> dbac6953e48aac341351067ba0938393e415b10bf48ac8cbbc7247deaf13ab67
> +SIZE (python/python-2.7.18-docs-pdf-a4.tar.bz2) = 11486967
> +SHA256 (python/python-2.7.18-docs-pdf-letter.tar.bz2) =
> 565971040db8994630fd5c2447e45c38428cfb22a7845cd2620160daf2c60b1e
> +SIZE (python/python-2.7.18-docs-pdf-letter.tar.bz2) = 11486126
> +SHA256 (python/python-2.7.18-docs-text.tar.bz2) =
> c86f5b5a2bd8f90158523efd350198d6cde7353965ef5a6ca5e54e5174af47f2
> +SIZE (python/python-2.7.18-docs-text.tar.bz2) = 1631043
> SHA256 (python/python-3.6.13-docs-html.tar.bz2) =
> 13e36aea543d2ab55d116a2c150684214c0be37992d71aba126cdf58d342adac
> SIZE (python/python-3.6.13-docs-html.tar.bz2) = 6016532
> SHA256 (python/python-3.6.13-docs-pdf-a4.tar.bz2) =
> eb278d548bf1646c85373dde006e42c68d7849c16db2d2a2fbcae9086c4279b5
> yasu@rolling-vm-freebsd2[1514]%
> --
>
> Does this mean documetn archive files of Python 2.7.18 are rerolled?
I submitted following bug reports on Bugzilla.
Bug 255767 lang/python-doc-html: Fix `make makesum`
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255767
Bug 255782 lang/python-doc-html: Fix distinfo of 2.7.18 document archive files
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255782
---
Yasuhiro Kimura
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: `make makesum` fails with lang/pyton-doc-html
From: Yasuhiro Kimura
Subject: Re: `make makesum` fails with lang/pyton-doc-html
Date: Tue, 11 May 2021 08:21:28 +0900 (JST)
> Bad news. The problem is found when I tried to update
> lang/python-doc-html/distinfo for Python 3.8.10 and 3.9.5.
>
(snip)
>
> Since lang/python-doc-html/Makefile and lang/python38/Makefile.version
> are modified in this case, information of files related to
> lang/python38 should be updated in lang/python-doc-html/distinfo. But
> as you can see information of files related to lang/python27 is also
> updated.
I modified Danilo' patch as following and confirmed `make makesum`
works as is expected with it.
--
diff --git a/lang/python-doc-html/Makefile b/lang/python-doc-html/Makefile
index 48c696c08995..6b0e9d5fadc5 100644
--- a/lang/python-doc-html/Makefile
+++ b/lang/python-doc-html/Makefile
@@ -3,7 +3,7 @@
PORTNAME= python-doc-${DOCFORMAT}
PORTVERSION= ${PYTHON_PORTVERSION}
CATEGORIES=lang python
-MASTER_SITES= PYTHON/ftp/python/doc/${PORTVERSION} \
+MASTER_SITES?= PYTHON/ftp/python/doc/${PORTVERSION} \
PYTHON/ftp/python/doc/current
DISTNAME= python-${PORTVERSION}-docs-${DOCFORMAT}
DIST_SUBDIR= python
@@ -38,7 +38,7 @@ _VERS!= ${MAKE} -V _PYTHON_VERSIONS:O
all_python_versions:
.for v in ${_VERS}
- @${MAKE} -V PYTHON_PORTVERSION DEFAULT_VERSIONS=python=${v}
+ @${MAKE} -C ${PORTSDIR}/lang/python${v:S/.//} -V PYTHON_PORTVERSION
.endfor
.if make(makesum)
@@ -54,6 +54,7 @@ DISTFILES+=
python-${v}-docs-${f}${EXTRACT_SUFX}:${v:S/./x/g},DEFAULT
.endfor
.endfor
MASTER_SITES+= PYTHON/ftp/python/doc/current
+.export MASTER_SITES
.endif
pre-install:
--
But I found another issue. If I execute `make makesum`, distinfo of
python 2.7 document archive files changes.
--
yasu@rolling-vm-freebsd2[1511]% pwd
/usr/ports/lang/python-doc-html
yasu@rolling-vm-freebsd2[1512]% make makesum
===> python-doc-html-3.9.4 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by python-doc-html-3.9.4 for building
yasu@rolling-vm-freebsd2[1513]% git diff
diff --git a/lang/python-doc-html/distinfo b/lang/python-doc-html/distinfo
index ba5ecf5b1a03..4f5ebc4b4501 100644
--- a/lang/python-doc-html/distinfo
+++ b/lang/python-doc-html/distinfo
@@ -1,12 +1,12 @@
-TIMESTAMP = 1618020033
-SHA256 (python/python-2.7.18-docs-html.tar.bz2) =
3d05142817615e77cec99f686dca58289bbfe008af22f94a93262e8663db81c7
-SIZE (python/python-2.7.18-docs-html.tar.bz2) = 4732851
-SHA256 (python/python-2.7.18-docs-pdf-a4.tar.bz2) =
ead357695e43c824ae1a83dd6cd3b4a47215658f3fa20111726ff7ef16a16dd2
-SIZE (python/python-2.7.18-docs-pdf-a4.tar.bz2) = 11455585
-SHA256 (python/python-2.7.18-docs-pdf-letter.tar.bz2) =
0e1259b379982ceb623f25af9a15ab3d9fcd054b5efcb9d5c173404f7b80048a
-SIZE (python/python-2.7.18-docs-pdf-letter.tar.bz2) = 11455989
-SHA256 (python/python-2.7.18-docs-text.tar.bz2) =
c2396b36632ecdefa3fbf9f73c80641c315e8d4a515da5e6616f4450e0ca74ff
-SIZE (python/python-2.7.18-docs-text.tar.bz2) = 1633624
+TIMESTAMP = 1620699906
+SHA256 (python/python-2.7.18-docs-html.tar.bz2) =
20445e9a571cacdd350f702f0980e4dc559b6ff81f1d69affe9b0a862fef2f0e
+SIZE (python/python-2.7.18-docs-html.tar.bz2) = 4634932
+SHA256 (python/python-2.7.18-docs-pdf-a4.tar.bz2) =
dbac6953e48aac341351067ba0938393e415b10bf48ac8cbbc7247deaf13ab67
+SIZE (python/python-2.7.18-docs-pdf-a4.tar.bz2) = 11486967
+SHA256 (python/python-2.7.18-docs-pdf-letter.tar.bz2) =
565971040db8994630fd5c2447e45c38428cfb22a7845cd2620160daf2c60b1e
+SIZE (python/python-2.7.18-docs-pdf-letter.tar.bz2) = 11486126
+SHA256 (python/python-2.7.18-docs-text.tar.bz2) =
c86f5b5a2bd8f90158523efd350198d6cde7353965ef5a6ca5e54e5174af47f2
+SIZE (python/python-2.7.18-docs-text.tar.bz2) = 1631043
SHA256 (python/python-3.6.13-docs-html.tar.bz2) =
13e36aea543d2ab55d116a2c150684214c0be37992d71aba126cdf58d342adac
SIZE (python/python-3.6.13-docs-html.tar.bz2) = 6016532
SHA256 (python/python-3.6.13-docs-pdf-a4.tar.bz2) =
eb278d548bf1646c85373dde006e42c68d7849c16db2d2a2fbcae9086c4279b5
yasu@rolling-vm-freebsd2[1514]%
--
Does this mean documetn archive files of Python 2.7.18 are rerolled?
---
Yasuhiro Kimura
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: `make makesum` fails with lang/pyton-doc-html
From: Yasuhiro Kimura
Subject: Re: `make makesum` fails with lang/pyton-doc-html
Date: Tue, 11 May 2021 03:03:51 +0900 (JST)
> Thank you for patch. I applied it to 61daf777c5d6 of main and now
> `make makesum` works fine.
Bad news. The problem is found when I tried to update
lang/python-doc-html/distinfo for Python 3.8.10 and 3.9.5.
--
yasu@rolling-vm-freebsd2[1443]% git status
On branch main
Your branch is up to date with 'origin/main'.
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified: lang/python-doc-html/Makefile
modified: lang/python38/Makefile.version
no changes added to commit (use "git add" and/or "git commit -a")
yasu@rolling-vm-freebsd2[1444]% git diff
diff --git a/lang/python-doc-html/Makefile b/lang/python-doc-html/Makefile
index 48c696c08995..b4c675e1729d 100644
--- a/lang/python-doc-html/Makefile
+++ b/lang/python-doc-html/Makefile
@@ -3,7 +3,7 @@
PORTNAME= python-doc-${DOCFORMAT}
PORTVERSION= ${PYTHON_PORTVERSION}
CATEGORIES=lang python
-MASTER_SITES= PYTHON/ftp/python/doc/${PORTVERSION} \
+MASTER_SITES?= PYTHON/ftp/python/doc/${PORTVERSION} \
PYTHON/ftp/python/doc/current
DISTNAME= python-${PORTVERSION}-docs-${DOCFORMAT}
DIST_SUBDIR= python
@@ -54,6 +54,7 @@ DISTFILES+=
python-${v}-docs-${f}${EXTRACT_SUFX}:${v:S/./x/g},DEFAULT
.endfor
.endfor
MASTER_SITES+= PYTHON/ftp/python/doc/current
+.export MASTER_SITES
.endif
pre-install:
diff --git a/lang/python38/Makefile.version b/lang/python38/Makefile.version
index 5587d0177cf9..12ed93354d24 100644
--- a/lang/python38/Makefile.version
+++ b/lang/python38/Makefile.version
@@ -2,4 +2,4 @@
# Do not forget to update python documentation (lang/python-doc-*)
# Run "make -C lang/python-doc-html makesum"
-PYTHON_PORTVERSION=3.8.9
+PYTHON_PORTVERSION=3.8.10
yasu@rolling-vm-freebsd2[1445]% make -C lang/python-doc-html makesum
===> python-doc-html-3.9.4 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by python-doc-html-3.9.4 for building
yasu@rolling-vm-freebsd2[1446]% git diff -- lang/python-doc-html/distinfo
diff --git a/lang/python-doc-html/distinfo b/lang/python-doc-html/distinfo
index ba5ecf5b1a03..6d35d0eb6a52 100644
--- a/lang/python-doc-html/distinfo
+++ b/lang/python-doc-html/distinfo
@@ -1,12 +1,12 @@
-TIMESTAMP = 1618020033
-SHA256 (python/python-2.7.18-docs-html.tar.bz2) =
3d05142817615e77cec99f686dca58289bbfe008af22f94a93262e8663db81c7
-SIZE (python/python-2.7.18-docs-html.tar.bz2) = 4732851
-SHA256 (python/python-2.7.18-docs-pdf-a4.tar.bz2) =
ead357695e43c824ae1a83dd6cd3b4a47215658f3fa20111726ff7ef16a16dd2
-SIZE (python/python-2.7.18-docs-pdf-a4.tar.bz2) = 11455585
-SHA256 (python/python-2.7.18-docs-pdf-letter.tar.bz2) =
0e1259b379982ceb623f25af9a15ab3d9fcd054b5efcb9d5c173404f7b80048a
-SIZE (python/python-2.7.18-docs-pdf-letter.tar.bz2) = 11455989
-SHA256 (python/python-2.7.18-docs-text.tar.bz2) =
c2396b36632ecdefa3fbf9f73c80641c315e8d4a515da5e6616f4450e0ca74ff
-SIZE (python/python-2.7.18-docs-text.tar.bz2) = 1633624
+TIMESTAMP = 1620688048
+SHA256 (python/python-3.8.10-docs-html.tar.bz2) =
5a24209934220c13e9ed531c50ae4ba80d7179fbbee383949873be785fe5b27d
+SIZE (python/python-3.8.10-docs-html.tar.bz2) = 6604538
+SHA256 (python/python-3.8.10-docs-pdf-a4.tar.bz2) =
a8e3e50608f7c99525040eee88d3dfea8d85ad6f6962a1d96d5e1d6e434ec60b
+SIZE (python/python-3.8.10-docs-pdf-a4.tar.bz2) = 14748468
+SHA256 (python/python-3.8.10-docs-pdf-letter.tar.bz2) =
dd463cd678e3d1e911dd9cc06fdc7967cf7c8754d76959a2a3075dcaa04ff8ca
+SIZE (python/python-3.8.10-docs-pdf-letter.tar.bz2) = 14858809
+SHA256 (python/python-3.8.10-docs-text.tar.bz2) =
b5e2151e5cfb41bce2a71b5a8c97e0315740656e4d5aeb9dbbf72cc21a4eb99b
+SIZE (python/python-3.8.10-docs-text.tar.bz2) = 2422201
SHA256 (python/python-3.6.13-docs-html.tar.bz2) =
13e36aea543d2ab55d116a2c150684214c0be37992d71aba126cdf58d342adac
SIZE (python/python-3.6.13-docs-html.tar.bz2) = 6016532
SHA256 (python/python-3.6.13-docs-pdf-a4.tar.bz2) =
eb278d548bf1646c85373dde006e42c68d7849c16db2d2a2fbcae9086c4279b5
@@ -23,14 +23,14 @@ SHA256 (python/python-3.7.10-docs-pdf-letter.tar.bz2) =
96de9c6e92754e8f0ab27cb7
SIZE (python/python-3.7.10-docs-pdf-letter.tar.bz2) = 14359866
SHA256 (python/python-3.7.10-docs-text.tar.bz2) =
cf6e58134550e92b6e25d365010834c8abdbed1479edf7a566fa841fcec6b960
SIZE (python/python-3.7.10-docs-text.tar.bz2) = 2293462
-SHA256 (python/python-3.8.9-docs-html.tar.bz2) =
0bece0235bdbddea03bfb855ee192ae9889745585dc47bfcae2e29856d212c09
-SIZE (python/python-3.8.9-docs-html.tar.bz2) = 6593775
-SHA256 (python/python-3.8.9-docs-pdf-a4.tar.bz2) =
b018e3ad4253207929d622401d9db76ea0d8782d516c431309294d9b3a8c2f8f
-SIZE (python/python-3.8.9-docs-pd
Re: Build of Python 3.8.10/3.9.5 fails on 12.2-RELEASE
From: Yasuhiro Kimura Subject: Build of Python 3.8.10/3.9.5 fails on 12.2-RELEASE Date: Mon, 10 May 2021 16:29:03 +0900 (JST) > I submitted patches to update lang/python3[89] to 3.8.10/3.9.5 > respectively. > > Bug 255729 - lang/python38: Update to 3.8.10 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255729 > Bug 255730 - lang/python39: Update to 3.9.5 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255730 > > I created them on 13.0-RELEASE. But after submitting them I found > build of them fail on 12.2-RELEASE as following. > > -- > /wrkdirs/usr/ports/lang/python38/work/Python-3.8.10/Modules/_ssl.c:3118:27: > error: implicit declaration of function 'SSLv3_method' is invalid in C99 > [-Werror,-Wimplicit-function-declaration] > ctx = SSL_CTX_new(SSLv3_method()); > ^ > /wrkdirs/usr/ports/lang/python38/work/Python-3.8.10/Modules/_ssl.c:3118:27: > warning: incompatible integer to pointer conversion passing 'int' to > parameter of type 'const SSL_METHOD *' (aka 'const struct ssl_method_st *') > [-Wint-conversion] > ctx = SSL_CTX_new(SSLv3_method()); > ^~ > /usr/include/openssl/ssl.h:1503:47: note: passing argument to parameter > 'meth' here > __owur SSL_CTX *SSL_CTX_new(const SSL_METHOD *meth); > ^ > 2 warnings and 1 error generated. > -- > > Full build logs. > > 3.8.10 on 12.2-RELEASE: > https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/122amd64-default-python/2021-05-10_11h21m50s/logs/python38-3.8.10.log > 3.8.10 on 13.0-RELEASE: > https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/130amd64-default-python/2021-05-10_11h24m03s/logs/python38-3.8.10.log > 3.9.5 on 12.2-RELEASE: > https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/122amd64-default-python/2021-05-10_11h26m11s/logs/python39-3.9.5.log > 3.9.5 on 13.0-RELEASE: > https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/130amd64-default-python/2021-05-10_11h28m01s/logs/python39-3.9.5.log > > Futher, build also succeeds with 14-CURRENT and 11.4-RELEASE. So it > fails only with 12.2-RELEASE. > > Since FreeBSD 12 or later use OpenSSL 1.1.1, it means build fails with > OpenSSL 1.1.1 in one case but succeeds in other cases. It seems quite > strange for me. > > Any suggestions? I investigated repository of Python and found following commits (bpo-43799) are the source of the problem. [3.8] bpo-43799: OpenSSL 3.0.0: declare OPENSSL_API_COMPAT 1.1.1 (GH-25329) (GH-25383) https://github.com/python/cpython/commit/b71aaa0df0f3a9640b034b4774651cd8c54d2fb9 [3.9] bpo-43799: OpenSSL 3.0.0: declare OPENSSL_API_COMPAT 1.1.1 (GH-25329) (GH-25382) https://github.com/python/cpython/commit/7d9d5bf863bb0af26b74b0732ab89b2053d2fbec I created patches to revert these commits and added them to both ports. Then they can be built fine with 12.2-RELEASE. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: `make makesum` fails with lang/pyton-doc-html
From: "Danilo G. Baio" Subject: Re: `make makesum` fails with lang/pyton-doc-html Date: Mon, 10 May 2021 11:25:23 -0300 > Hi. > > Take a look on [1], it was working last time I checked. > > If it's ok, I'll open a review, please let me know. > > More details about that on [2] and [3]. > > 1 - https://people.freebsd.org/~dbaio/python-doc-html-distinfo.patch > 2 - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249063 > 3 - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249537 Thank you for patch. I applied it to 61daf777c5d6 of main and now `make makesum` works fine. Best Regards. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
`make makesum` fails with lang/pyton-doc-html
Hello, I tried to update lang/pyton-doc-html and found `make makesum` fails as following. -- yasu@rolling-vm-freebsd2[1242]% pwd /usr/ports yasu@rolling-vm-freebsd2[1243]% git status On branch main Your branch is up to date with 'origin/main'. nothing to commit, working tree clean yasu@rolling-vm-freebsd2[1244]% make -C lang/python-doc-html makesum /usr/ports ===> python-doc-html-3.9.4 depends on file: /usr/local/sbin/pkg - found => python-3.8.9-docs-html.tar.bz2 doesn't seem to exist in /net/freebsd/ports/distfiles/python. ===> /!\ Warning /!\ The :3x8x9 group used for python-3.8.9-docs-html.tar.bz2 is missing from MASTER_SITES. Check for typos, or errors. => Attempting to fetch https://www.python.org/ftp/python/doc/3.9.4/python-3.8.9-docs-html.tar.bz2 fetch: https://www.python.org/ftp/python/doc/3.9.4/python-3.8.9-docs-html.tar.bz2: Not Found => Attempting to fetch https://www.python.org/ftp/python/doc/current/python-3.8.9-docs-html.tar.bz2 fetch: https://www.python.org/ftp/python/doc/current/python-3.8.9-docs-html.tar.bz2: Not Found => Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/python/python-3.8.9-docs-html.tar.bz2 fetch: http://distcache.FreeBSD.org/ports-distfiles/python/python-3.8.9-docs-html.tar.bz2: Not Found => Couldn't fetch it - please try to retrieve this => port manually into /net/freebsd/ports/distfiles/python and try again. *** Error code 1 Stop. make[1]: stopped in /usr/ports/lang/python-doc-html *** Error code 1 Stop. make: stopped in /usr/ports/lang/python-doc-html yasu@rolling-vm-freebsd2[1245]% ------ What's wrong? --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Build of Python 3.8.10/3.9.5 fails on 12.2-RELEASE
Hello, I submitted patches to update lang/python3[89] to 3.8.10/3.9.5 respectively. Bug 255729 - lang/python38: Update to 3.8.10 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255729 Bug 255730 - lang/python39: Update to 3.9.5 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255730 I created them on 13.0-RELEASE. But after submitting them I found build of them fail on 12.2-RELEASE as following. -- /wrkdirs/usr/ports/lang/python38/work/Python-3.8.10/Modules/_ssl.c:3118:27: error: implicit declaration of function 'SSLv3_method' is invalid in C99 [-Werror,-Wimplicit-function-declaration] ctx = SSL_CTX_new(SSLv3_method()); ^ /wrkdirs/usr/ports/lang/python38/work/Python-3.8.10/Modules/_ssl.c:3118:27: warning: incompatible integer to pointer conversion passing 'int' to parameter of type 'const SSL_METHOD *' (aka 'const struct ssl_method_st *') [-Wint-conversion] ctx = SSL_CTX_new(SSLv3_method()); ^~ /usr/include/openssl/ssl.h:1503:47: note: passing argument to parameter 'meth' here __owur SSL_CTX *SSL_CTX_new(const SSL_METHOD *meth); ^ 2 warnings and 1 error generated. -- Full build logs. 3.8.10 on 12.2-RELEASE: https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/122amd64-default-python/2021-05-10_11h21m50s/logs/python38-3.8.10.log 3.8.10 on 13.0-RELEASE: https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/130amd64-default-python/2021-05-10_11h24m03s/logs/python38-3.8.10.log 3.9.5 on 12.2-RELEASE: https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/122amd64-default-python/2021-05-10_11h26m11s/logs/python39-3.9.5.log 3.9.5 on 13.0-RELEASE: https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/130amd64-default-python/2021-05-10_11h28m01s/logs/python39-3.9.5.log Futher, build also succeeds with 14-CURRENT and 11.4-RELEASE. So it fails only with 12.2-RELEASE. Since FreeBSD 12 or later use OpenSSL 1.1.1, it means build fails with OpenSSL 1.1.1 in one case but succeeds in other cases. It seems quite strange for me. Any suggestions? --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x,Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
From: Stefan Esser
Subject: Re: Making a port to use OpenSSL of ports collection on FreeBSD
11.x,Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
Date: Wed, 5 May 2021 18:55:47 +0200
>> You misunderstand my intention. What I would like to do is to make a
>> port use security/openssl instead of base OpenSSL even if user sets
>> 'DEFAULT_VERSIONS+=ssl=base' in /etc/make.conf (or user doesn't
>> customize setting about ssl at all).
>
> You can mark the port as broken if the user has selected "base" and
> this is incompatible with the port's requirements. E.g.:
>
> .include
>
> .if ${SSL_DEFAULT} == base
> BROKEN_FreeBSD_11= OpenSSL 1.1 required
> .endif
>
> .include
>
> You can of course add a better message, and the user can decide to
> try the compilation again after changing the default. But this will
> of course prevent the building of official packages for FreeBSD-11.
>
>> As I wrote previous mail, if 'USES=python:3.8+' is specified in
>> Makefile of a port, lang/python38 is used for the port event if user
>> adds 'DEFAULT_VERSIONS+=python=3.7' in /etc/make.conf. I'm looking for
>> similar way about ssl setting.
>
> You could add a dependency on the openssl port and make sure, that
> the port's include file and library is used in preference of the
> base version on FreeBSD-11.
>
> But you have to consider the risk of mixing references to the base and
> the ports version in one binary (e.g. other libraries are linked in that
> had been built against the base version).
Thank you for explanation. The risk certainly cannot be ignored. So
the best practice is
1. Mark BROKEN if system is FreeBSD 11.x and SSL_DEFAULT is base.
2. For uses who want to used a port on FreeBSD 11.x with base OpenSSL,
copy it to other name before updating it.
And before I came to this conclusion, I noticed that the port in
question was already updated exactly this way;-).
---
Yasuhiro Kimura
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
From: Chris Subject: Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x Date: Wed, 05 May 2021 08:03:00 -0700 > I ran into a similar situation requiring freebsd 11 users not use > SSL from base, and I simply used a conditional based against freebsd > version, that also included a RUN_DEPENDS on security/openssl > Wouldn't that work in your case? > > --Chris Probably only adding security/openssl to *_DEPENDS isn't enough. If you look at Mk/Uses/ssl.mk, you'll find the path of include files and libraries are customized depending on which ssl stack is used. So you also need to add similar custimizetion in Makefile of port avoding conflicts with the settings in Mk/Uses/ssl.mk. And it must be hard job. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
From: Michael Gmelin Subject: Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x Date: Wed, 5 May 2021 17:32:02 +0200 > Which port are you talking about by the way? > > This worked for me just fine in the past (placed in make.conf): > > DEFAULT_VERSIONS+=ssl=libressl > > for LibreSSL and > > DEFAULT_VERSIONS+=ssl=openssl > > for openssl from ports. > > See also: > > $ head -n12 /usr/ports/Mk/Uses/ssl.mk > # Handle dependency on *ssl ports. > # > # Feature: SSL_DEFAULT > # Usage:USES=ssl > # Valid ARGS: none (build and run), build, run > # > # The user can choose which ssl library he wants with: > # > # DEFAULT_VERSIONS+=ssl= > # > # Variants being base, openssl, libressl, and libressl-devel. > # > > Cheers, > Michael You misunderstand my intention. What I would like to do is to make a port use security/openssl instead of base OpenSSL even if user sets 'DEFAULT_VERSIONS+=ssl=base' in /etc/make.conf (or user doesn't customize setting about ssl at all). As I wrote previous mail, if 'USES=python:3.8+' is specified in Makefile of a port, lang/python38 is used for the port event if user adds 'DEFAULT_VERSIONS+=python=3.7' in /etc/make.conf. I'm looking for similar way about ssl setting. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
From: Michael Gmelin Subject: Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x Date: Tue, 4 May 2021 23:05:06 +0200 > See https://docs.freebsd.org/en/books/porters-handbook/uses/#uses-ssl > > Best I checked it but couldn't find proper solution. I think what is necessary in my case is something like version-spec argument of 'USES=python'. For example, if 'USES=python:3.8+' is specified in Makefile of a port, lang/python38 is used for it even if user sets 'DEFAULT_VERSIONS+=python=3.7' in /etc/make.conf. But 'USES=ssl' doesn't provide such argument. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Making a port to use OpenSSL of ports collection on FreeBSD 11.x
Hello, Of the currently supported FreeBSD versions, base system of FreeBSD 11.x uses OpenSSL 1.0.2 and that of FreeBSD 12.x or later use OpenSSL 1.1.1. Then when new version of an application dropped suport of OpenSSL 1.0.2, is there any way to make the port of it to use OpenSSL of ports collection if the system is FreeBSD 11.x? Best Regards. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Ports recompile for 13.0-RELEASE
From: Yasuhiro Kimura Subject: Re: Ports recompile for 13.0-RELEASE Date: Wed, 05 May 2021 00:15:39 +0900 (JST) > It depends on how there are installed. If they are installed by using > official pakcages or building personal packages with poudriere, then > `pkg upgrade` is worth trying. Oops, it should be `pkg upgrade -f`. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Ports recompile for 13.0-RELEASE
From: "@lbutlr" Subject: Ports recompile for 13.0-RELEASE Date: Tue, 4 May 2021 08:10:38 -0600 > With the move to FreeBSD 13.0 is there a simple (single step) way to > reinstall all the current ports other than saving off a list of the > ports and then stepping through that list to reinstall them? It depends on how there are installed. If they are installed by using official pakcages or building personal packages with poudriere, then `pkg upgrade` is worth trying. But you should save list of installed packages just in case. otherwise (i.e. you used portmaster or simple `cd /usr/port/category/portname; make insall`) `portmaster -af` may work fine if you are lucky. But in this case I think saving list of installed packages, removing all of them and then reinstalling them is probably the easiest and shortest way as a result. > And finally, the release of 13.0 ends the 12.x versions, right? > There will not be a 12.3. According to 'Supported FreeBSD releases' (https://www.freebsd.org/security/#sup), expected EoL of 12.2-RELEASE is '12.3-RELEASE + 3 months', and that of stable/12 is June 30, 2024. So at least 12.3-RELEASE will be released. And probably 12.4-RELEASE will be too. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to make 'named' rc script invokded earlier at boot time
From: b56...@oldach.net (Helge Oldach) Subject: Re: How to make 'named' rc script invokded earlier at boot time Date: Fri, 30 Apr 2021 11:25:03 +0200 (CEST) > Looks like this is caused by security/trousers which has "BEFORE: named > hastd". This port had been touched 3 weeks ago. You provide me very good hint! On my home server security/trousers and emulators/tpm-emulator are installed as dependencies of security/gnutls. They install /usr/local/etc/rc.d/tcsd and /usr/local/etc/rc.d/tpmd respectivley. And there is circular dependency between these 2 rc srcipts and /usr/local/etc/rc.d/named. -- root@eastasia[1067]# rcorder /etc/rc.d/* /usr/local/etc/rc.d/* > /dev/null rcorder: file `/usr/local/etc/rc.d/tcsd' is before unknown provision `kerberos' rcorder: Circular dependency on file `/usr/local/etc/rc.d/named'. rcorder: Circular dependency on provision `fake_prov_0004': /usr/local/etc/rc.d/tcsd -> /usr/local/etc/rc.d/tpmd -> /etc/rc.d/SERVERS -> /usr/local/etc/rc.d/named -> /usr/local/etc/rc.d/tcsd. rcorder: `/usr/local/etc/rc.d/named' was seen in circular dependencies for 1 times. rcorder: `/etc/rc.d/SERVERS' was seen in circular dependencies for 1 times. rcorder: `/usr/local/etc/rc.d/tpmd' was seen in circular dependencies for 1 times. rcorder: `/usr/local/etc/rc.d/tcsd' was seen in circular dependencies for 1 times. rcorder: `/usr/local/etc/rc.d/named' was seen in circular dependencies for 1 times. root@eastasia[1068]# -- If I temporally move /usr/local/etc/rc.d/tcsd to somewhere else and add 'ntpdate' to 'BEFORE' line of /usr/local/etc/rc.d/named, then 'named' comes before 'ntpupdate' in the result of rcorder. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to make 'named' rc script invokded earlier at boot time
From: Yasuhiro Kimura Subject: Re: How to make 'named' rc script invokded earlier at boot time Date: Fri, 30 Apr 2021 17:18:26 +0900 (JST) >> The only way I can see is modify the named rc script and add the >> services that needs named to be started on the BEFORE line at the >> beginning of the script. Mind you, it really needs to start after >> syslog (unless you log directly to files and do not use syslog.) > > Thanks for advice. I'll try it. I tried it but am confused by the result. I modified /usr/local/etc/rc.d/named on my home server as following. -- root@eastasia[1051]# head /usr/local/etc/rc.d/named #!/bin/sh # PROVIDE: named # REQUIRE: NETWORKING ldconfig syslogd # BEFORE: SERVERS ntpdate # KEYWORD: shutdown # # Add the following lines to /etc/rc.conf to enable BIND: # named_enable (bool): Run named, the DNS server (or NO). root@eastasia[1052]# -- And I executed `rcorder /etc/rc.d/* /usr/local/etc/rc.d/*`. Then I got just same result as before the modification. So I modifed /etc/rc.d/ntpdate as following. -- root@eastasia[1053]# head /etc/rc.d/ntpdate ~ #!/bin/sh # # $FreeBSD$ # # PROVIDE: ntpdate # REQUIRE: NETWORKING syslogd named # KEYWORD: nojail . /etc/rc.subr root@eastasia[1054]# -- But the result still didn't changed. As I wrote another mail my result of `rcorder -p` is different from that of Helge Oldach. These oddities may be related. I'll investigate further but it may take for a while. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to make 'named' rc script invokded earlier at boot time
From: Mathieu Arnold Subject: Re: How to make 'named' rc script invokded earlier at boot time Date: Fri, 30 Apr 2021 10:02:31 +0200 > There is an option in the port to have named start later, but up to now, > it was starting early enough. > > The only way I can see is modify the named rc script and add the > services that needs named to be started on the BEFORE line at the > beginning of the script. Mind you, it really needs to start after > syslog (unless you log directly to files and do not use syslog.) Thanks for advice. I'll try it. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to make 'named' rc script invokded earlier at boot time
From: b56...@oldach.net (Helge Oldach) Subject: Re: How to make 'named' rc script invokded earlier at boot time Date: Fri, 30 Apr 2021 10:01:47 +0200 (CEST) > Can you try rcorder -p? That will group equally ranked scripts on the same > line. > > On 13, I'm seeing: > > (snip) > /etc/rc.d/pwcheck /etc/rc.d/watchdogd /usr/local/etc/rc.d/named > /etc/rc.d/auditd /etc/rc.d/ntpdate /etc/rc.d/bsnmpd /etc/rc.d/savecore > /etc/rc.d/power_profile /etc/rc.d/localpkg /etc/rc.d/hastd > /etc/rc.d/rpcbind /etc/rc.d/SERVERS /etc/rc.d/auditdistd > (snip) > > which implies that the ordering of named and ntpdate is random however both > are before SERVERS. > > Kind regards > Helge I get following result. (snip) /etc/rc.d/NETWORKING /etc/rc.d/kdc /etc/rc.d/kfd /etc/rc.d/pppoed /etc/rc.d/nfsuserd /etc/rc.d/iscsid /etc/rc.d/iscsictl /etc/rc.d/nfscbd /etc/rc.d/kpasswdd /etc/rc.d/kadmind /etc/rc.d/ipropd_slave /etc/rc.d/ipropd_master/etc/rc.d/mountcritremote /etc/rc.d/devfs /etc/rc.d/virecover /etc/rc.d/os-release /etc/rc.d/motd /etc/rc.d/archdep /etc/rc.d/mdconfig2 /etc/rc.d/gptboot /etc/rc.d/wpa_supplicant /etc/rc.d/accounting /etc/rc.d/dmesg /etc/rc.d/cleartmp /etc/rc.d/hostapd /etc/rc.d/newsyslog /etc/rc.d/syslogd /etc/rc.d/sysvipc /etc/rc.d/linux /etc/rc.d/pwcheck /etc/rc.d/localpkg /etc/rc.d/power_profile /etc/rc.d/auditd /etc/rc.d/bsnmpd /etc/rc.d/ntpdate /etc/rc.d/savecore /etc/rc.d/watchdogd /etc/rc.d/rpcbind /etc/rc.d/auditdistd /etc/rc.d/nfsclient /usr/local/etc/rc.d/tpmd /usr/local/etc/rc.d/tcsd /etc/rc.d/hastd /usr/local/etc/rc.d/named /etc/rc.d/SERVERS (snip) 'named' is still later than 'ntpdate' on my home server. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
How to make 'named' rc script invokded earlier at boot time
I installed dns/bind916 on my home server and configured it so it worked as both authoritative and recursor. Then I added 'nameserver 127.0.0.1' to /etc/resolv.conf and everything worked fine. But after updating OS from 12.2-RELEASE to 13.0-RELEASE I noticed execution of some rc scripts fails at boot time because of DNS lookup error. And I also found these scripts are executed earlier than 'named'. Now let me use 'ntpdate' as an example. If I run `rcorder /etc/rc.d/* /usr/local/etc/rc.d/*` on 12.2-RELEASE, then I get following result. -- root@rolling-vm-freebsd3[474]# uname -a FreeBSD rolling-vm-freebsd3.home.utahime.org 12.2-RELEASE-p6 FreeBSD 12.2-RELEASE-p6 GENERIC amd64 root@rolling-vm-freebsd3[475]# rcorder /etc/rc.d/* /usr/local/etc/rc.d/* /etc/rc.d/growfs /etc/rc.d/sysctl /etc/rc.d/hostid /etc/rc.d/zvol /etc/rc.d/dumpon (snip) /etc/rc.d/static_arp /etc/rc.d/bridge /etc/rc.d/route6d /etc/rc.d/NETWORKING /etc/rc.d/mountcritremote /etc/rc.d/devfs /etc/rc.d/ipmon /etc/rc.d/kdc /etc/rc.d/mdconfig2 /etc/rc.d/newsyslog /etc/rc.d/syslogd /usr/local/etc/rc.d/tcsd /usr/local/etc/rc.d/named /etc/rc.d/watchdogd /etc/rc.d/savecore /etc/rc.d/archdep /etc/rc.d/linux /etc/rc.d/sysvipc /etc/rc.d/SERVERS /usr/local/etc/rc.d/tpmd /usr/local/etc/rc.d/stunnel /etc/rc.d/accounting /etc/rc.d/ntpdate /etc/rc.d/rpcbind /etc/rc.d/nfsclient /etc/rc.d/nisdomain (snip) -- As you can see, while 'named' is executed before SERVERS, 'ntpdate' is done after it. On the other hand I get following result on 13.0-RELEASE. -- root@rolling-vm-freebsd2[332]# uname -a FreeBSD rolling-vm-freebsd2.home.utahime.org 13.0-RELEASE FreeBSD 13.0-RELEASE #0 releng/13.0-n244733-ea31abc261f: Fri Apr 9 04:24:09 UTC 2021 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 root@rolling-vm-freebsd2[333]# rcorder /etc/rc.d/* /usr/local/etc/rc.d/* /etc/rc.d/dhclient /etc/rc.d/dumpon /etc/rc.d/growfs /etc/rc.d/natd (snip) /etc/rc.d/netwait /etc/rc.d/blacklistd /etc/rc.d/local_unbound /etc/rc.d/NETWORKING /etc/rc.d/pppoed /etc/rc.d/kdc /etc/rc.d/kfd /etc/rc.d/nfsuserd /etc/rc.d/iscsid /etc/rc.d/ipropd_slave /etc/rc.d/nfscbd /etc/rc.d/iscsictl /etc/rc.d/ipropd_master /etc/rc.d/kadmind /etc/rc.d/kpasswdd /etc/rc.d/mountcritremote /etc/rc.d/wpa_supplicant /etc/rc.d/motd /etc/rc.d/accounting /etc/rc.d/cleartmp /etc/rc.d/dmesg /etc/rc.d/archdep /etc/rc.d/gptboot /etc/rc.d/hostapd /etc/rc.d/virecover /etc/rc.d/mdconfig2 /etc/rc.d/devfs /etc/rc.d/os-release /etc/rc.d/newsyslog /etc/rc.d/linux /etc/rc.d/syslogd /etc/rc.d/sysvipc /etc/rc.d/watchdogd /etc/rc.d/savecore /etc/rc.d/ntpdate /etc/rc.d/localpkg /etc/rc.d/auditd /etc/rc.d/bsnmpd /etc/rc.d/pwcheck /etc/rc.d/power_profile /etc/rc.d/rpcbind /etc/rc.d/auditdistd /usr/local/etc/rc.d/named /etc/rc.d/nfsclient /etc/rc.d/hastd /etc/rc.d/SERVERS /etc/rc.d/nisdomain /usr/local/etc/rc.d/stunnel /usr/local/etc/rc.d/tpmd /usr/local/etc/rc.d/tcsd (snip) -- Now both 'named' and 'ntpdate' are executed before SERVERS. And unfortunately the latter is earlier than the former. So it is natural that execution of 'ntpdate' fails with DNS lookup failure. I compared ntpdate rc script between releng/12.2 and releng/13.0 but there is no difference. -- yasu@rolling-vm-freebsd2[1035]% pwd /usr/src yasu@rolling-vm-freebsd2[1036]% git diff origin/releng/12.2 origin/releng/13.0 -- libexec/rc/rc.d/ntpdate yasu@rolling-vm-freebsd2[1037]% -- And of cource there is no difference with /usr/local/etc/rc.d/named either. So it seems evaluation of rcorder(8) is changed between 12.2-RELASE and 13.0-RELEASE. Then is there any way to make 'named' rc script invoked earlier at boot time on 13.0-RELEASE? Best Regards. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/luasec maintainer not responding
From: Thomas Morper Subject: security/luasec maintainer not responding Date: Thu, 29 Apr 2021 19:42:35 +0200 (CEST) > Second: how do you deal with this situation in general? I think I've asked > this question before, but the results were somewhat inconclusive. When is > a port considered unmaintained despite formally having a maintainer and > how do you either mark it as unmaintained or assign a new maintainer with > the least amount of work for anyone involved? 1. Submit patch to change MAINTAINER of the port in question. 2. Wait for timeout (for about a month). 3. Ask committers for commiting the patch. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: INDEX build failed for 11.x
From: Ports Index build
Subject: INDEX build failed for 11.x
Date: Thu, 8 Apr 2021 00:05:39 GMT
> INDEX build failed with errors:
> Generating INDEX-11 - please wait..--- describe.accessibility ---
> --- describe.arabic ---
> --- describe.archivers ---
> --- describe.astro ---
> --- describe.audio ---
> --- describe.benchmarks ---
> --- describe.biology ---
> --- describe.cad ---
> --- describe.chinese ---
> --- describe.comms ---
> --- describe.converters ---
> --- describe.databases ---
> --- describe.deskutils ---
> --- describe.devel ---
> --- describe.dns ---
> --- describe.editors ---
> --- describe.emulators ---
> --- describe.finance ---
> --- describe.french ---
> --- describe.ftp ---
> [...]
> --- describe.print ---
> --- describe.russian ---
> --- describe.science ---
> --- describe.security ---
> --- describe.shells ---
> --- describe.sysutils ---
> --- describe.textproc ---
> --- describe.ukrainian ---
> --- describe.vietnamese ---
> --- describe.www ---
> --- describe.x11 ---
> --- describe.x11-clocks ---
> --- describe.x11-drivers ---
> --- describe.x11-fm ---
> --- describe.x11-fonts ---
> --- describe.x11-servers ---
> --- describe.x11-themes ---
> --- describe.x11-toolkits ---
> --- describe.x11-wm ---
> Done.
> make_index: /home/indexbuild/tindex/ports/databases/p5-AnyEvent-CouchDB: no
> entry for /home/indexbuild/tindex/ports/databases/couchdb2
>
(snip)
Attached patch fixes the failure. Would someone please commit it?
Best Regards.
>From 00e18b09e2438be2d7c1f4ca86a9092c5b46d585 Mon Sep 17 00:00:00 2001
From: Yasuhiro Kimura
Date: Thu, 8 Apr 2021 10:40:22 +0900
Subject: [PATCH] databases/p5-AnyEvent-CouchDB: remove port
Remove databases/p5-AnyEvent-CouchDB because it depends on expired
databases/couchdb2.
---
MOVED | 2 +-
databases/Makefile | 1 -
databases/p5-AnyEvent-CouchDB/Makefile | 33 -
databases/p5-AnyEvent-CouchDB/distinfo | 2 --
databases/p5-AnyEvent-CouchDB/pkg-descr | 10
databases/p5-AnyEvent-CouchDB/pkg-plist | 10
6 files changed, 1 insertion(+), 57 deletions(-)
delete mode 100644 databases/p5-AnyEvent-CouchDB/Makefile
delete mode 100644 databases/p5-AnyEvent-CouchDB/distinfo
delete mode 100644 databases/p5-AnyEvent-CouchDB/pkg-descr
delete mode 100644 databases/p5-AnyEvent-CouchDB/pkg-plist
diff --git a/MOVED b/MOVED
index 2dc8f9a0132d..091b24e3b48b 100644
--- a/MOVED
+++ b/MOVED
@@ -16274,4 +16274,4 @@ misc/floatator||2021-04-07|Has expired: Unmaintained
and dead upstream, does not
finance/wmstock||2021-04-07|Has expired: Unmaintained and dead upstream, does
not build with -fno-common (llvm 11)
ftp/frox||2021-04-07|Has expired: Unmaintained and dead upstream, does not
build with -fno-common (llvm 11)
databases/couchdb2|databases/couchdb3|2021-04-07|No longer supported upstream,
uses spidermonkey68 & python2; move to databases/couchdb3
-
+databases/p5-AnyEvent-CouchDB||2021-04-07|Depends on expired databases/couchdb2
diff --git a/databases/Makefile b/databases/Makefile
index 89fa0c284e2c..58b8520e7da8 100644
--- a/databases/Makefile
+++ b/databases/Makefile
@@ -243,7 +243,6 @@
SUBDIR += p5-Amazon-SimpleDB
SUBDIR += p5-Amon2-DBI
SUBDIR += p5-AnyEvent-BDB
-SUBDIR += p5-AnyEvent-CouchDB
SUBDIR += p5-AnyEvent-DBD-Pg
SUBDIR += p5-AnyEvent-Memcached
SUBDIR += p5-AnyEvent-Redis
diff --git a/databases/p5-AnyEvent-CouchDB/Makefile
b/databases/p5-AnyEvent-CouchDB/Makefile
deleted file mode 100644
index c59d83f24b1e..
--- a/databases/p5-AnyEvent-CouchDB/Makefile
+++ /dev/null
@@ -1,33 +0,0 @@
-# Created by: Sunpoet Po-Chuan Hsieh
-
-PORTNAME= AnyEvent-CouchDB
-PORTVERSION= 1.31
-PORTREVISION= 3
-CATEGORIES=databases perl5
-MASTER_SITES= CPAN
-PKGNAMEPREFIX= p5-
-
-MAINTAINER=sunp...@freebsd.org
-COMMENT= Non-blocking CouchDB client based on jquery.couch.js
-
-LICENSE= MIT
-
-DEPRECATED=Uses EOL Python 2.7 via databases/couchdb2
-EXPIRATION_DATE=2021-06-23
-
-BUILD_DEPENDS= ${RUN_DEPENDS}
-RUN_DEPENDS= couchdb2>=0.9.0:databases/couchdb2 \
- p5-AnyEvent-HTTP>=2.11:www/p5-AnyEvent-HTTP \
- p5-CouchDB-View>=0:databases/p5-CouchDB-View \
- p5-Data-Dump-Streamer>=0:devel/p5-Data-Dump-Streamer \
- p5-Exception-Class>=0:devel/p5-Exception-Class \
- p5-IO-All>=0:devel/p5-IO-All \
- p5-JSON>=2:converters/p5-JSON \
- p5-Scope-Guard>=0:devel/p5-Scope-Guard
-
-USES= perl5
-USE_PERL5= configure
-
-NO_ARCH= yes
-
-.include
diff --git a/databases/p5-AnyEvent-CouchDB/distinfo
b/databases/p5-AnyEvent-CouchDB/distinfo
deleted file mode 100644
index 715e713b60cc..
--- a/databases/p5-AnyEvent-CouchDB/dis
Re: MariaDB Options for Port.,MariaDB Options for Port.
From: "Janky Jay, III"
Subject: MariaDB Options for Port.,MariaDB Options for Port.
Date: Wed, 10 Mar 2021 17:59:35 -0700
> I've been trying to add a MariaDB option to a port I maintain but
> everything I have tried has failed. There's is obviously something I'm
> not understanding about the available options so I'm hoping someone can
> point me the right direction.
>
> The port currently has a MySQL option which works fine but I'd like
> to add MariaDB in there as an alternative:
>
> .if ${PORT_OPTIONS:MMYSQLSERVER}
> USES+= mysql:server
> .endif
>
> Based on the information I found in the Porter's Handbook [1], it
> appears there are options for MariaDB but they come from variants of
> USES=mysql (such as "mysql:105m", for MariaDB.) However, setting this to
> the version isn't working. Plus, I don't want to specify a required
> version since there isn't one (I'd like users to be able to use whatever
> version they prefer.) It also appears I cannot use multiple USES= lines
> because aside from the version arg, it would just use those settings for
> MySQL and ignore MariaDB like it's already doing.
>
> Below is the line I last tested without any luck. Again, I don't
> want to specify a version, though. I'd like it do the same thing that
> USES+=mysql does where it will install the default version if MariaDB
> doesn't exist but if it does, it'll find the correct libs and move
> forward with the dependency:
>
> .if ${PORT_OPTIONS:MMARIADBSERVER}
> USES+= mysql:105m
> .endif
>
> Can someone please point me to more informative documentation or
> maybe even provide an example port that is already doing this? I've
> searched the ports tree but failed to find anything helpful.
>
> [1] - https://docs.freebsd.org/en/books/porters-handbook/#uses-mysql
>
> Regards,
> Janky Jay, III
>
Your port works fine with both MySQL and MariaDB. Right? If so you
should add `USES=mysql` without version arguments in the Makefile of
your port. Then user can specify which version of MySQL or MariaDB to
be used. For example, if he wants to use MariaDB 10.5 then he should
add following line in make.conf
------
DEFAULT_VERSIONS+=10.5m
--
---
Yasuhiro Kimura
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: port that needs go >= 1.16
From: Nuno Teixeira Subject: port that needs go >= 1.16 Date: Thu, 18 Feb 2021 11:56:27 + > Hello! > > I'm testing updating security/gopass > <https://www.freshports.org/security/gopass/> to latest version and it > fails compiling because it need go lang >= 1.16, and mine is 1.15.8. > > How to "force" port makefile to use >= 1.16 > Do I need to do that? Since 1.16 is available now on ports? > > https://github.com/gopasspw/gopass/issues/1804 r565496 updated lang/go to 1.16. https://svnweb.freebsd.org/ports?view=revision=565496 --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: List of packages upgraded last time `pkg upgrade` was executed
From: Michael Gmelin Subject: Re: List of packages upgraded last time `pkg upgrade` was executed Date: Wed, 27 Jan 2021 10:05:57 +0100 > This will give you a list of all packages that were updated/installed > last: > > pkg query -e %t=$(pkg query %t | sort -n | tail -n1) %n-%v I tried this but unfortunately it doesn't seem to work as is expected. On the host I tried it, following packages are upgraded when I did `pkg upgrade` last time. p5-URI-5.06 p5-Module-CoreList-5.20210120 rubygem-bundler-2.2.7_1,1 sudo-1.9.5p2 1611721387 And I got following result. yasu@eastasia[1213]% pkg query -e %t=$(pkg query %t | sort -n | tail -n1) %n-%v p5-Module-CoreList-5.20210120 p5-URI-5.06 yasu@eastasia[1213]% So I checked timestamp of install packages. yasu@eastasia[1216]% pkg query -a '%n-%v %t' | sort -k 2 -n -r | head -10 ~ p5-URI-5.06 1611721389 p5-Module-CoreList-5.20210120 1611721389 rubygem-bundler-2.2.7_1,1 1611721388 sudo-1.9.5p2 1611721387 p5-Config-General-2.63 1611685127 libunwind-20201110 1611685127 bind916-9.16.11 1611685127 zstd-1.4.8 1611685126 sqlite3-3.34.1,1 1611685126 bind-tools-9.16.11 1611685125 yasu@eastasia[1217]% As you can see timestamps of rubygem-bundler-2.2.7_1,1 and sudo-1.9.5p2 are smaller than that of p5-URI-5.06 and p5-Module-CoreList-5.20210120. So they aren't included in the list. > As far as I can tell, packages installed by the same pkg invocation run > share the same installation timestamp (I didn't check the pkg sources, > but that's what appears to be the case), According to the above result, it doesn't seem to be true. And I think it's quite possible. When packages are upgraded they are upgraded not in parallel but sequentially. So let me assume following situation. * Pakcage A and B are to be upgraded. * A is upgraded first and B is next. * Both are quite large package. * Host is low-spec. In this case upgrade of each package may take a few minutes. And it result in that there is difference of a few minites between the timestamps of them after upgrade. > If you use a script to do upgrades, you could store the timestamp as > part of that and do something like this: > > touch /tmp/lastupgrade > pkg upgrade > # then, later: > pkg query -e "%t>=$(stat -f %m /tmp/lastupgrade)" %n-%v This didn't hit upon me and I think it's really excellent way to use file for timestamp. I'll use it in my shell script. Thank you for letting me know. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: List of packages upgraded last time `pkg upgrade` was executed
From: Freddie Cash Subject: Re: List of packages upgraded last time `pkg upgrade` was executed Date: Tue, 26 Jan 2021 17:26:29 -0800 > /var/log/messages and I think /var/log/daemon include the output of the pkg > commands. If you have the log files backed up from the last time it was > run, you could grep for pkg in those. > > No idea if this info is also stored in the sqlite databases pkg uses. Thank you for reply. But my intention is to write shell script that gets the list of upgraded packages and does something by using it. Because of that the list need to be gotton without any user interaction. So unfortunately your method is not applicable to my case. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
List of packages upgraded last time `pkg upgrade` was executed
Hello, Is there any way to get the list of packages upgraded (and installed as new dependency if there are) last time `pkg upgrade` was executed? Best Regards. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: What does "build-as-user" of package build means?
From: Jan Beich Subject: Re: What does "build-as-user" of package build means? Date: Fri, 04 Dec 2020 07:14:58 +0100 >> So I have the question as is written in subject. Would someone please >> let me know what is different from "121amd64-default" build? > > build-as-user used to mean BUILD_AS_NON_ROOT=yes in poudriere.conf but > the default changed in http://github.com/freebsd/poudriere/commit/e64d1c931624 Thanks for reply. Then there is no difference between "121amd64-default" and "121amd64-default-build-as-user" now, and I'm confused why build error only happens with the latter. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
What does "build-as-user" of package build means?
Hello, Since September I've been receiving mail from pkg-fallout that reports build failure of devel/magit. Following are logs of build error. http://package19.nyi.freebsd.org/data/121amd64-default-build-as-user/548168/logs/magit-emacs27_nox-2.90.1_4.log http://package19.nyi.freebsd.org/data/121amd64-default-build-as-user/549535/logs/magit-emacs27_nox-2.90.1_4.log http://package19.nyi.freebsd.org/data/121amd64-default-build-as-user/551346/logs/magit-emacs27_nox-2.90.1_4.log http://package19.nyi.freebsd.org/data/121amd64-default-build-as-user/552777/logs/magit-emacs27_nox-2.90.1_4.log http://package19.nyi.freebsd.org/data/121amd64-default-build-as-user/554920/logs/magit-emacs27-2.90.1_4.log http://package19.nyi.freebsd.org/data/121amd64-default-build-as-user/556128/logs/magit-emacs27-2.90.1_4.log According to it bus error happens while byte compiling elisp file. And it only happens with "121amd64-default-build-as-user" build and not with "121amd64-default" build. I tried build test with same combinatin of host and jail (i.e. 13-CURRENT amd64 host and 12.1-RELEASE amd64 jail). But build succeeds without any error. So I have the question as is written in subject. Would someone please let me know what is different from "121amd64-default" build? Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/ruby-gems strange ?
From: KIRIYAMA Kazuhiko Subject: devel/ruby-gems strange ? Date: Mon, 23 Nov 2020 15:09:58 +0900 > Hi all, > > devel/ruby-gems can't install because of rack of stuffs: > (snip) > > Is this ruby-gems corrupted ? Yes, currently devel/ruby-gems is broken with lang/ruby30. While version of devel/ruby-gems is 3.0.8, version of rubygems bundled in 3.0.0-preview1 is 3.2.0.rc1. So the reason of breakge may be that 3.0.8 isn't compatible with Ruby 3.0. Since 3.2.0 isn't released yet I tried to update devel/ruby-gems to 3.1.4. But another and worse problem happened. 3.1.4 fails to install with any version of ruby in ports tree. And I'm in stuck at this status. Probably some hacks are necessary but unfortunately I haven't found it yet. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Port build failure in stage-qa,Port build failure in stage-qa
From: Stefan Esser Subject: Port build failure in stage-qa,Port build failure in stage-qa Date: Wed, 11 Nov 2020 21:56:49 +0100 > Since DEVELOPER=yes cannot be overridden on the command line, I'll > have to remove it from make.conf to get a kernel with matching > modules installed. I add following lines in make.conf. -- .ifndef NO_DEVELOPER DEVELOPER=yes .endif -- And developer mode can be disabled from command line with % make NO_DEVELOPER=yes Just FYI. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: OpenJDK ports and 13-CURRENT
From: Yasuhiro KIMURA Subject: Re: OpenJDK ports and 13-CURRENT Date: Sun, 11 Oct 2020 08:35:39 +0900 (JST) >> Can you try the attached patch? I haven't yet looked at openjdk 13 and >> up, but I assume they will need at least the XSynchronize fix, and maybe >> the above ones, if the upstream branches were made after 2020-02-05. > > I tried your patch but it fails at patch phase as following. Sorry, I made a mistake. Your patch just works fine on 13-CURRENT amd64 r366578. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: OpenJDK ports and 13-CURRENT
From: Yasuhiro KIMURA
Subject: Re: OpenJDK ports and 13-CURRENT
Date: Sun, 11 Oct 2020 08:35:39 +0900 (JST)
> From: Dimitry Andric
> Subject: Re: OpenJDK ports and 13-CURRENT
> Date: Sun, 11 Oct 2020 00:57:33 +0200
>
>> Can you try the attached patch? I haven't yet looked at openjdk 13 and
>> up, but I assume they will need at least the XSynchronize fix, and maybe
>> the above ones, if the upstream branches were made after 2020-02-05.
>
> I tried your patch but it fails at patch phase as following.
I modified your patch as following and now build of java/openjdk12
succeeeds on 13-CURRENT amd64 r366578.
>From 5fb14c6b20c000f57ad975d79aed0072f142ec80 Mon Sep 17 00:00:00 2001
From: Yasuhiro KIMURA
Date: Sun, 11 Oct 2020 10:28:47 +0900
Subject: [PATCH] java/openjdk12: Fix build with -fno-common (Clang 11/GCC 10)
Fix build with -fno-common (Clang 11/GCC 10)
---
java/openjdk12/files/patch-changeset-57932| 27 +++
java/openjdk12/files/patch-changeset-57994| 26 ++
..._unix_classes_sun_awt_X11_XlibWrapper.java | 11
...nix_native_libawt__xawt_xawt_XlibWrapper.c | 15 +++
4 files changed, 79 insertions(+)
create mode 100644 java/openjdk12/files/patch-changeset-57932
create mode 100644 java/openjdk12/files/patch-changeset-57994
create mode 100644
java/openjdk12/files/patch-src_java.desktop_unix_classes_sun_awt_X11_XlibWrapper.java
create mode 100644
java/openjdk12/files/patch-src_java.desktop_unix_native_libawt__xawt_xawt_XlibWrapper.c
diff --git a/java/openjdk12/files/patch-changeset-57932
b/java/openjdk12/files/patch-changeset-57932
new file mode 100644
index ..24b929d5ac08
--- /dev/null
+++ b/java/openjdk12/files/patch-changeset-57932
@@ -0,0 +1,27 @@
+changeset: 57932:9e54ea7d9cd9
+user:qpzhang
+date:Wed Feb 05 20:31:09 2020 +0800
+summary: 8238388: libj2gss/NativeFunc.o "multiple definition" link errors
with GCC10
+
+--- src/java.security.jgss/share/native/libj2gss/NativeFunc.c.orig
2020-04-17 22:35:42 UTC
src/java.security.jgss/share/native/libj2gss/NativeFunc.c
+@@ -27,6 +27,9 @@
+ #include
+ #include "NativeFunc.h"
+
++/* global GSS function table */
++GSS_FUNCTION_TABLE_PTR ftab;
++
+ /* standard GSS method names (ordering is from mapfile) */
+ static const char RELEASE_NAME[]= "gss_release_name";
+ static const char IMPORT_NAME[] = "gss_import_name";
+--- src/java.security.jgss/share/native/libj2gss/NativeFunc.h.orig
2020-04-17 22:35:42 UTC
src/java.security.jgss/share/native/libj2gss/NativeFunc.h
+@@ -277,6 +277,6 @@ typedef struct GSS_FUNCTION_TABLE {
+ typedef GSS_FUNCTION_TABLE *GSS_FUNCTION_TABLE_PTR;
+
+ /* global GSS function table */
+-GSS_FUNCTION_TABLE_PTR ftab;
++extern GSS_FUNCTION_TABLE_PTR ftab;
+
+ #endif
diff --git a/java/openjdk12/files/patch-changeset-57994
b/java/openjdk12/files/patch-changeset-57994
new file mode 100644
index ..ac5ef8190d89
--- /dev/null
+++ b/java/openjdk12/files/patch-changeset-57994
@@ -0,0 +1,26 @@
+changeset: 57994:6925fca95959
+user:qpzhang
+date:Tue Feb 04 21:27:10 2020 +0800
+summary: 8238380: java.base/unix/native/libjava/childproc.c "multiple
definition" link errors with GCC10
+
+--- src/java.base/unix/native/libjava/childproc.c.orig 2020-04-17 22:35:42 UTC
src/java.base/unix/native/libjava/childproc.c
+@@ -33,6 +33,7 @@
+
+ #include "childproc.h"
+
++const char * const *parentPathv;
+
+ ssize_t
+ restartableWrite(int fd, const void *buf, size_t count)
+--- src/java.base/unix/native/libjava/childproc.h.orig 2020-04-17 22:35:42 UTC
src/java.base/unix/native/libjava/childproc.h
+@@ -118,7 +118,7 @@ typedef struct _SpawnInfo {
+ * The cached and split version of the JDK's effective PATH.
+ * (We don't support putenv("PATH=...") in native code)
+ */
+-const char * const *parentPathv;
++extern const char * const *parentPathv;
+
+ ssize_t restartableWrite(int fd, const void *buf, size_t count);
+ int restartableDup2(int fd_from, int fd_to);
diff --git
a/java/openjdk12/files/patch-src_java.desktop_unix_classes_sun_awt_X11_XlibWrapper.java
b/java/openjdk12/files/patch-src_java.desktop_unix_classes_sun_awt_X11_XlibWrapper.java
new file mode 100644
index ..4f3913a95410
--- /dev/null
+++
b/java/openjdk12/files/patch-src_java.desktop_unix_classes_sun_awt_X11_XlibWrapper.java
@@ -0,0 +1,11 @@
+--- src/java.desktop/unix/classes/sun/awt/X11/XlibWrapper.java.orig
2020-04-17 22:35:42 UTC
src/java.desktop/unix/classes/sun/awt/X11/XlibWrapper.java
+@@ -529,7 +529,7 @@ static native String XSetLocaleModifiers(String modifi
+ display Specifies the connection to the X server.
+ onoff Specifies a Boolean value that indicates whether to
enable or disable synchronization.
+ */
+-static native int
Re: OpenJDK ports and 13-CURRENT
From: Dimitry Andric Subject: Re: OpenJDK ports and 13-CURRENT Date: Sun, 11 Oct 2020 00:57:33 +0200 > Can you try the attached patch? I haven't yet looked at openjdk 13 and > up, but I assume they will need at least the XSynchronize fix, and maybe > the above ones, if the upstream branches were made after 2020-02-05. I tried your patch but it fails at patch phase as following. yasu@rolling-vm-freebsd1[1326]% make PORTSDIR=/usr0/freebsd/ports/git check-plist ===> License GPLv2 accepted by the user ===> openjdk12-12.0.2+10.4_1 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by openjdk12-12.0.2+10.4_1 for building ===> Extracting for openjdk12-12.0.2+10.4_1 => SHA256 Checksum OK for battleblow-openjdk-jdk12u-jdk-12.0.2+10-4_GH0.tar.gz. ===> Patching for openjdk12-12.0.2+10.4_1 ===> Applying FreeBSD patches for openjdk12-12.0.2+10.4_1 from /usr0/freebsd/ports/git/java/openjdk12/files 2 out of 2 hunks failed--saving rejects to src/java.security.jgss/share/native/libj2gss/NativeFunc.c.rej 2 out of 2 hunks failed--saving rejects to src/java.security.jgss/share/native/libj2gss/NativeFunc.h.rej ===> FAILED Applying FreeBSD patch-changeset-57932 ===> Cleanly applied FreeBSD patch(es) patch-10-af5c725b ===> FAILED to apply cleanly FreeBSD patch(es) patch-changeset-57932 *** Error code 1 Stop. make: stopped in /usr0/freebsd/ports/git/java/openjdk12 yasu@rolling-vm-freebsd1[1327]% --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Poudriere/PREFIX breakage?
From: Mason Loring Bliss Subject: Poudriere/PREFIX breakage? Date: Mon, 5 Oct 2020 23:30:36 -0400 > Hi, all. I just spun up a Poudriere build server, building 2020Q4 for 12.1 > amd64. I set PREFIX=/opt in /usr/local/etc/poudriere.d/make.conf and a > number of things broke, but a number didn't. When I killed the build, as > clearly there's something wrong, I had 29 successful builds and 19 > failures, and a number of skips given that gettext-tools was one of the > failures. This is because base system implicitly assumes PREFIX=/usr/local. If you exec `fgrep -r /usr/local /etc`, then you find '/usr/local' is hard-coded in some files under /etc. To make poudriere build with PREFIX=/opt, you need to create custom jail that all occurrences of '/usr/local' in files under /etc are replaced with `/opt`. But it is still necessary condition and not sufficiend one. Some ports may be unable to be built with non-default prefix. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Seeing packaging problems since about 1-2 days (Requesting argument %2 while only 1 arguments are available)
From: Matthias Fechner Subject: Seeing packaging problems since about 1-2 days (Requesting argument %2 while only 1 arguments are available) Date: Fri, 2 Oct 2020 10:28:52 +0200 > Dear all, > > I see recently new package errors like (this also affects ports I > maintain): > > ===> Building package for avahi-app-0.7_3 > pkg-static: Requesting argument %2 while only 1 arguments are > available > pkg-static: Requesting argument %2 while only 1 arguments are > available > > Anyone an idea what caused this and how to fix it? > > Gruß > Matthias Probably it is fixed with r550901. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [jes...@cisco.com: [Clamav-devel] ClamAV?? blog: ClamAV 0.103.0 release candidate]
From: The Doctor via freebsd-ports Subject: [jes...@cisco.com: [Clamav-devel] ClamAV?? blog: ClamAV 0.103.0 release candidate] Date: Tue, 18 Aug 2020 16:35:28 -0600 > heads up! Folloing is patch to update security/clamav to 0.103.0-rc. Please keep in mind that 0.103.0 is still release candidate and not suitable for production use. Index: security/clamav/Makefile === --- security/clamav/Makefile(revision 545179) +++ security/clamav/Makefile(working copy) @@ -1,7 +1,7 @@ # $FreeBSD$ PORTNAME= clamav -PORTVERSION= 0.102.4 +DISTVERSION= 0.103.0-rc PORTEPOCH= 1 CATEGORIES=security MASTER_SITES= https://www.clamav.net/downloads/production/ Index: security/clamav/distinfo === --- security/clamav/distinfo(revision 545179) +++ security/clamav/distinfo(working copy) @@ -1,3 +1,3 @@ -TIMESTAMP = 1594929106 -SHA256 (clamav-0.102.4.tar.gz) = eebd426a68020ecad0d2084b8c763e6898ccfd5febcae833d719640bb3ff391b -SIZE (clamav-0.102.4.tar.gz) = 1323 +TIMESTAMP = 1597791094 +SHA256 (clamav-0.103.0-rc.tar.gz) = bf3d77969bd5dbf7dd4eb820a3812788fd6cab7aaf8bed3c8facea909917 +SIZE (clamav-0.103.0-rc.tar.gz) = 13398760 Index: security/clamav/pkg-plist === --- security/clamav/pkg-plist (revision 545179) +++ security/clamav/pkg-plist (working copy) @@ -36,10 +36,10 @@ %%PORTDOCSDOCSDIR%%/html/UserManual/libclamav.html %%UNRAR%%lib/libclamunrar.so %%UNRAR%%lib/libclamunrar.so.9 -%%UNRAR%%lib/libclamunrar.so.9.0.4 +%%UNRAR%%lib/libclamunrar.so.9.0.5 %%UNRAR%%lib/libclamunrar_iface.so %%UNRAR%%lib/libclamunrar_iface.so.9 -%%UNRAR%%lib/libclamunrar_iface.so.9.0.4 +%%UNRAR%%lib/libclamunrar_iface.so.9.0.5 @dir(%%CLAMAVUSER%%,%%CLAMAVGROUP%%,0755) %%DBDIR%% @dir(%%CLAMAVUSER%%,%%CLAMAVGROUP%%,0755) %%LOGDIR%% @dir(%%CLAMAVUSER%%,%%CLAMAVGROUP%%,0755) %%RUNDIR%% @@ -60,10 +60,10 @@ include/libfreshclam.h lib/libclamav.so lib/libclamav.so.9 -lib/libclamav.so.9.0.4 +lib/libclamav.so.9.0.5 lib/libfreshclam.so lib/libfreshclam.so.2 -lib/libfreshclam.so.2.0.0 +lib/libfreshclam.so.2.0.1 libdata/pkgconfig/libclamav.pc man/man1/clambc.1.gz man/man1/clamconf.1.gz --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Planned deprecation of portsnap
From: Kurt Jaeger Subject: Re: [HEADS UP] Planned deprecation of portsnap Date: Wed, 5 Aug 2020 06:40:39 +0200 > There's a list where the git topic is discussed: > > https://lists.freebsd.org/pipermail/freebsd-git/ > > Have a look at the archive, and yes, subversion as version control > system for the FreeBSD project will probably be replaced by git. It's a bit hard for me to read entire archive;-). So is there summary of git migration project (about purpose, plan, current status, etc)? --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: www/py-html5lib with FLAVOR=py27 failed to build
From: KIRIYAMA Kazuhiko Subject: www/py-html5lib with FLAVOR=py27 failed to build Date: Sat, 25 Jul 2020 15:17:04 +0900 > www/py-html5lib with FLAVOR=py27 had failed to build: I tried `cd /usr/ports/www/py-html5lib; make FLAVOR=py27 install` with following conditions, OS: 11.4-RELEASE, 12.1-RELEASE and 13-CURRENT r363475 (amd64) Ports tree: head r543492 And in all cases it compeletes without any error. Do you have any non-default setting about options or something related to ports build? --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Segmentation fault happens after updating mail/postfix to 3.5.5
Hello All, After updating mail/postfix to 3.5.5 following warning message appears in /var/log/maillog. Jul 26 11:47:34 eastasia postfix/smtpd[93696]: connect from maybe.home.utahime.org[192.168.174.201] Jul 26 11:47:34 eastasia postfix/smtpd[93696]: SSL_accept error from maybe.home.utahime.org[192.168.174.201]: -1 Jul 26 11:47:34 eastasia postfix/smtpd[93696]: warning: TLS library problem: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate:/usr/src/crypto/openssl/ssl/record/rec_layer_s3.c:1544:SSL alert number 42: Jul 26 11:47:34 eastasia postfix/master[93317]: warning: process /usr/local/libexec/postfix/smtpd pid 93696 killed by signal 11 yasu@eastasia[3721]% uname -a FreeBSD eastasia.home.utahime.org 12.1-RELEASE-p7 FreeBSD 12.1-RELEASE-p7 GENERIC amd64 Does anyone else experience it? --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sqlite3-3.32.3_1,1 no longer build with readline
From: marco Subject: sqlite3-3.32.3_1,1 no longer build with readline Date: Sat, 25 Jul 2020 09:20:35 + > I recently upgraded sqlite3 to sqlite3-3.32.3_1,1 via pkg upgrade. > I noticed the behaviour has changed and arrow up to recall the history > no longer works. > Seems the pkg is no longer being build with readline support. > > [~] pkg info sqlite3-3.32.3_1,1 | grep -i readline > READLINEP : off > READLINES : off > > Not sure in which version this changed since I hadn't done a pkg upgrade for > probably at least 2 weeks. > > I hope this was some oversight and not a conscious decision? I submitted patch to fix this problem as following bug report. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248260 Just FYI. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Bug report commit request
Dear Committers, Would someone please commit following bug report? Bug 242293 - graphics/rubygem-fastimage: Update to 2.1.7 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242293 Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: latest Makefile breaks compilation of security/clamav if base is lacking sendmail
Hello Michael,
Thank you for bug report and patch. I confirmed your patch fixes the
problem with 12.1-RELEASE.
From: Michael Grimm
Subject: latest Makefile breaks compilation of security/clamav if base is
lacking sendmail
Date: Sun, 5 Jul 2020 15:37:13 +0200
> I managed to get compilation working with the attached, surely crude and
> dirty hack (due to my lack of knowledge regarding ports Makefiles), by adding
> 'MILTER_LDFLAGS= -L${LOCALBASE}/lib' and 'MILTER_CFLAGS=
> -I${LOCALBASE}/include' in order to help finding relevant files from port
> mail/libmilter.
>
> What worries my somehow, although clamav is working as usual, is the
> following part in poudrier's log:
>
> checking for mi_stop in -lmilter… yes
> checking libmilter/mfapi.h usability… yes
> checking libmilter/mfapi.h presence… no
> configure: WARNING: libmilter/mfapi.h: accepted by the compiler,
> rejected by the preprocessor!
> configure: WARNING: libmilter/mfapi.h: proceeding with the compiler's
> result
> checking for libmilter/mfapi.h... yes
>
>
> Here my question: Is this the right way to fix this issue?
I'm not sure why configure script produces such warning messages. But
mail/libmilter surely installs ${PREFIX}/lib/libmilter/mfapi.h and
configure script correctly detects it anyway. Therefore I don't think
this warning message is of much concern.
And I submitted a bit modified patch as following bug report.
security/clamav: Fix build after r541115 when base system is build
with 'WITHOUT_SENDMAIL=yes'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247792
Best Regards.
---
Yasuhiro KIMURA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Can not add port with name "py3c" (which is name of project!)
From: Lev Serebryakov Subject: Can not add port with name "py3c" (which is name of project!) Date: Mon, 1 Jun 2020 00:30:04 +0300 > I want to add "devel/py3c" [0] as it is requirement for new Subversion > python bindings. > > When I try to commit this new port I've got this error from pre-commit > hook: > (snip) > > Please note, that port name DOES NOT START with "py3-" :) According to "Python Ports Policy" in FreeBSD Wiki, this port should be named as "py-py3c". https://wiki.freebsd.org/Python/PortsPolicy#Naming --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Bug report commit request
Dear Committers, Would someone please commit following bug report? Bug 244424 mail/postfix-policyd-spf-python: Update to 2.9.2 and rename https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244424 Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to change PATH setting of poudriere
From: Yasuhiro KIMURA
Subject: Re: How to change PATH setting of poudriere
Date: Fri, 15 May 2020 10:00:32 +0900 (JST)
> Thank you for reply. I added above lines to make.conf but resulted in
> error that "Variable PATH is recursive". So I changed as follwing.
>
> PATH=/sbin:/bin:/usr/sbin:/usr/bin:/opt/sbin:/opt/bin:${HOME}/bin
> .export PATH
>
> Then build progressed but failed in other port. And error seems to be
> nothing to do with PATH setting. So let me change my question.
Let me provide detail of the problem.
Environments:
Host: 12.1-RELEASE-p5 amd64
Poudriere: 3.3.4
Jail: 12.1-RELEASE-p5 amd64
Ports tree: head r535191
I'm maintainer of security/clamav and would like to test attached
patch of this bug report.
Bug 246059 - security/clamav: fix build with non-default LOCALBASE, PREFIX
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246059
I added following lines in /usr/local/etc/poudriere.d/make.conf,
applied the patch to ports tree and tried test build of
security/clamav from scratch.
--
LOCALBASE=/opt
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/opt/sbin:/opt/bin:${HOME}/bin
.export PATH
--
Then test build failed with configure error of
misc/help2man. And URL below is build log.
https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/121amd64-test/2020-05-15_13h43m34s/logs/help2man-1.47.15.log
According to it build failed because configure script couldn't find
Locale::gettext perl module.
--
===
===> Configuring for help2man-1.47.15
configure: loading site script /usr/ports/Templates/config.site
checking for perl... perl
checking for module Locale::gettext... no
checking for msgfmt... /opt/bin/msgfmt
checking for gcc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking for library containing dlsym... none required
checking for library containing bindtextdomain... -lintl
configure: error: perl module Locale::gettext required
===> Script "configure" failed unexpectedly.
Rebuild lang/perl5.30 and devel/p5-Locale-gettext manually before contacting
maintainer.
*** Error code 1
Stop.
make: stopped in /usr/ports/misc/help2man
--
But p5-Locale-gettext is surely installed at build-depends phase.
--
===
===> help2man-1.47.15 depends on package: p5-Locale-gettext>=0 - not found
===> Installing existing package /packages/All/p5-Locale-gettext-1.07.txz
[121amd64-test-job-01] Installing p5-Locale-gettext-1.07...
[121amd64-test-job-01] `-- Installing gettext-runtime-0.20.2...
[121amd64-test-job-01] | `-- Installing indexinfo-0.3.1...
[121amd64-test-job-01] | `-- Extracting indexinfo-0.3.1: done
[121amd64-test-job-01] `-- Extracting gettext-runtime-0.20.2: .. done
[121amd64-test-job-01] `-- Installing perl5-5.30.2...
[121amd64-test-job-01] `-- Extracting perl5-5.30.2: .. done
[121amd64-test-job-01] Extracting p5-Locale-gettext-1.07: done
=
Message from perl5-5.30.2:
--
The /usr/bin/perl symlink has been removed starting with Perl 5.20.
For shebangs, you should either use:
#!/usr/local/bin/perl
or
#!/usr/bin/env perl
The first one will only work if you have a /usr/local/bin/perl,
the second will work as long as perl is in PATH.
===> help2man-1.47.15 depends on package: p5-Locale-gettext>=0 - found
===> Returning to build of help2man-1.47.15
--
So it seems something other than PATH setting causes this build error.
---
Yasuhiro KIMURA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to change PATH setting of poudriere
From: Bryan Drewery
Subject: Re: How to change PATH setting of poudriere,Re: How to change PATH
setting of poudriere
Date: Thu, 14 May 2020 14:09:40 -0700
> But I think the make.conf method should work fine. PATH is passed down
> in MAKE_ENV and CONFIGURE_ENV but exporting it might be needed.
>
> PATH:= ${PATH}:/opt/bin
> .export PATH
Thank you for reply. I added above lines to make.conf but resulted in
error that "Variable PATH is recursive". So I changed as follwing.
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/opt/sbin:/opt/bin:${HOME}/bin
.export PATH
Then build progressed but failed in other port. And error seems to be
nothing to do with PATH setting. So let me change my question.
In general what settings are necessary to build and install ports with
non default LOCALBASE?
I though following 2 settings are sufficient.
1. Set LOCALBASE in make.conf
2. Change setting of PATH environment variable so it includes
${LOCALBASE}/bin (and ${LOCALBASE}/sbin too?)
However, in reality, some ports failed to build with them.
Then are any other settings necessary or does it caused by any other
reason (e.g. problme of failed ports, some other setting for poudriere
specific, etc.)?
Best Regards.
---
Yasuhiro KIMURA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
How to change PATH setting of poudriere
Hello. I would like to test non-default LOCALBASE build with poudriere and add 'LOCALBASE=/opt' in /usr/local/etc/poudriere.d/make.conf. But build of some ports fails because /opt/bin is not included in value of PATH environment variable. How do I change PATH setting of poudriere? Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: svn commit: r358166 - head
From: Baptiste Daroussin Subject: Re: svn commit: r358166 - head Date: Fri, 21 Feb 2020 09:25:22 +0100 >> Are there any way to know which of installed ports are linked to base >> ncurses? >> > All the one with USES=ncurses in ports, otherwise I am sorry but no we have no > way to track that down. Thanks for reply. Then I'll rebuild all installed ports as the surest way. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: svn commit: r358166 - head
(Switch to freebsd-ports ML) From: Baptiste Daroussin Subject: svn commit: r358166 - head Date: Thu, 20 Feb 2020 09:33:14 + (UTC) > Author: bapt > Date: Thu Feb 20 09:33:14 2020 > New Revision: 358166 > URL: https://svnweb.freebsd.org/changeset/base/358166 > > Log: > Update the UPDATING information now that ncurses shlib has been bumped > > Modified: > head/UPDATING > > Modified: head/UPDATING > == > --- head/UPDATING Thu Feb 20 09:17:45 2020(r358165) > +++ head/UPDATING Thu Feb 20 09:33:14 2020(r358166) > @@ -26,10 +26,10 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW: > disable the most expensive debugging functionality run > "ln -s 'abort:false,junk:false' /etc/malloc.conf".) > > -20200218: > - ncurses has been updated to a newer version (6.1-20200118). After an > - update some applications using ncurses may results have some rendering > - problems and would need to be rebuilt. > +20200220: > + ncurses has been updated to a newer version (6.1-20200118). Given the > ABI > + has changed, users will have to rebuild all the ports that are linked to > + ncurses. > > 20200217: > The size of struct vnet and the magic cookie have changed. Are there any way to know which of installed ports are linked to base ncurses? Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: parsedmarc
From: Andrea Venturoli Subject: parsedmarc Date: Sun, 19 Jan 2020 16:23:04 +0100 > Is there any chance that these three port be updated? You can create patches to update them by yourself and submit them to FreeBSD Bugzilla. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Discussion on moving manpages to ${PREFIX}/share/man
From: Baptiste Daroussin
Subject: Re: Discussion on moving manpages to ${PREFIX}/share/man
Date: Mon, 13 Jan 2020 09:22:01 +0100
> The discussion happened here:
> https://lists.freebsd.org/pipermail/freebsd-arch/2017-March/018115.html
>
> For some reason I followed up on this only 1.5 years after, and don't know
> when
> I will do the manpage part ;)
I thought the discussion took place somewhere else but didn't imagine
it did more than one year and a half ago :-).
From: Baptiste Daroussin
Subject: Re: Discussion on moving manpages to ${PREFIX}/share/man
Date: Mon, 13 Jan 2020 09:28:24 +0100
> Also note that we did change the manpath to include share/man in base in:
> https://svnweb.freebsd.org/base?view=revision=315053
> Followed by:
> https://svnweb.freebsd.org/base?view=revision=315142
>
> Which both have been merged to freebsd 11 and 12 so we can start thinking
> about
> doing it properly in ports.
I tried it by changing Mk/bsd.port.mk and Templates/BSD.local.dist and
found I need to change Makefile, pkg-plist and patches of lots lots
lots of ports. So I decided to do this work as my long term item ;-).
---
Yasuhiro KIMURA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Discussion on moving manpages to ${PREFIX}/share/man
Hello,
Commit message of ports r484628 says as following.
--
r484628 | bapt | 2018-11-11 03:12:57 +0900 (Sun, 11 Nov 2018) | 23 lines
Install texinfo files (GNU info) into ${PREFIX}/share/info
After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.
--
I checked 2018's archive of this ML but couldn't find such thread.
Would someone please tell me where this discussion took place?
Best Regards.
---
Yasuhiro KIMURA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: tmux-3.0a config file trouble
From: "Alex V. Petrov" Subject: Re: FreeBSD Port: tmux-3.0a config file trouble Date: Sun, 5 Jan 2020 15:58:37 +0700 > I know that. > Even if I run tmux -f ~/.tmux.conf, tmux ignores the configuration file. > The configuration file from the example where "set -g status-bg red". > The color remains green. I tried it on 12.1-RELEASE-p1 amd64 and background color of status line changed to red successfully. What happens if you add some other customizations to ~/.tmux.conf? Are they also ignored? --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: tmux-3.0a config file trouble
From: "Alex V. Petrov" Subject: FreeBSD Port: tmux-3.0a config file trouble Date: Sun, 5 Jan 2020 15:01:55 +0700 > For me, new tmux don't see config file into any placeses. > ~/.tmux.conf > ~/.config/tmux/tmux.conf > ~/.config/tmux/.tmux.conf > ~/.config/.tmux/tmux.conf > ~/.config/.tmux/.tmux.conf According to tmux(1) man page, tmux only read /usr/local/etc/tmux.conf and ~/.tmux.conf. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Bug report commit request
Dear comitters, Would someone please commit following bug reports? Bug 242290 sysutils/tmux: Update to 3.0a (maintainer timeout) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242290 Bug 242293 graphics/rubygem-fastimage: Update to 2.1.7 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242293 Bug 242458 security/py-acme security/py-certbot*: Update to 1.0.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242458 Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Bug reports commit request
Dear Committers, Would someone please commit following bug reports? Bug 241859 devel/treepy.el: Add patch to fix incompatibility with recent snapshot of Emacs. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241859 Bug 241861 devel/psvn: Update to 20150720.214200. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241861 Bug 242091 japanese/ebnetd: Fix build on real environment https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242091 Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Bug report commit request
Dear Committers, Would someone please commit following bug report? security/vuxml: Document potential bypass of Runas user restrictions in sudo https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241244 Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Strange build error of java/openjdk12 with poudriere and 13-CURRENT jail
From: Yasuhiro KIMURA Subject: Strange build error of java/openjdk12 with poudriere and 13-CURRENT jail Date: Fri, 11 Oct 2019 02:20:56 +0900 (JST) > While building java/openjdk12 with poudriere and 13-CURRENT jail, I > experienced strange build error, If I build it with 'poudriere > testport' then it is built successfully. > > https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/curamd64-local/2019-10-10_00h38m18s/logs/openjdk12-12.0.2+10.3.log > > But I build it with 'poudriere bulk' then it fails to build. > > https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/curamd64-local/2019-10-09_17h51m57s/logs/openjdk12-12.0.2+10.3.log I submitted bug report for this problem. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241226 Just FYI. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Strange build error of java/openjdk12 with poudriere and 13-CURRENT jail
Hello, While building java/openjdk12 with poudriere and 13-CURRENT jail, I experienced strange build error, If I build it with 'poudriere testport' then it is built successfully. https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/curamd64-local/2019-10-10_00h38m18s/logs/openjdk12-12.0.2+10.3.log But I build it with 'poudriere bulk' then it fails to build. https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/curamd64-local/2019-10-09_17h51m57s/logs/openjdk12-12.0.2+10.3.log With 12.0-RELEASE jail build succeeds with both 'poudriere testport' and 'poudriere bulk'. What is wrong? Environments are, * Host - Guest VM of VirtualBox on 64bit Windows 10 ver. 1903 - 4 CPUs, 8GB Memory, 100GB Disk - 13-CURRENT amd64 r353107 GENERIC, WITHOUT_LIB32=yes * Poudriere 3.3.2_1 * Jail 13-CURRENT amd64 r353107 GENERIC * Ports tree Head r513940 Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Is IPV6 option still necessary?
On October 10, 2012 IPV6 option of all ports was enabled by default. Commit message said "We are in 2012, it is time to activate IPV6 options by default everywhere". And now we are in 2019. IPv6 is more widely used than 2012. So I wonder if IPV6 option is still necessary. If you use official packages then you always use IPv6-enabled binaries. And even if you build packages by yourself you still use IPv6-enabled ones unless you disable IPV6 option. So I think at most only a few people uses IPv6-disabled packages. Are there anybody who still disables IPV6 option for some serious reason such as working around IPv6-related problem? If there aren't then I think it's time to remove IPV6 option from ports framework. Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ruby25 from ports will not compile
From: "@lbutlr" Subject: ruby25 from ports will not compile Date: Fri, 6 Sep 2019 12:44:29 -0600 > Trying to update ruby on 11.2-RELEASE-p11 (I have also tried to switch to > ruby26 with basically the same results) > > # cd /usr/ports/lang/ruby25 > # make MAKE_JOBS_UNSAFE=yes install > vm.c:(.text+0x1e0bb): undefined reference to > `__dtraceenabled_ruby___method__entry' > vm.c:(.text+0x1e0ef): undefined reference to > `__dtraceenabled_ruby___method__return' > vm.c:(.text+0x1e15d): undefined reference to `__dtrace_ruby___method__entry' > vm.c:(.text+0x1e274): undefined reference to `__dtrace_ruby___method__return' > vm.o: In function `hook_before_rewind': > vm.c:(.text+0x1ed7b): undefined reference to > `__dtraceenabled_ruby___method__return' > vm.c:(.text+0x1eefe): undefined reference to `__dtrace_ruby___method__return' > cc: error: linker command failed with exit code 1 (use -v to see invocation) > *** Error code 1 > > Stop. > make[2]: stopped in /usr/ports/lang/ruby25/work/ruby-2.5.6 > *** Error code 1 What is your architecture? I made clean install of 11.2-RELEASE-p14 amd64, checked out latest ports tree (r511379) and tried # cd /usr/ports/lang/ruby25 # make BATCH=yes install # cd /usr/ports/lang/ruby26 # make BATCH=yes install Then everything completed successfully. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bug report commit request
From: Koichiro Iwao Subject: Re: Bug report commit request Date: Fri, 29 Mar 2019 16:14:53 +0900 > Regarding the PR, koobs@ has already taken it. I leave it to him. > I'm also a big user of certbot, I can also understand your change > and commit it. No. He set keyword and changed status but didn't take. Bug 236367 is still assinged to pyt...@freebsd.org. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Bug report commit request
Dear Committers, Would someone please commit following bug report? Bug 236367 - security/py-acme security/py-certbot*: Update to 0.32.0. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236367 Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Strange build error of graphics/cairo on latest 13-CURRENT
From: Jan Beich Subject: Re: Strange build error of graphics/cairo on latest 13-CURRENT Date: Sun, 24 Mar 2019 07:36:03 +0100 >> Yesterday I updated my 13-CURRENT amd64 host to r345414 and now I'm >> experiencing strange build error of graphics/cairo. If I build it with >> "cd /usr/ports/graphics/cairo; make install" it finishes >> successfully. But if I do it with portmaster it fails at configure >> phase as following. > Can you reproduce after https://svnweb.freebsd.org/changeset/base/345431 ? I updated host and jail to r345464 and now graphics/cairo can be built with portmaster and poudriere. I wonder why build didn't fail with simple "make install". But anyway problem is fixed. Thank you for advice. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Strange build error of graphics/cairo on latest 13-CURRENT
Hello. Yesterday I updated my 13-CURRENT amd64 host to r345414 and now I'm experiencing strange build error of graphics/cairo. If I build it with "cd /usr/ports/graphics/cairo; make install" it finishes successfully. But if I do it with portmaster it fails at configure phase as following. -- checking how to enable unused result warnings... __attribute__((__warn_unused_result__)) checking how to allow undefined symbols in shared libraries used by test suite... -Wl,--allow-shlib-undefined checking whether byte ordering is bigendian... no checking whether float word ordering is bigendian... unknown configure: error: Unknown float word ordering. You need to manually preset ax_cv_c_float_words_bigendian=no (or yes) according to your system. ===> Script "configure" failed unexpectedly. Please report the problem to gn...@freebsd.org [maintainer] and attach the "/usr0/freebsd/ports/work/net/freebsd/ports/head/graphics/cairo/work/cairo-1.16.0/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 Stop. make: stopped in /net/freebsd/ports/head/graphics/cairo -- And this error also happens with poudriere and same jail as host. Does anybody else experience it? --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Request for help: remove bundler from ruby 2.6 port
From: Yasuhiro KIMURA
Subject: Re: Request for help: remove bundler from ruby 2.6 port
Date: Thu, 17 Jan 2019 01:48:16 +0900 (JST)
> From: Yasuhiro KIMURA
> Subject: Re: Request for help: remove bundler from ruby 2.6 port
> Date: Sun, 06 Jan 2019 16:07:01 +0900 (JST)
>
>> https://www.utahime.org/FreeBSD/ports/lang_ruby26.20190105.patch
>>
>> Please take following step to apply this patch.
>>
>> 1. cd /usr/ports
>> 2. svn copy lang/ruby25 lang/ruby26
>> 3. svn delete lang/ruby26/pkg-message
>> 4. svn patch /path/to/this/patch
>
> Updated.
>
> https://www.utahime.org/FreeBSD/ports/lang_ruby26.20190116.patch
>
> Same step is necessary to apply this patch.
I took for a while but I submitted final version as following bug
report.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235826
Now version if updated to 2.6.1. But biggest change is that I gave up
including all standard library. It is because some files such as
'bundler', 'gem' and 'rake' are installed in ${PREFIX}/bin and
therefor conflists with port version of them. So following module are
separeated as other ports.
* DBM
* GDBM
* bundler
* gem
* rake
Please test attached patch and report bug if you find it.
Best Regards.
---
Yasuhiro KIMURA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bug report commit request
From: Kurt Jaeger
Subject: Re: Bug report commit request
Date: Tue, 12 Feb 2019 05:21:58 +0100
> There is no other LICENSE=NONE instance in the ports tree.
yasu@eastasia[2769]% LANG=C svn info
/usr0/freebsd/ports/head.test
Path: .
Working Copy Root Path: /usr0/freebsd/ports/head.test
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 492755
Node Kind: directory
Schedule: normal
Last Changed Author: yuri
Last Changed Rev: 492755
Last Changed Date: 2019-02-12 15:18:05 +0900 (Tue, 12 Feb 2019)
yasu@eastasia[2770]% find -s . -name Makefile -exec grep 'LICENSE.*NONE' {} +
/usr0/freebsd/ports/head.test
./audio/playgsf/Makefile:LICENSE= GPLv2+ LGPL21 NONE
./comms/geoid/Makefile:LICENSE= GPLv2+ NONE # only one src file contains
license
./emulators/fuse-roms/Makefile:LICENSE= NONE
./french/fortune-mod-zarathoustra/Makefile:LICENSE= NONE
./games/goonies/Makefile:LICENSE= NONE
./games/tyrian-data/Makefile:LICENSE= NONE
./graphics/hiptext/Makefile:LICENSE=NONE
./mail/mbox2imap/Makefile:LICENSE= NONE
./mail/ratelimit-policyd/Makefile:LICENSE= NONE
./misc/susv2/Makefile:LICENSE= NONE
./misc/susv3/Makefile:LICENSE= NONE
./misc/susv4/Makefile:LICENSE= NONE
./multimedia/bsdbktr_tvtune/Makefile:LICENSE= NONE
./security/ngrok/Makefile:LICENSE= NONE APACHE20 BSD3CLAUSE CC0-1.0 LGPL3+
MIT
./sysutils/abgx360/Makefile:LICENSE=NONE
./sysutils/abgx360gui/Makefile:LICENSE= NONE
./sysutils/etcmerge/Makefile:LICENSE= NONE
./www/ctemplate/Makefile:LICENSE= NONE
./www/subsonic-standalone/Makefile:LICENSE= NONE
./x11/xtset/Makefile:LICENSE= NONE
yasu@eastasia[2771]%
---
Yasuhiro KIMURA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bug report commit request
From: Kurt Jaeger Subject: Re: Bug report commit request Date: Mon, 11 Feb 2019 10:44:49 +0100 >> > What about the LICENSE=NONE setting ? It stops the port from being build >> > in poudriere ? >> > Can the LICENSE line be just removed ? >> You can build this port with poudriere by adding >> 'LICENSES_ACCEPTED=NONE' in /usr/local/etc/poudriere.d/make.conf. > So, does it sound sensible to define a LICENSE that one has to special-case > immediatly just to do a test-build ? I mean, don't we all have better things > to do than shooting ourselves in the feet ? There is really no license information about this software. So according to license framework of FreeBSD ports there isn't anything wrong about adding 'LICENSE=NONE' in Makefile of this port. And if it is really problematic then what should be fixed is license framework itself or behavior of poudriere about it rather than license information of this port. Ad-hocism doesn't pay in the long run. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bug report commit request
From: Kurt Jaeger Subject: Re: Bug report commit request Date: Mon, 11 Feb 2019 10:10:32 +0100 > What about the LICENSE=NONE setting ? It stops the port from being build in > poudriere ? > > Can the LICENSE line be just removed ? You can build this port with poudriere by adding 'LICENSES_ACCEPTED=NONE' in /usr/local/etc/poudriere.d/make.conf. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Request for help: remove bundler from ruby 2.6 port
From: Yasuhiro KIMURA Subject: Re: Request for help: remove bundler from ruby 2.6 port Date: Sun, 06 Jan 2019 16:07:01 +0900 (JST) > https://www.utahime.org/FreeBSD/ports/lang_ruby26.20190105.patch > > Please take following step to apply this patch. > > 1. cd /usr/ports > 2. svn copy lang/ruby25 lang/ruby26 > 3. svn delete lang/ruby26/pkg-message > 4. svn patch /path/to/this/patch Updated. https://www.utahime.org/FreeBSD/ports/lang_ruby26.20190116.patch Same step is necessary to apply this patch. Currently there is one problem. Rubygem ports fails to be installed. For example install of graphics/rubygem-fastimage fails as following. yasu@rolling-vm-freebsd2[2012]% pwd /usr0/freebsd/ports/head/graphics/rubygem-fastimage yasu@rolling-vm-freebsd2[2013]% make PORTSDIR=/usr0/freebsd/ports/head check-plist ===> License MIT accepted by the user ===> rubygem-fastimage-2.1.5 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by rubygem-fastimage-2.1.5 for building ===> Extracting for rubygem-fastimage-2.1.5 => SHA256 Checksum OK for rubygem/fastimage-2.1.5.gem. ===> rubygem-fastimage-2.1.5 depends on file: /usr/local/bin/ruby26 - found Unpacked gem: '/usr0/freebsd/ports/work/usr0/freebsd/ports/head/graphics/rubygem-fastimage/work/fastimage-2.1.5' ===> Patching for rubygem-fastimage-2.1.5 ===> rubygem-fastimage-2.1.5 depends on file: /usr/local/bin/ruby26 - found ===> rubygem-fastimage-2.1.5 depends on file: /usr/local/bin/ruby26 - found ===> Configuring for rubygem-fastimage-2.1.5 ===> Building for rubygem-fastimage-2.1.5 Successfully built RubyGem Name: fastimage Version: 2.1.5 File: fastimage-2.1.5.gem ===> Staging for rubygem-fastimage-2.1.5 ===> rubygem-fastimage-2.1.5 depends on file: /usr/local/bin/ruby26 - found ===> Generating temporary packing list (cd /usr0/freebsd/ports/work/usr0/freebsd/ports/head/graphics/rubygem-fastimage/work/fastimage-2.1.5; /usr/bin/env RB_USER_INSTALL=yes LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 /usr/local/bin/gem26 install -l --no-update-sources --install-dir /usr0/freebsd/ports/work/usr0/freebsd/ports/head/graphics/rubygem-fastimage/work/stage/usr/local/lib/ruby/gems/2.6 --ignore-dependencies --bindir=/usr0/freebsd/ports/work/usr0/freebsd/ports/head/graphics/rubygem-fastimage/work/stage/usr/local/bin --no-document rdoc,ri fastimage-2.1.5.gem -- --build-args ) ERROR: While executing gem ... (TypeError) no implicit conversion of nil into String *** Error code 1 Stop. make: stopped in /usr0/freebsd/ports/head/graphics/rubygem-fastimage yasu@rolling-vm-freebsd2[2014]% Would someone please help me to fix it? Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: php56
From: tech-lists Subject: php56 Date: Sun, 13 Jan 2019 12:29:36 + > Is there a way of installing php56 and php56-extensions from ports or > packages now? > > I know it's EoL, but need it because I need to support a (non-ports) > program for the time being and said program will not work under php7* > > context is 11-stable/amd64 > > thanks, svn checkout -r 488893 /usr/ports --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Request for help: remove bundler from ruby 2.6 port
From: Yasuhiro KIMURA Subject: Re: Request for help: remove bundler from ruby 2.6 port Date: Sun, 30 Dec 2018 10:35:14 +0900 (JST) > Thank you for reply. Then I'm going to create full port and post here > again. Created. https://www.utahime.org/FreeBSD/ports/lang_ruby26.20190105.patch Please take following step to apply this patch. 1. cd /usr/ports 2. svn copy lang/ruby25 lang/ruby26 3. svn delete lang/ruby26/pkg-message 4. svn patch /path/to/this/patch This time it is full port. So it includes following modules/commands that are removed from lang/ruby2[234]. * Gem * Rake * GDBM And it make back end dbm library of DBM module selectable from following ones. * Berkeley DB (Default) * GDBM * libc * QDBM --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Request for help: remove bundler from ruby 2.6 port
From: Adam Weinberger Subject: Re: Request for help: remove bundler from ruby 2.6 port Date: Sat, 29 Dec 2018 15:34:17 -0700 > I think perhaps it's worth considering doing the opposite and, > beginning with 2.6, install the entire standard library by default. > Gems and stdlib exist side-by-side without problem, and many of the > gems that are deleted are generally kept up-to-date. > > Even if we don't want to install the entire standard library, I'd at > least strongly argue for including the most important gems (rake, gem, > minitest, and bundler) by default. They are basic components of ruby > itself, and ports should provide //optional// newer versions of them. From: Pete Wright Subject: Re: Request for help: remove bundler from ruby 2.6 port Date: Sat, 29 Dec 2018 16:41:32 -0800 > +1 from me on this. > > i think the benefits of lowering the porting overhead combined with > the fact that most ruby envs i've supported (and currently support) > are built around the expectation that rake, gem and bundler are all > available - so this would lower my administrative overhead as well. Thank you for reply. Then I'm going to create full port and post here again. But I'm away from this evening to next Saturday and can't access development environment during that time. So if someone else want to try it, please don't hesitate. Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Request for help: remove bundler from ruby 2.6 port
Hello all, Ruby 2.6.0 is released and I tried porting it. After creating start point by 'svn copy lang/ruby25 lang/ruby26', I made following changes. https://www.utahime.org/FreeBSD/ports/lang_ruby26.patch It is build successfully and works fine on 12.0-RELEASE amd64. But there is still one issue left. >From 2.6.0 ruby includes 'bundler'. But according to the convention of ruby port it should be removed from ruby core port in the same way as 'gem' and 'rake'. I learned from Makefile that it is achieved by removing related files from source tree at post-patch target. However I don't know enough about what files need to be removed to cleanly remove bundler from ruby 2.6 port. So would someone please help me about it? Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Bug report commit request
Dear Committers, Would someone please commit following bug report? [NEW PORT] mail/s-nail: Send and receive Internet mail https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232189 Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
From: Michael Grimm Subject: Re: security/clamav-milter fails to compile (preliminary patch included) Date: Sat, 22 Dec 2018 23:11:09 +0100 > Thank you very, very much, your patch works in my case (lacking sendmail in > base). > > mike> poudriere bulk -j stable -C security/clamav-milter > > … will run to completion, see: > > ===> clamav-milter-0.100.2,1 depends on shared library: libmilter.so > - not found > ===> Installing existing package /packages/All/libmilter-8.15.2_1.txz > [stable-default-job-01] Installing libmilter-8.15.2_1... > [stable-default-job-01] Extracting libmilter-8.15.2_1: .. done > ===> clamav-milter-0.100.2,1 depends on shared library: libmilter.so > - found (/usr/local/lib/libmilter.so) > ===> Returning to build of clamav-milter-0.100.2,1 > > Thank you very much. Your patch is much more elegant then my one ;-) Thank you for checking patch. Then I'll submit this patch to Bugzilla. I may take for a while but will be committed to ports repository. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
From: Michael Grimm Subject: Re: security/clamav-milter fails to compile (preliminary patch included) Date: Sat, 22 Dec 2018 22:20:04 +0100 > If I do set the option to create the milter interface (sp?) in > security/clamav I do run into the same error "Cannot find libmilter". > > I didn't try to build security/clamav without milter support, though. Due to > obvious reasons, because I do need the milter support for postfix. Thank you for replay. Then please try following patch. With it security/clamav (and security/clamav-milter) should depend on mail/libmilter only when there isn't sendmail in base system. Index: Makefile === --- Makefile(revision 488063) +++ Makefile(working copy) @@ -15,6 +15,10 @@ LIB_DEPENDS= libltdl.so:devel/libltdl \ libcurl.so:ftp/curl +.if !exists(/usr/lib/libmilter.so) +LIB_DEPENDS+= libmilter.so:mail/libmilter +.endif + USES= cpe gmake gnome libtool ncurses pathfix pkgconfig ssl USE_RC_SUBR= clamav-clamd clamav-freshclam USE_LDCONFIG= yes Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
From: Michael Grimm Subject: Re: security/clamav-milter fails to compile (preliminary patch included) Date: Sat, 22 Dec 2018 21:47:50 +0100 > See my last mail. I do not have sendmail compiled for base, thus I am lacking > libmilter.so.X in my poudriere jail. > Yes, that is non-default ;-) My port has default settings. Sorry, I read only first mail. Then I have another question. Does build of security/clamav, master port of security/clamav-milter, also fail on your environment? --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
Hello Michael. From: Michael Grimm Subject: security/clamav-milter fails to compile (preliminary patch included) Date: Sat, 22 Dec 2018 17:14:11 +0100 > after upgrading from STABLE-11 to STABLE-12 security/clamav-milter failed to > compile: > > configure: error: Cannot find libmilter > ===> Script "configure" failed unexpectedly. > Please report the problem to y...@utahime.org [maintainer] and attach > the > > "/wrkdirs/usr/ports/security/clamav-milter/work/clamav-0.100.2/config.log" > including the output of the failure of your make command. Also, it > might be > a good idea to provide an overview of all packages installed on your > system > (e.g. a /usr/local/sbin/pkg-static info -g -Ea). > *** Error code 1 > > Stop. I tried build with poudriere under following conditions. Host: FreeBSD rolling-vm-freebsd1.home.utahime.org 13.0-CURRENT FreeBSD 13.0-CURRENT r342280 GENERIC amd64 Poudriere: 3.2.8 Jails: 1. 13.0-CURRENT r342280 amd64 Build from source tree. 2. 12.0-STABLE r341991 amd64 Installed from https://download.freebsd.org/ftp/snapshots/amd64/12.0-STABLE/ 3. 12.0-RELEASE-p1 amd64 Installed from https://download.freebsd.org/ftp/releases/amd64/12.0-RELEASE/ 4. 11.2-STABLE r341995 amd64 Installed from https://download.freebsd.org/ftp/snapshots/amd64/11.2-STABLE/ 5. 11.2-RELEASE-p7 amd64 Installed from https://download.freebsd.org/ftp/releases/amd64/11.2-RELEASE/ Ports tree: r488063 And build of security/clamav-milter succeeded with all cases. Do you use any non-default setting about clamav-milter itself or any of its dependencies? --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Building devel/llvm60 on FreeBSD 12.0
From: Carmel NY Subject: Building devel/llvm60 on FreeBSD 12.0 Date: Tue, 18 Dec 2018 16:41:27 + > Has anyone, besides me of course, had a problem building "devel/llvm60" after > updating to FreeBSD 12.0-RELEASE? Host: FreeBSD rolling-vm-freebsd2.home.utahime.org 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC amd64 Clean installed Poudriere: 3.2.8 Jail: JAILNAME VERSION ARCH METHOD TIMESTAMP PATH 120amd64 12.0-RELEASEamd64 ftp2018-12-14 04:46:41 /usr/local/poudriere/jails/120amd64 Ports tree: Path: /usr/ports Working Copy Root Path: /usr/ports URL: https://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 487713 Node Kind: directory Schedule: normal Last Changed Author: garga Last Changed Rev: 487713 Last Changed Date: 2018-12-18 06:02:00 +0900 (Tue, 18 Dec 2018) Result: https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/120amd64-local/2018-12-19_02h39m00s/logs/llvm60-6.0.1_4.log Just FYI. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/jsoncpp and staging?
From: Steve Kargl Subject: Re: devel/jsoncpp and staging? Date: Tue, 18 Dec 2018 08:21:46 -0800 >> I cannot reproduce the error you encounter, what version of FreeBSD are >> you running? > FreeBSD sleepdirt 13.0-CURRENT FreeBSD 13.0-CURRENT r341703 HPC amd64 > This corresponds to a /usr/src from Dec. 7, 2018. I experienced same problem with 13.0-CURRENT r341690. See thread starting with following message for more detail. https://lists.freebsd.org/pipermail/freebsd-current/2018-December/072355.html Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Ports build fails on 13-CURRENT r341690
From: Justin Hibbits Subject: Re: Ports build fails on 13-CURRENT r341690 Date: Wed, 12 Dec 2018 10:37:25 -0600 > I see the exact same problem on one of my powerpc64 machines (a > P5020-based machine). I see it intermittently on my POWER9, so thought > it was a race condition, but it's 100% reproducible on my P5020 machine. Thank you for reply. I updated my system to r342006 and now the problem disappeared. Just FYI. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ClamAV Port Version Regression?,ClamAV Port Version Regression?
Hello Janky.
From: "Janky Jay, III"
Subject: ClamAV Port Version Regression?,ClamAV Port Version Regression?
Date: Tue, 11 Dec 2018 10:51:43 -0700
> After a portsnap to pull ${latest), I'm seeing the following:
>
> clamav-0.101.0_2 < needs updating (index has 0.100.2,1)
>
> The version that is claiming to be the latest appears to be a version
> regression. Am I wrong here? I checked the ClamAV site and it appears
> version 0.101.0 is, in fact, the latest. So, I'm wondering if there was
> possibly a revision issue that's causing this?
The problem about libclamav API is found in 0.101.0.
http://lists.clamav.net/pipermail/clamav-users/2018-December/007236.html
This results in build error of some ports that depends on
security/clamav. So it is downgraded to 0.100.2 until 0.101.1 is
released.
---
Yasuhiro KIMURA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Ports build fails on 13-CURRENT r341690
Hello, yasu@rolling-vm-freebsd1[2018]% uname -a FreeBSD rolling-vm-freebsd1.home.utahime.org 13.0-CURRENT FreeBSD 13.0-CURRENT r341690 GENERIC amd64 yasu@rolling-vm-freebsd1[2019]% LANG=C svn info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: https://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 341690 Node Kind: directory Schedule: normal Last Changed Author: kib Last Changed Rev: 341690 Last Changed Date: 2018-12-08 00:19:00 +0900 (Sat, 08 Dec 2018) yasu@rolling-vm-freebsd1[2020]% LANG=C svn info /usr/ports Path: /usr/ports Working Copy Root Path: /usr/ports URL: https://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 487116 Node Kind: directory Schedule: normal Last Changed Author: yuri Last Changed Rev: 487116 Last Changed Date: 2018-12-10 10:06:34 +0900 (Mon, 10 Dec 2018) Build of ports-mgmt/pkg fails as following. -- > Compressing man pages (compress-man) === === ===> Building package for pkg-1.10.5_5 install -l rs /.npkg/All/pkg-1.10.5_5.txz /.npkg/Latest/pkg.txz install: /.npkg/All/pkg-1.10.5_5.txz: realpath: No such file or directory *** Error code 71 Stop. make[1]: stopped in /usr/ports/ports-mgmt/pkg *** Error code 1 Stop. make: stopped in /usr/ports/ports-mgmt/pkg =>> Cleaning up wrkdir ===> Cleaning for pkg-1.10.5_5 build of ports-mgmt/pkg | pkg-1.10.5_5 ended at Mon Dec 10 16:49:35 JST 2018 build time: 00:03:50 !!! build failure encountered !!! -- Full build log: https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/curamd64-local/2018-12-10_16h45m20s/logs/errors/pkg-1.10.5_5.log And this prevent any other ports from building. Does anyone else experience it? Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Bug report commit request
Dear committers, Would someone please commit following 4 bug reports? Bug 229647 - emulators/virtualbox-ose-additions: Make broken when DEBUG option is ON https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229647 Bug 230289 - lang/ruby23 lang/ruby24 lang/ruby25: Remove dbm library and replace it with databases/rubygem-dbm https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230289 Bug 230297 - ports-mgmt/portupgrade ports-mgmt/portupgrade-devel: Switch to use databases/rubygem-dbm https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230297 Bug 230301 - Mk/Uses/bdb.mk: Remove WITH_BDB6_PERMITTED https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230301 Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Bug report commit request
Dear Committers, Would someone please commit following 4 bug reports? Bug 230145 - devel/boehm-gc: enable static libraries https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230145 Bug 230289 - lang/ruby23 lang/ruby24 lang/ruby25: Remove dbm library and replace it with databases/rubygem-dbm https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230289 Bug 230297 - ports-mgmt/portupgrade ports-mgmt/portupgrade-devel: Switch to use databases/rubygem-dbm https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230297 Bug 230301 - Mk/Uses/bdb.mk: Remove WITH_BDB6_PERMITTED https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230301 Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Regression of dtrace on 13-CURRENT
From: Yasuhiro KIMURA Subject: Regression of dtrace on 13-CURRENT Date: Thu, 25 Oct 2018 14:46:00 +0900 (JST) > So there is regression about dtrace between r339436 and r339548. I submitted this problem to Bugzilla. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Regression of dtrace on 13-CURRENT
Hello.
On 13-CURRENT r339548 build of lang/perl5.26 fails with configure error.
--
yasu@rolling-vm-freebsd1[2100]% uname -a
FreeBSD rolling-vm-freebsd1.home.utahime.org 13.0-CURRENT FreeBSD 13.0-CURRENT
r339548 GENERIC_UTAHIME amd64
yasu@rolling-vm-freebsd1[2101]% pwd
/usr/ports/lang/perl5.26
yasu@rolling-vm-freebsd1[2102]% make
===> License ART10 GPLv1+ accepted by the user
===> perl5.26-5.26.2 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by perl5.26-5.26.2 for building
===> Extracting for perl5.26-5.26.2
=> SHA256 Checksum OK for perl/perl-5.26.2.tar.xz.
/bin/ln -s libperl.so.5.26.2
/usr0/freebsd/ports/work/net/freebsd/ports/head/lang/perl5.26/work/perl-5.26.2/libperl.so
/bin/ln -s libperl.so.5.26.2
/usr0/freebsd/ports/work/net/freebsd/ports/head/lang/perl5.26/work/perl-5.26.2/libperl.so.5.26
===> Patching for perl5.26-5.26.2
===> Applying FreeBSD patches for perl5.26-5.26.2
/usr/bin/sed -i.bak -e 's|/usr/local|/usr/local|g'
/usr0/freebsd/ports/work/net/freebsd/ports/head/lang/perl5.26/work/perl-5.26.2/Configure
/usr0/freebsd/ports/work/net/freebsd/ports/head/lang/perl5.26/work/perl-5.26.2/hints/freebsd.sh
/usr/bin/sed -i.bak -e '/do_installprivlib = 0 if .versiononly/d;
/^if.*nopods.*versiononly || /s/.*/if (1) {/'
/usr0/freebsd/ports/work/net/freebsd/ports/head/lang/perl5.26/work/perl-5.26.2/installperl
===> Configuring for perl5.26-5.26.2
First let's make sure your kit is complete. Checking...
(snip)
Colon-separated list of additional directories for perl to search? [none]
Checking out function prototypes...
Support DTrace if available? [y]
Where is the dtrace executable? (~name ok) [/usr/sbin/dtrace]
*** Configure: Fatal Error: /usr/sbin/dtrace doesn't support -h flag
***
*** Your installed dtrace doesn't support the -h switch to compile a D
*** program into a C header. Can't continue.
===> Script "Configure" failed unexpectedly.
Please report the problem to m...@freebsd.org [maintainer] and attach the
"/usr0/freebsd/ports/work/net/freebsd/ports/head/lang/perl5.26/work/perl-5.26.2/config.log"
including the output of the failure of your make command. Also, it might be
a good idea to provide an overview of all packages installed on your system
(e.g. a /usr/local/sbin/pkg-static info -g -Ea).
*** Error code 1
Stop.
make: stopped in /net/freebsd/ports/head/lang/perl5.26
yasu@rolling-vm-freebsd1[2103]%
--
In perl-5.26.2/Configure there is following test.
--
if $test -f $dtrace
then
if $dtrace -h -s ../perldtrace.d \
-o perldtrace.tmp >/dev/null 2>&1 \
&& rm -f perldtrace.tmp
then
echo " "
echo "Good: your $dtrace knows about the -h flag."
else
cat >&2
Re: Build of python 3.7.1 succeeds with poudriere but fails with real system
From: Walter Schwarzenfeld Subject: Re: Build of python 3.7.1 succeeds with poudriere but fails with real system Date: Sun, 21 Oct 2018 21:34:41 +0200 > There is an new PR > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232510 Thanks. I added myself to CC list of this PR. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Build of python 3.7.1 succeeds with poudriere but fails with real system
Hello. With r482664 lang/python37 was updated to 3.7.1. So I updated ports tree and built it. With poudriere build completed successfully. But with real system build failed as following. --- libpython3.so --- cc -pthread -shared -L/usr/local/lib -fstack-protector -Wl,--no-as-needed -o libpython3.so -Wl,-hlibpython3.so --- python --- --- Programs/_testembed --- --- python --- cc -pthread -L/usr/local/lib -fstack-protector -Wl,--export-dynamic -o python Programs/python.o -L. -lpython3.7m -lintl -ldl -L/usr/local/lib -lintl -lutil -lm --- Programs/_testembed --- cc -pthread -L/usr/local/lib -fstack-protector -Wl,--export-dynamic -o Programs/_testembed Programs/_testembed.o -L. -lpython3.7m -lintl -ldl -L/usr/local/lib -lintl -lutil -lm Programs/_testembed.o: In function `test_init_from_config': _testembed.c:(.text+0xd28): undefined reference to `_Py_InitializeFromConfig' Programs/_testembed.o: In function `test_init_dev_mode': _testembed.c:(.text+0xe0f): undefined reference to `_Py_InitializeFromConfig' Programs/_testembed.o: In function `test_init_isolated': _testembed.c:(.text+0xeb3): undefined reference to `_Py_InitializeFromConfig' cc: error: linker command failed with exit code 1 (use -v to see invocation) --- pybuilddir.txt --- --- Programs/_testembed --- *** [Programs/_testembed] Error code 1 make[1]: stopped in /usr0/freebsd/ports/work/usr0/freebsd/ports/head/lang/python37/work/Python-3.7.1 --- pybuilddir.txt --- LD_LIBRARY_PATH=/usr0/freebsd/ports/work/usr0/freebsd/ports/head/lang/python37/work/Python-3.7.1 ./python -E -S -m sysconfig --generate-posix-vars ; if test $? -ne 0 ; then echo "generate-posix-vars failed" ; rm -f ./pybuilddir.txt ; exit 1 ; fi 1 error make[1]: stopped in /usr0/freebsd/ports/work/usr0/freebsd/ports/head/lang/python37/work/Python-3.7.1 ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make: stopped in /usr0/freebsd/ports/head/lang/python37 yasu@with[572]% I tried on 11.2-RELEASE/12.0-BETA1 amd64 and got same result. Does anyone else experienced this? Or are there anyone who succeeded to build on real system? Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bug report commit request
2018年7月30日 03:44, "Kurt Jaeger" wrote: > Hi! > >> Bug 228861 - mail/mew: Update to 6.8 and etc >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228861 >> >> Testbuilds@work > > Committed, thanks! Thank you for committing them. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Bug report commit request
Dear Committers, Would someone please commit following 2 bug reports? Bug 228861 - mail/mew: Update to 6.8 and etc https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228861 Bug 229077 - textproc/multimarkdown: Switch to 'USES=localbase:ldflags' https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229077 Bug 228861 is maintainer timeout (49days). Bug 229077 is update of non-maintainer port. Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bug report commit request
Ninix distribution site http://www.geocities.co.jp/SiliconValley-Cupertino/7565/ Home page of ninix-aya developement projcet http://ninix-aya.osdn.jp/ Ninix-aya distribution site http://osdn.jp/projects/ninix-aya/ Concluded. -- Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bug report commit request
From: Kurt Jaeger Subject: Re: Bug report commit request Date: Sun, 17 Jun 2018 18:15:04 +0200 >> Bug 228241 - games/ninix-aya: Change MASTER_SITES to DEBIAN_POOL >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228241 > > The official dist-site is SF, and there's a version 5.0.5 available. > > Any reason why updating from 4.4 to 5.0.5 is not feasable ? > >> Bug 228242 - japanese/font-ume: Fix MASTER_SITES >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228242 > > We have 0.0.660, but the dist site @osdn has 0.0.670 ? > >> Bug 228243 - japanese/FreeWnn-server: Remove ftp.freewnn.org from >> MASTER_SITES >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228243 > > We have 1.1.1.a021, the dist-site has a023 ? 1. I found these problems when I submitted following bug report. Bug 225609 - Mk/bsd.sites.mk: rename MASTER_SITE_SOURCEFORGE_JP to MASTER_SITE_OSDN https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225609 2. When I submitted it I found fetching problem of these ports as secondary problem. it is not unclear if the problem is temporary or not. So at the time I left it as it is. 3. Bug 225609 was committed on March 25 and my main purpose is achieved. 4. About a month ago I remembered this problem and confirmed it is not temporary. 5. I myself don't have motivation to update these ports because I don't use any of then. Especially there seems to be large change of build conditions of games/ninix-aya from 4.4 to 5.0.5. So I only fixed fetching problem of these ports. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Removing git dependencies on perl5 and python27
From: Joseph Mingrone
Subject: Re: Removing git dependencies on perl5 and python27
Date: Sun, 17 Jun 2018 05:59:46 -0300
> Mahmoud Al-Qudsi writes:
>> Do you know what features python unlocks?
> I am not sure, but grepping gives some hints.
>From /usr/ports/devel/git/Makefile
--
OPTIONS_DEFINE= GUI SVN GITWEB CONTRIB P4 CVS HTMLDOCS PERL ICONV CURL \
SEND_EMAIL NLS PCRE SUBTREE
OPTIONS_DEFAULT=CONTRIB P4 CVS PERL GITWEB ICONV CURL SEND_EMAIL PCRE \
SUBTREE
(snip)
CONTRIB_DESC= Install contributed scripts
P4_DESC=Enable Perforce support
(snip)
.if ${PORT_OPTIONS:MP4} || ${PORT_OPTIONS:MCONTRIB}
USES+= python
CONFIGURE_ARGS+=--with-python=${PYTHON_CMD}
.else
CONFIGURE_ARGS+=--without-python
.endif
--
So python is required
* To use some of contributed scripts.
* To import from and submit to Perforce repositories.
I'm not sure if P4 option should be enabled by default. But I think it
is incosistent that default valued of P4 options is on while that of
SVN options is off.
---
Yasuhiro KIMURA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Bug report commit request
Dear Committers, Would someone please commit following bug reports? Bug 228241 - games/ninix-aya: Change MASTER_SITES to DEBIAN_POOL https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228241 Bug 228242 - japanese/font-ume: Fix MASTER_SITES https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228242 Bug 228243 - japanese/FreeWnn-server: Remove ftp.freewnn.org from MASTER_SITES https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228243 As for bug 228241 there isn't maintainer of games/ninix-aya. And regarding bug 228242 and 228243 there aren't any responces from maintainer for a month. Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Breakage of editors/tamago
From: Robert Huff Subject: Re: Breakage of editors/tamago (Re: build errors after upgrading editors/emacs to version 26.1) Date: Thu, 7 Jun 2018 16:58:54 -0400 > Additional data points: > 1) Under Emacs, vm (mail reader viewmail) compiled for Emacs 25.3 > does not work for 26.1. > 2) Attempts to compile vm-8.2.0b under Emacs 26.1 fail due to > changes in how Emacs > processes Lisp. This is a registered bug, at > "https://bugs.launchpad.net/vm/+bug/1763377;. > There is a patch, which at least in my case fixes one problem > but reveals another. (Build log > available on request.) > Thank you for information. At first I'll check the bug report. Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Breakage of editors/tamago (Re: build errors after upgrading editors/emacs to version 26.1)
Hello all, From: Joseph Mingrone Subject: build errors after upgrading editors/emacs to version 26.1 Date: Tue, 29 May 2018 22:17:00 -0300 > Poudriere tests of all 'USES=emacs' ports with the latest editors/emacs > (version 26.1) resulted in the following errors in either 10i386 or > 11amd64 jails: > > editors/tamago (hrs@) I'm investigating breakage of this port and submitted report of current status as following bug report. Bug 228812 - editors/tamago: This port is broken only with restrected conditions https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228812 Summary of report is * This port is not broken with real environment (i.e. not poudriere). it applies to all flavors. * With poudriere full, canna and nox are broken. devel_full and devel_nox are not. * Accoding to the error message of poudriere build log, source of build failure may be bug of Emacs 26.1. I'll continue to investigating this problem. But to be honest I'm far from emacs lisp expert, and I know almost nothing about inside of Emacs either. So please give me hint, idea, suggestion, etc if something hits upon you about this problem. Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bug report commit request
From: Kurt Jaeger <li...@opsec.eu> Subject: Re: Bug report commit request Date: Sun, 13 May 2018 13:34:21 +0200 >> Would someone please commit following bug report with maintainer >> timeout? >> Bug 227497 - devel/dash.el: Update to 2.14.1 >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227497 > Done. Thank you. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
