poudriere-devel cross update-builds of ports build-depends failures: "pkg-static: wrong architecture: FreeBSD:12:armv7 instead of FreeBSD:12:amd64" (similarly for FreeBSD:12:aarch64 )

2018-01-28 Thread Mark Millard via freebsd-ports
It has been some time since I did a buildworld (-r327485). The same for builing updated ports. For the following I've not done any0 rebuilds or installs of world, just ports. # svnlite info /usr/ports/ | grep "Re[plv]" Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository

Re: When does a newly committed port become installable via 'pkg'?

2018-01-28 Thread Matthew Seaman
On 28/01/2018 20:14, James E Keenan wrote: > Earlier today (about 0910 EST), thanks to Po-Chuan Hsieh, a new port I > had created was committed to the repository.  It was very quickly > visible at these locations: > > https://svnweb.freebsd.org/ports/head/devel/p5-CPAN-Testers-Common-Client/ >

Re: When does a newly committed port become installable via 'pkg'?

2018-01-28 Thread James E Keenan
On 01/28/2018 05:13 PM, Mike Clarke wrote: On Sunday 28 Jan 2018 13:01:44 Freddie Cash wrote: You can switch to the "latest" repo, which gets rebuilt every Tuesday, I believe. It's more frequent than that now. Packages for 111amd64- default seem to be getting updated about every 2 days.

Re: When does a newly committed port become installable via 'pkg'?

2018-01-28 Thread Mike Clarke
On Sunday 28 Jan 2018 13:01:44 Freddie Cash wrote: > You can switch to the "latest" repo, which gets rebuilt every Tuesday, I > believe. It's more frequent than that now. Packages for 111amd64- default seem to be getting updated about every 2 days. -- Mike Clarke

Re: When does a newly committed port become installable via 'pkg'?

2018-01-28 Thread Mike Clarke
On Sunday 28 Jan 2018 17:01:09 James E Keenan wrote: > Thanks. Upon reading 'man 5 pkg.conf', which identified the system-wide > configuration file as being located as /etc/pkg/FreeBSD.conf. That file > does contain this entry: > > # > url: "pkg+http://pkg.FreeBSD.org/${ABI}/quarterly;, >

Re: When does a newly committed port become installable via 'pkg'?

2018-01-28 Thread Adam Weinberger
On 28 Jan, 2018, at 13:14, James E Keenan wrote: Earlier today (about 0910 EST), thanks to Po-Chuan Hsieh, a new port I had created was committed to the repository. It was very quickly visible at these locations:

Re: When does a newly committed port become installable via 'pkg'?

2018-01-28 Thread James E Keenan
On 01/28/2018 04:01 PM, Freddie Cash wrote: On Jan 28, 2018 12:15 PM, "James E Keenan" > wrote: Earlier today (about 0910 EST), thanks to Po-Chuan Hsieh, a new port I had created was committed to the repository.  It was very quickly

Re: When does a newly committed port become installable via 'pkg'?

2018-01-28 Thread Freddie Cash
On Jan 28, 2018 12:15 PM, "James E Keenan" wrote: Earlier today (about 0910 EST), thanks to Po-Chuan Hsieh, a new port I had created was committed to the repository. It was very quickly visible at these locations:

When does a newly committed port become installable via 'pkg'?

2018-01-28 Thread James E Keenan
Earlier today (about 0910 EST), thanks to Po-Chuan Hsieh, a new port I had created was committed to the repository. It was very quickly visible at these locations: https://svnweb.freebsd.org/ports/head/devel/p5-CPAN-Testers-Common-Client/

Re: daily security run output and joomla3

2018-01-28 Thread Per olof Ljungmark
On 01/28/18 19:31, Baptiste Daroussin wrote: > On Mon, Jan 29, 2018 at 03:27:22AM +0900, Yasuhiro KIMURA wrote: >> From: Larry Rosenman >> Subject: Re: daily security run output and joomla3 >> Date: Sun, 28 Jan 2018 12:04:56 -0600 >> >>> But as the OP notes, the joomla3

Re: daily security run output and joomla3

2018-01-28 Thread Matthew Seaman
On 28/01/2018 18:04, Larry Rosenman wrote: > On Mon, Jan 29, 2018 at 02:56:51AM +0900, Yasuhiro KIMURA wrote: >> From: Carmel NY >> Subject: Re: daily security run output and joomla3 >> Date: Sun, 28 Jan 2018 17:38:10 + >> You can try "pkg check -r", see man

Re: daily security run output and joomla3

2018-01-28 Thread Eugene Grosbein
29.01.2018 1:04, Larry Rosenman wrote: >> Accoding to the messages of security periodic sript, the problrem is >> not checksum mismatch but lost of package files. And "pkg check -r" >> cannot recover it. So you should reinstall www/joomla3. >> > But as the OP notes, the joomla3 instructions

Re: daily security run output and joomla3

2018-01-28 Thread Baptiste Daroussin
On Sun, Jan 28, 2018 at 07:31:00PM +0100, Baptiste Daroussin wrote: > On Mon, Jan 29, 2018 at 03:27:22AM +0900, Yasuhiro KIMURA wrote: > > From: Larry Rosenman > > Subject: Re: daily security run output and joomla3 > > Date: Sun, 28 Jan 2018 12:04:56 -0600 > > > > > But as the

Re: daily security run output and joomla3

2018-01-28 Thread Baptiste Daroussin
On Mon, Jan 29, 2018 at 03:27:22AM +0900, Yasuhiro KIMURA wrote: > From: Larry Rosenman > Subject: Re: daily security run output and joomla3 > Date: Sun, 28 Jan 2018 12:04:56 -0600 > > > But as the OP notes, the joomla3 instructions *REQUIRE* > > removal of the install directory

Re: daily security run output and joomla3

2018-01-28 Thread Yasuhiro KIMURA
From: Larry Rosenman Subject: Re: daily security run output and joomla3 Date: Sun, 28 Jan 2018 12:04:56 -0600 > But as the OP notes, the joomla3 instructions *REQUIRE* > removal of the install directory for security reasons, so > I understand where he is coming from. Do you

Re: daily security run output and joomla3

2018-01-28 Thread Baptiste Daroussin
On Sun, Jan 28, 2018 at 12:04:56PM -0600, Larry Rosenman wrote: > On Mon, Jan 29, 2018 at 02:56:51AM +0900, Yasuhiro KIMURA wrote: > > From: Carmel NY > > Subject: Re: daily security run output and joomla3 > > Date: Sun, 28 Jan 2018 17:38:10 + > > > > >>You can try

Re: daily security run output and joomla3

2018-01-28 Thread Carmel NY
On Mon, 29 Jan 2018 02:56:51 +0900, Yasuhiro KIMURA stated: >From: Carmel NY >Subject: Re: daily security run output and joomla3 >Date: Sun, 28 Jan 2018 17:38:10 + > >>>You can try "pkg check -r", see man pkg-check >> >> Unfortunately, that has no affect. >

Re: daily security run output and joomla3

2018-01-28 Thread Larry Rosenman
On Mon, Jan 29, 2018 at 02:56:51AM +0900, Yasuhiro KIMURA wrote: > From: Carmel NY > Subject: Re: daily security run output and joomla3 > Date: Sun, 28 Jan 2018 17:38:10 + > > >>You can try "pkg check -r", see man pkg-check > > > > Unfortunately, that has no affect. >

Re: daily security run output and joomla3

2018-01-28 Thread Yasuhiro KIMURA
From: Carmel NY Subject: Re: daily security run output and joomla3 Date: Sun, 28 Jan 2018 17:38:10 + >>You can try "pkg check -r", see man pkg-check > > Unfortunately, that has no affect. Accoding to the messages of security periodic sript, the problrem is not

Re: daily security run output and joomla3

2018-01-28 Thread Carmel NY
On Sun, 28 Jan 2018 17:51:16 +0100, Miroslav Lachman stated: >Carmel NY wrote on 2018/01/28 11:59: >> FreeBSD-11.1-RELEASE-p6 >> >> I have "www/joomla3" installed and working fine. Part of the configuration >> routine is the removal of the "installation" directory in joomla3 when it is >>

Re: daily security run output and joomla3

2018-01-28 Thread Miroslav Lachman
Carmel NY wrote on 2018/01/28 11:59: FreeBSD-11.1-RELEASE-p6 I have "www/joomla3" installed and working fine. Part of the configuration routine is the removal of the "installation" directory in joomla3 when it is configured. This is done as a security feature and joomla3 advertises that it will

daily security run output and joomla3

2018-01-28 Thread Carmel NY
FreeBSD-11.1-RELEASE-p6 I have "www/joomla3" installed and working fine. Part of the configuration routine is the removal of the "installation" directory in joomla3 when it is configured. This is done as a security feature and joomla3 advertises that it will not run if that directory is present.

FreeBSD ports you maintain which are out of date

2018-01-28 Thread portscout
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,

INDEX now builds successfully on 10.x

2018-01-28 Thread Ports Index build
___ 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"

INDEX build failed for 10.x

2018-01-28 Thread Ports Index build
INDEX build failed with errors: Generating INDEX-10 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- --- describe.astro --- --- describe.audio --- --- describe.benchmarks --- --- describe.biology --- --- describe.cad --- --- describe.chinese --- ---

INDEX build failed for 10.x

2018-01-28 Thread Ports Index build
INDEX build failed with errors: Generating INDEX-10 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- --- describe.astro --- --- describe.audio --- --- describe.benchmarks --- --- describe.biology --- --- describe.cad --- --- describe.chinese --- ---

INDEX build failed for 10.x

2018-01-28 Thread Ports Index build
INDEX build failed with errors: Generating INDEX-10 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- --- describe.astro --- --- describe.audio --- --- describe.benchmarks --- --- describe.biology --- --- describe.cad --- --- describe.chinese --- ---