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"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ cad/gmsh| 4.0.6 | 4.0.7 +-+ databases/postgresql-plv8js | 1.4.8 | v2.3.9 +-+ devel/py-certsrv| 2.0.0 | 2.1.0 +-+ multimedia/motion | 4.0.1 | release-4.2.1 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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"
Updating "mysql80-server" port
My daily security run summary includes the following: Checking for packages with security vulnerabilities: Database fetched: Sun Dec 9 03:18:49 EST 2018 mysql80-server-8.0.12_2 This has been included in the report for quite some time now. After doing some quick checking, I find that MySQL 8.0.13 has been available since 2018-10-22. I was just wondering why, especially if there is a security problem, this port has not been updated? Thanks! -- Carmel ___ 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: certbot lost certificates , and registration data
On 10/12/2018 13:15, Paul Macdonald via freebsd-questions wrote: Is anyone else seeing py-certbot having lost all installed certs, and the initial registation data? There was an update on the 7th Upgrade of py27-certbot-0.28.0_1,1 to py27-certbot-0.29.1_1,1 and on 3 boxes tested so far, which all had certs, i now see no certs listed and a request to redo the initial registation on attempts to install a new cert. i don't see any issues upstream here: https://github.com/letsencrypt/boulder/issues/ so not sure if this is FBSD thing or not. Paul. passing --config-dir /usr/local/etc/letsencrypt shows expected output, i suspect something has happend with that flag on the upgrade ( i see /etc/letsencrypt directories on affected servers) -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07970339546 e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA Virtual Servers from £50.00pm High specification Dedicated Servers from £150.00pm ___ 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: certbot lost certificates , and registration data
On 10/12/2018 14:10, Paul Macdonald via freebsd-ports wrote:
On 10/12/2018 13:15, Paul Macdonald via freebsd-questions wrote:
Is anyone else seeing py-certbot having lost all installed certs, and
the initial registation data?
There was an update on the 7th
Upgrade of py27-certbot-0.28.0_1,1 to py27-certbot-0.29.1_1,1
and on 3 boxes tested so far, which all had certs, i now see no certs
listed and a request to redo the initial registation on attempts to
install a new cert.
i don't see any issues upstream here:
https://github.com/letsencrypt/boulder/issues/ so not sure if this is
FBSD thing or not.
Paul.
passing --config-dir /usr/local/etc/letsencrypt shows expected output, i
suspect something has happend with that flag on the upgrade ( i see
/etc/letsencrypt directories on affected servers)
This upstream commit:
https://github.com/certbot/certbot/commit/a23d76beb0e2c9539670766045314a5d50f582a2#diff-64ccdc74e8a07f9b039a6254093f1d0d
breaks the post-patch target in the security/certbot port Makefile:
post-patch:
@${REINPLACE_CMD} \
-e 's|/etc/|${LOCALBASE}/etc/|' \
-e 's|/var/lib|/var/db|' \
${WRKSRC}/${PORTNAME}/constants.py
Looks like the REINPLACE_CMD should be applied to
${WRKSRC}/${PORTNAME}/compat.py now.
Or compat.py should be patched to grok FREEBSD_DEFAULT_FOLDERS
Cheers,
Matthew
___
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: certbot lost certificates , and registration data
On 11/12/2018 1:43 am, Matthew Seaman wrote:
On 10/12/2018 14:10, Paul Macdonald via freebsd-ports wrote:
On 10/12/2018 13:15, Paul Macdonald via freebsd-questions wrote:
Is anyone else seeing py-certbot having lost all installed certs, and
the initial registation data?
There was an update on the 7th
Upgrade of py27-certbot-0.28.0_1,1 to py27-certbot-0.29.1_1,1
and on 3 boxes tested so far, which all had certs, i now see no certs
listed and a request to redo the initial registation on attempts to
install a new cert.
i don't see any issues upstream here:
https://github.com/letsencrypt/boulder/issues/ so not sure if this is
FBSD thing or not.
Paul.
passing --config-dir /usr/local/etc/letsencrypt shows expected output,
i suspect something has happend with that flag on the upgrade ( i see
/etc/letsencrypt directories on affected servers)
This upstream commit:
https://github.com/certbot/certbot/commit/a23d76beb0e2c9539670766045314a5d50f582a2#diff-64ccdc74e8a07f9b039a6254093f1d0d
breaks the post-patch target in the security/certbot port Makefile:
post-patch:
@${REINPLACE_CMD} \
-e 's|/etc/|${LOCALBASE}/etc/|' \
-e 's|/var/lib|/var/db|' \
${WRKSRC}/${PORTNAME}/constants.py
Looks like the REINPLACE_CMD should be applied to
${WRKSRC}/${PORTNAME}/compat.py now.
Or compat.py should be patched to grok FREEBSD_DEFAULT_FOLDERS
Cheers,
Matthew
Nice find Matthew.
Prefer the latter (and sent upstream). Can one of you create a bugzilla
issue for this and cc me please.
If you'd like to give a representative/attempted patch a go, please do.
./koobs
___
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: certbot lost certificates , and registration data
On 10/12/2018 14:54, Kubilay Kocak wrote:
On 11/12/2018 1:43 am, Matthew Seaman wrote:
On 10/12/2018 14:10, Paul Macdonald via freebsd-ports wrote:
On 10/12/2018 13:15, Paul Macdonald via freebsd-questions wrote:
Is anyone else seeing py-certbot having lost all installed certs,
and the initial registation data?
There was an update on the 7th
Upgrade of py27-certbot-0.28.0_1,1 to py27-certbot-0.29.1_1,1
and on 3 boxes tested so far, which all had certs, i now see no
certs listed and a request to redo the initial registation on
attempts to install a new cert.
i don't see any issues upstream here:
https://github.com/letsencrypt/boulder/issues/ so not sure if this
is FBSD thing or not.
Paul.
passing --config-dir /usr/local/etc/letsencrypt shows expected
output, i suspect something has happend with that flag on the upgrade
( i see /etc/letsencrypt directories on affected servers)
This upstream commit:
https://github.com/certbot/certbot/commit/a23d76beb0e2c9539670766045314a5d50f582a2#diff-64ccdc74e8a07f9b039a6254093f1d0d
breaks the post-patch target in the security/certbot port Makefile:
post-patch:
@${REINPLACE_CMD} \
-e 's|/etc/|${LOCALBASE}/etc/|' \
-e 's|/var/lib|/var/db|' \
${WRKSRC}/${PORTNAME}/constants.py
Looks like the REINPLACE_CMD should be applied to
${WRKSRC}/${PORTNAME}/compat.py now.
Or compat.py should be patched to grok FREEBSD_DEFAULT_FOLDERS
Cheers,
Matthew
Nice find Matthew.
Prefer the latter (and sent upstream). Can one of you create a bugzilla
issue for this and cc me please.
If you'd like to give a representative/attempted patch a go, please do.
./koobs
I'll take a look at this when I get home from work this evening.
Cheers,
Matthew
___
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: Best way to deal with .pyc files?
On 12/7/18 10:17 AM, John Baldwin wrote:
> On 12/6/18 11:17 AM, Michael Gmelin wrote:
>>
>>
>>> On 6. Dec 2018, at 19:21, John Baldwin wrote:
>>>
>>> The devel/gdb port installs python scripts into
>>> /usr/local/share/gdb/python.
>>> If you then run kgdb as root (not that unusual), it will generate .pyc
>>> files in
>>> those directories that are not deleted by 'pkg delete'. What is the best
>>> way to
>>> handle this case? Should the pkg-plist include @rmtry entries for each pyc
>>> file or is there a better way?
>>>
>>
>> Pre-generate the pyc files on package build and install them with the port,
>> so they become part of plist (there are examples of that in the ports tree,
>> whenever possible for both py27 and py3x).
>
> Ok. One follow-up question. GDB's python bindings work with both py2 and
> py3, but the bindings are optional. Right now PYTHON is a port option
> (but on by default). If I wanted to add flavors I would probably want them
> to be conditional on the option, so the results would be 'gdb' and
> 'gdb-py3' packages by default, but if someone was using poudriere locally
> and disabled python, I would only want to build a single 'gdb' without
> python. So, can I make the flavors conditional on an option or is it too
> late to define flavors after including bsd.ports.options.mk?
>
> That is, can I do something this:
>
> OPTIONS_DEFINE= PYTHON
> OPTIONS_DEFAULT= PYTHON
>
> .include
>
> .if ${PORT_OPTIONS:MPYTHON}
> USES_PYTHON= flavors
> .endif
FYI, this worked:
OPTIONS_DEFINE= DEBUG GDB_LINK GUILE KGDB NLS PYTHON TUI
OPTIONS_DEFAULT=GDB_LINK KGDB NLS PYTHON TUI PORT_READLINE PORT_ICONV
SYSTEM_ZLIB
...
PYTHON_USES=python
...
.include
.if ${PORT_OPTIONS:MPYTHON}
USE_PYTHON= flavors
.endif
.include
--
John Baldwin
___
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"
