FreeBSD ports you maintain which are out of date

2020-02-17 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,

Re: amd64->{armv7,aarc64} cross builds of devel/llvm10 (via poudriere-devel): failed in package stage for missing libarcher* files

2020-02-17 Thread Mark Millard via freebsd-ports
On 2020-Feb-17, at 09:56, Mark Millard wrote: > On 2020-Feb-17, at 09:53, Mark Millard wrote: > >> [The native arm64 build worked fine. But the cross builds >> got . . .] >> >> The builds failed with: >> >> > Compressing man pages (compress-man) >> ===> Installing ldconfig

Re: Why is pkg version taking so long?

2020-02-17 Thread Kevin Oberman
Never mind. I had a corrupt /usr/ports/Makefile. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Mon, Feb 17, 2020 at 9:19 AM Kevin Oberman wrote: > Today I ran "pkg version -vl\<" to

Re: amd64->{armv7,aarc64} cross builds of devel/llvm10 (via poudriere-devel): failed in package stage for missing libarcher* files

2020-02-17 Thread Mark Millard via freebsd-ports
On 2020-Feb-17, at 09:53, Mark Millard wrote: > [The native arm64 build worked fine. But the cross builds > got . . .] > > The builds failed with: > > > Compressing man pages (compress-man) > ===> Installing ldconfig configuration file >

amd64->{armv7,aarc64} cross builds of devel/llvm10 (via poudriere-devel): failed in package stage for missing libarcher* files

2020-02-17 Thread Mark Millard via freebsd-ports
[The native arm64 build worked fine. But the cross builds got . . .] The builds failed with: > Compressing man pages (compress-man) ===> Installing ldconfig configuration file ===

Why is pkg version taking so long?

2020-02-17 Thread Kevin Oberman
Today I ran "pkg version -vl\<" to see what ports had been updated. This usually ran in a few seconds. Today it had provided no output after a much longer time and I noticed it was running a "make flavors-package-names" on a large number of the ports installed; perhaps all of them. It ran for over

Re: Starting with poudriere

2020-02-17 Thread Baptiste Daroussin
On Mon, Feb 17, 2020 at 07:55:25AM -0800, George Hartzell wrote: > Baptiste Daroussin writes: > > > > You should really have a look at overlays which are supported in > > poudriere-devel, it will allow you to get rid of portshaker with your use > case: > > > >

Re: Starting with poudriere

2020-02-17 Thread George Hartzell
Baptiste Daroussin writes: > > You should really have a look at overlays which are supported in > poudriere-devel, it will allow you to get rid of portshaker with your use > case: > > https://reviews.freebsd.org/rP510950 > > in poudriere an overlay is just a "regular ports tree"

Bug 244099 - [PATCH] net/ceph14: upgrade to 14.2.7 with dashboard

2020-02-17 Thread Willem Jan Withagen
Can one of the commiters please pickup this update? Thanx, --WjW ___ 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: Starting with poudriere

2020-02-17 Thread Baptiste Daroussin
On Sun, Feb 16, 2020 at 10:18:33AM -0800, George Hartzell wrote: > Dan McGrath writes: > > [...] I am not sure about repo priorities, or how you would deal > > with conflicts with build options that pull in common ports. It is > > something I have been meaning to look into, sorry! Perhaps