In message <20190109031415.gc26...@kib.kiev.ua>, Konstantin Belousov
writes:
> On Tue, Jan 08, 2019 at 06:56:11PM -0800, Cy Schubert wrote:
> > In message <20190109022154.gb26...@kib.kiev.ua>, Konstantin Belousov
> > writes:
> > > On Tue, Jan 08, 2019 at 04:47:19PM -0800, Cy Schubert wrote:
> >
On Tue, Jan 08, 2019 at 06:56:11PM -0800, Cy Schubert wrote:
> In message <20190109022154.gb26...@kib.kiev.ua>, Konstantin Belousov
> writes:
> > On Tue, Jan 08, 2019 at 04:47:19PM -0800, Cy Schubert wrote:
> > > Can you provide a complete listing, please. That library didn't build on
> > > yo
>
In message <20190109022154.gb26...@kib.kiev.ua>, Konstantin Belousov
writes:
> On Tue, Jan 08, 2019 at 04:47:19PM -0800, Cy Schubert wrote:
> > Can you provide a complete listing, please. That library didn't build on yo
> ur machine for some reason and we need to find out why. Also, can you also
Can you provide a complete listing, please. That library didn't build on your
machine for some reason and we need to find out why. Also, can you also send a
copy of config.log?
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top
Error install
===> Installing for krb5-1.17
===> Checking if krb5 already installed
===> Registering installation for krb5-1.17 as automatic
pkg-static: Unable to access file
/usr/ports/security/krb5/work/stage/usr/local/lib/krb5/plugins/kdb/klmdb.so:No
such file or directory
*** Error code
Hi Franco,
Am 08.01.2019 um 15:58 schrieb Franco Fichtner:
> Explicit CONFLICTS only exist within the ports tree
> during builds.
>
> pkg detects conflicts simply when files are attempted
> to be installed in the same place -- i.e. a file already
> belongs to another installed package.
hm, this
___
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"
On 1/8/19 3:58 PM, Franco Fichtner wrote:
Hi Matthias,
Explicit CONFLICTS only exist within the ports tree
during builds.
pkg detects conflicts simply when files are attempted
to be installed in the same place -- i.e. a file already
belongs to another installed package.
Cheers,
Franco
On
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 ---
---
Hi Matthias,
Explicit CONFLICTS only exist within the ports tree
during builds.
pkg detects conflicts simply when files are attempted
to be installed in the same place -- i.e. a file already
belongs to another installed package.
Cheers,
Franco
> On 8. Jan 2019, at 3:52 PM, Matthias Fechner
Dear all,
I just implement some changes in the gitlab-ce port which requires some
conflicts.
I tried to add:
CONFLICTS_INSTALL= gitolite-* \
gitolite2-* \
gogs-* \
${PYTHON_PKGNAMEPREFIX}-gitosis-*
My test machine has gitolite and gitlab-ce
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,
12 matches
Mail list logo
