Hi, Reference:
From: Ports Index build indexbu...@freebsd.org
Date: Tue, 18 Aug 2015 12:37:35 GMT
Ports Index build wrote:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to
On 2015/08/24 14:20, Julian H. Stacey wrote:
have no LATEST_LINK strings, not duplicate values as falsely asserted.
Nothing has LATEST_LINK strings any more. The whole concept of
LATEST_LINK is gone now. The mass email was triggered because of a
forgotten monitoring script that was confused by
On Thu, 20 Aug 2015 11:07:55 -0400 Vick Khera vi...@khera.org wrote
On Tue, Aug 18, 2015 at 8:37 AM, Ports Index build indexbu...@freebsd.org
wrote:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either
On Tue, Aug 18, 2015 at 8:37 AM, Ports Index build indexbu...@freebsd.org
wrote:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
PKGNAME, e.g. by using PKGNAMESUFFIX. Note that
On Wednesday, 19 August 2015 at 9:15:00 +1000, Greg 'groggy' Lehey wrote:
On Tuesday, 18 August 2015 at 12:37:31 +, Ports Index build wrote:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values.
Without counting, it looks
Ports Index build wrote:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is
deprecated. See the portmgr blog
Am 18.08.2015 um 14:37 schrieb Ports Index build indexbu...@freebsd.org:
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is
deprecated.
+--On 18 août 2015 14:53:31 +0200 Michelle Sullivan miche...@sorbs.net
wrote:
| Ports Index build wrote:
| Dear port maintainers,
|
| The following list includes ports maintained by you that have duplicate
| LATEST_LINK values. They should either be modified to use a unique
| PKGNAME, e.g. by
On Tuesday, 18 August 2015 at 12:37:31 +, Ports Index build wrote:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values.
Without counting, it looks like a complete list of all ports,
unsorted. Would it be possible to modify the
On 2015-08-18 18:15, Greg 'groggy' Lehey wrote:
On Tuesday, 18 August 2015 at 12:37:31 +, Ports Index build wrote:
Dear port maintainers,
The following list includes ports maintained by you that have
duplicate
LATEST_LINK values.
Without counting, it looks like a complete list of all
I got an email with this subject but I’m not sure what to do about it. The port
on the list which I maintain (deskutils/autocutsel) doesn’t use LATEST_LINK or
munge PKGNAME at all, and I don’t see any collisions in e.g. INDEX-10.
I tried the recipes at
Hi!
I got an email with this subject but I?m not sure what to do about it.
Ignore it, someone sent the wrong stuff.
--
p...@opsec.eu+49 171 3101372 5 years to go !
___
freebsd-ports@freebsd.org mailing list
Hi,
This looks like a bsd.port.mk or similar change resulting in PKGNAME*FIX not
being put into LATEST_LINK?
Or have these all been broken a while?
Chris
On 18 August 2015 13:37:23 BST, Ports Index build indexbu...@freebsd.org
wrote:
Dear port maintainers,
The following list includes ports
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is
deprecated. See the portmgr blog post for more information:
Ports Index build wrote on 20.02.2014 16:40:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is
deprecated. See the
On Thu, Feb 20, 2014 at 04:56:36PM +0400, Ruslan Makhmatkhanov wrote:
Ports Index build wrote on 20.02.2014 16:40:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
PKGNAME,
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is
deprecated. See the portmgr blog post for more information:
On 01/11/14 10:39, Ports Index build wrote:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is
deprecated. See
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is
deprecated. See the portmgr blog post for more information:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is
deprecated. See the portmgr blog post for more information:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports
On 17 Nov 2011 13:38, Erwin Lansing er...@freebsd.org wrote:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports
On 13 February 2011 13:00, Erwin Lansing er...@freebsd.org wrote:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports
Erwin Lansing wrote:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports
On Fri, 5 Jun 2009 14:40:09 GMT
Erwin Lansing er...@freebsd.org mentioned:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to
On Fri, Jun 05, 2009 at 06:55:39PM +0400, Stanislav Sedov wrote:
I think there was some error in generating this list. How does this
happened that the PKGNAME of lang/ocaml became ocaml-notk? It gets
set to ocaml-notk only if WITHOUT_TK is defined.
Indeed, fixed in the latest revision.
On Fri, 5 Jun 2009 18:25:11 +0200
Erwin Lansing er...@lansing.dk mentioned:
On Fri, Jun 05, 2009 at 06:55:39PM +0400, Stanislav Sedov wrote:
I think there was some error in generating this list. How does this
happened that the PKGNAME of lang/ocaml became ocaml-notk? It gets
set to
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports
On Tue, Aug 15, 2006 at 07:19:35PM -0400, Kris Kennaway wrote:
LATEST_LINK PORTNAME MAINTAINER
==
mediawikiwww/mediawiki [EMAIL PROTECTED]
mediawiki
39 matches
Mail list logo
