Re: Ports with duplicate LATEST_LINKs

2015-08-24 Thread Matthew Seaman
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

Re: Ports with duplicate LATEST_LINKs

2015-08-24 Thread Julian H. Stacey
Hi, Reference: > From: Ports Index build > 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 use a unique .

Re: Ports with duplicate LATEST_LINKs

2015-08-20 Thread Chris H
On Thu, 20 Aug 2015 11:07:55 -0400 Vick Khera wrote > On Tue, Aug 18, 2015 at 8:37 AM, 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

Re: Ports with duplicate LATEST_LINKs

2015-08-20 Thread Vick Khera
On Tue, Aug 18, 2015 at 8:37 AM, 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

Re: Ports with duplicate LATEST_LINKs

2015-08-19 Thread Greg 'groggy' Lehey
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

Re: Ports with duplicate LATEST_LINKs

2015-08-18 Thread Larry Rosenman
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 po

Re: Ports with duplicate LATEST_LINKs

2015-08-18 Thread Greg 'groggy' Lehey
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

Re: Ports with duplicate LATEST_LINKs

2015-08-18 Thread Kurt Jaeger
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 https:

Re: Ports with duplicate LATEST_LINKs

2015-08-18 Thread John Nielsen
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 https://wiki.freebsd.org/ports/PkgNameColli

Re: Ports with duplicate LATEST_LINKs

2015-08-18 Thread Chris Rees
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 wrote: >Dear port maintainers, > >The following list includes ports maintained by you t

Re: Ports with duplicate LATEST_LINKs

2015-08-18 Thread Stefan Bethke
> Am 18.08.2015 um 14:37 schrieb Ports Index build : > 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 b

Re: Ports with duplicate LATEST_LINKs

2015-08-18 Thread Mathieu Arnold
+--On 18 août 2015 14:53:31 +0200 Michelle Sullivan 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 using PKGNAMESUF

Re: Ports with duplicate LATEST_LINKs

2015-08-18 Thread Michelle Sullivan
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 blo

Re: Ports with duplicate LATEST_LINKs

2014-02-20 Thread Brad Davis
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 > >

Re: Ports with duplicate LATEST_LINKs

2014-02-20 Thread Ruslan Makhmatkhanov
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

Ports with duplicate LATEST_LINKs

2014-02-20 Thread Ports Index build
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: http://

Re: Ports with duplicate LATEST_LINKs

2014-01-11 Thread Danilo E. Gondolfo
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.

Ports with duplicate LATEST_LINKs

2014-01-11 Thread Ports Index build
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: http://

Ports with duplicate LATEST_LINKs

2013-11-08 Thread Ports Index build
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: http://

Ports with duplicate LATEST_LINKs

2013-11-07 Thread Ports Index build
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: http://

Ports with duplicate LATEST_LINKs

2013-10-04 Thread Ports Index build
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 confli

Ports with duplicate LATEST_LINKs

2013-05-21 Thread Ports Index build
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 confli

Ports with duplicate LATEST_LINKs

2013-05-20 Thread Ports Index build
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 confli

Ports with duplicate LATEST_LINKs

2013-05-10 Thread Ports Index build
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 confli

Ports with duplicate LATEST_LINKs

2013-03-27 Thread indexbuild
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 confli

Ports with duplicate LATEST_LINKs

2012-05-25 Thread Erwin Lansing
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 confli

Re: Ports with duplicate LATEST_LINKS

2011-11-17 Thread Chris Rees
On 17 Nov 2011 13:38, "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 ot

Ports with duplicate LATEST_LINKS

2011-11-17 Thread Erwin Lansing
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 confli

Re: Ports with duplicate LATEST_LINKS

2011-02-13 Thread Chris Rees
On 13 February 2011 13:00, 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 o

Ports with duplicate LATEST_LINKS

2011-02-13 Thread Erwin Lansing
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 confli

Re: Ports with duplicate LATEST_LINKS

2010-01-06 Thread Philip M. Gollucci
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 directory

Ports with duplicate LATEST_LINKS

2010-01-06 Thread Erwin Lansing
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 confli

Ports with duplicate LATEST_LINKS

2010-01-05 Thread Erwin Lansing
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 confli

Re: Ports with duplicate LATEST_LINKS

2009-06-06 Thread Stanislav Sedov
On Fri, 5 Jun 2009 14:40:09 GMT Erwin Lansing 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 avoid overwriti

Ports with duplicate LATEST_LINKS

2009-06-06 Thread Erwin Lansing
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 confli

Re: Ports with duplicate LATEST_LINKS

2009-06-05 Thread Stanislav Sedov
On Fri, 5 Jun 2009 18:25:11 +0200 Erwin Lansing 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 ocaml-notk o

Re: Ports with duplicate LATEST_LINKS

2009-06-05 Thread Erwin Lansing
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.

Duplicate LATEST_LINKS

2009-05-20 Thread Pav Lucistnik
Please fix :) adodb/space/portstreesports/databases/adodb m...@freebsd.org adodb/space/portstreesports/databases/adodb5 m...@freebsd.org apache /space/portstreesports/www/apache13 apa...@freebsd.org apache /space/portstree

Ports with duplicate LATEST_LINKS

2006-12-01 Thread Kris Kennaway
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 confli

Ports with duplicate LATEST_LINKS

2006-11-03 Thread Kris Kennaway
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 confli

Ports with duplicate LATEST_LINKS

2006-09-16 Thread Kris Kennaway
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 confli

Ports with duplicate LATEST_LINKS

2006-09-02 Thread Kris Kennaway
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 confli

Re: Ports with duplicate LATEST_LINKS

2006-08-15 Thread Edwin Groothuis
On Wed, Aug 16, 2006 at 10:30:19AM +1000, Edwin Groothuis wrote: > On Tue, Aug 15, 2006 at 07:19:35PM -0400, Kris Kennaway wrote: > postfix mail/postfix [EMAIL PROTECTED] > postfix mail/postfix22 [EMAIL PROTECTED] > > Fixed thes

Re: Ports with duplicate LATEST_LINKS

2006-08-15 Thread Edwin Groothuis
On Tue, Aug 15, 2006 at 07:19:35PM -0400, Kris Kennaway wrote: > LATEST_LINK PORTNAME MAINTAINER > == > mediawikiwww/mediawiki [EMAIL PROTECTED] > mediawiki

Re: Ports with duplicate LATEST_LINKS

2006-08-15 Thread Mikhail Teterin
вівторок 15 серпень 2006 19:19, Kris Kennaway написав: > gpc                  lang/gpc                       [EMAIL PROTECTED] > gpc                  devel/gpc                     [EMAIL PROTECTED] I just renamed the package created by devel/gpc into "libgpc". The directory can now be repo-copied

Ports with duplicate LATEST_LINKS

2006-08-15 Thread Kris Kennaway
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 confli