Date: Thu, 20 Aug 2015 08:23:30 -0700 From: "Chris H" <bsd-lists@bsdforge.com> To: <freebsd-ports@freebsd.org> Subject: Re: Ports with duplicate LATEST_LINKs Message-ID: <677f9dccb8a0c62247e0fb9867cf1449@ultimatedns.net> In-Reply-To: <CALd%2BdcdVDiqXyFHO5nUdjZgpQEdvFX-VyS0BwwdV0=TiZBiC_w@mail.gmail.com> References: <201508181237.t7ICbxbo026068@portsindexbuild.ysv.freebsd.org>, <CALd%2BdcdVDiqXyFHO5nUdjZgpQEdvFX-VyS0BwwdV0=TiZBiC_w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 20 Aug 2015 11:07:55 -0400 Vick Khera <vivek@khera.org> wrote > On Tue, Aug 18, 2015 at 8:37 AM, Ports Index build <indexbuild@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 NO_LATEST_LINK is > > deprecated. See the portmgr blog post for more information: > > http://blogs.freebsdish.org/portmgr/2013/10/03/package-name-collisions/ > > > > > > > > > I got the above message the other day while on vacation. It *killed* my > mobile mail client, since it was so long and full of email addresses it > wanted to make clickable. > > Anyhow, I have no idea what action I'm supposed to take on the 20 ports > with my name associated. It seems to me it is just a list of every port I > maintain. Please advise. Thanks! Nothing required on your part. The script that generated the email to the list was a misfire, that shouldn't have occurred. Note: I had nothing to do with it. I am only reporting what happened, for your convenience. :) --Chris > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?677f9dccb8a0c62247e0fb9867cf1449>