** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
Synopsis: new port: dns/bind10
Responsible-Changed-From-To: erwin-po...@freebsd.org
Responsible-Changed-By: erwin
Responsible-Changed-When: Tue Apr 23 11:59:11 UTC 2013
Responsible-Changed-Why:
Release to the masses, I won't have time to look at this
in the foreseeable future, it it's still open
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
...@gmail.com
- *databases/py-bsddb* pyt...@freebsd.org: py25-bsddb-2.5.4_2
py26-bsddb-2.6.6_2
| revision 1.15
| date: 2010/10/28 21:00:08; author: erwin; state: Exp; lines: +1 -1
| Deprecate md5 in favour of sha256 checksums. md5 checksums will no longer
| be generated or checked
; author: mi; state: Exp; lines: +2 -2
| Use SourceForge's mirrors, now that the distfile is available there AND
| no longer available in the interim location.
|
| Pushed by: erwin (pointyhat)
- *games/warsow* da...@freebsd.org: warsow-0.6 warsow-0.42_3
| revision 1.22
| date: 2011
-2.1p2_4
| revision 1.23
| date: 2009/11/09 01:21:34; author: mi; state: Exp; lines: +2 -2
| Use SourceForge's mirrors, now that the distfile is available there AND
| no longer available in the interim location.
|
| Pushed by: erwin (pointyhat)
- *misc/kaddressbook-plugins* k
; author: mi; state: Exp; lines: +2 -2
| Use SourceForge's mirrors, now that the distfile is available there AND
| no longer available in the interim location.
|
| Pushed by: erwin (pointyhat)
- *misc/p5-Geo-Coder-Multiple* w...@freebsd.org: p5-Geo-Coder-Multiple-0.60
p5-Geo-Coder
a repocopy.
Please fix any errors as soon as possible.
The ports tree was updated at Fri Apr 29 2011 12:00:22 UTC.
- *chinese/joe* syl...@freebsd.org: editors/joe
| revision 1.27
| date: 2010/10/28 21:00:07; author: erwin; state: Exp; lines: +1 -1
| Deprecate md5 in favour of sha256
| revision 1.23
| date: 2009/11/09 01:21:34; author: mi; state: Exp; lines: +2 -2
| Use SourceForge's mirrors, now that the distfile is available there AND
| no longer available in the interim location.
|
| Pushed by: erwin (pointyhat)
- *misc/p5-Geo-Coder-Multiple* w...@freebsd.org
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
.
There's a short presentation from BSDCan with some bullet points:
http://people.freebsd.org/~erwin/presentations/20110512-BSDCan-packages-summary.pdf
This is also a topic we'll talk more about at EuroBSDCon next month.
My $0.02: It might be worthy to experiment a branched development
model
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: rubygem-atoulme-Antwrap-0.7.2: no entry for
/usr/ports/devel/rubygem-rjb
Committers on the hook:
arved pav rea thierry
Most recent CVS update was:
U devel/Makefile
U devel/rubygem-atoulme-antwrap/Makefile
U
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: rubygem-atoulme-Antwrap-0.7.2: no entry for
/usr/ports/devel/rubygem-rjb
Committers on the hook:
arved cy pav rea thierry
Most recent CVS update was:
U games/angband/Makefile
U games/angband/distinfo
U
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: linux-f10-gnutls-2.4.2: no entry for
/usr/ports/security/linux-libgcrypt
make_index: linux-f10-gnutls-2.4.2: no entry for
/usr/ports/security/linux-libtasn1
Committers on the hook:
brooks bsam kuriyama sunpoet
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
INDEX build failed with errors:
Generating INDEX-7 - please wait../a/erwin/tindex/ports/Mk/bsd.port.mk, line
2323: Malformed conditional (${PREFIX} == /usr)
/a/erwin/tindex/ports/Mk/bsd.port.mk, line 2959: Malformed conditional
(${PREFIX} == /usr)
/a/erwin/tindex/ports/Mk/bsd.port.mk, line 3060
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
On Sep 26, 2011, at 11:32 AM, Sergey V. Dyatko wrote:
Hi Erwin,
Hi Sergey,
When we can expect INDEX-10.bz2 on http://www.FreeBSD.org/ports/ ? :-)
Later today. Running a test run as we speak :-)
Erwin
___
freebsd-ports@freebsd.org mailing
-BETA3 and as HEAD hasn't diverged
that much, it would be nice if people installed the beta and reported
any bugs found there.
Erwin
--
Erwin Lansing http://droso.org
Prediction is very difficult
especially about the futureer...@freebsd.org
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: py27-zope.component-3.11.0: no entry for
/usr/ports/devel/py-zope.interface
make_index: py27-zope.component-3.11.0: no entry for
/usr/ports/devel/py-zope.interface
make_index: kojoney-0.0.4.1_3: no entry for
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
or autotools, such a fix needs proper testing, for which
we do not currently have the resources as we are concentrating on
releasing 9.0. I would suggest you do the same and make 9.0 the best
release possible during the next few weeks, after that we'll start
looking into 10.0.
Erwin
--
Erwin
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
Warning: Duplicate INDEX entry: qhull-1.0_2
Committers on the hook:
eadler kmoore stephen sunpoet thierry
Most recent CVS update was:
U databases/p5-BSON/Makefile
U databases/p5-BSON/distinfo
U
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
that is sweeping,
i.e. touches a large number of ports, infrastructural changes, commts to
ports with unusually high number of dependencies, and any other commit
that requires the rebuilding of many packages will not be allowed
without prior explicit approval from portmgr after that date.
-erwin
with some fun facts, only 232 ports break on HEAD
currently. Unfortunately, some of these are pretty high profile and
prevent almost 19.000 other ports from building, leaving only slighty
more than 3000 ports to build successfully.
Erwin
--
Erwin Lansing http
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: linux-mplayerplug-in-3.55_3: no entry for
/usr/ports/graphics/linux-tiff
make_index: linux-mplayerplug-in-3.55_3: no entry for
/usr/ports/x11-toolkits/linux-pango
make_index: nspluginwrapper-1.4.4: no entry for
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: git-subversion-1.7.7: no entry for
/usr/ports/devel/subversion-freebsd
make_index: thunar-vcs-plugin-0.1.4_4: no entry for
/usr/ports/devel/subversion-freebsd
make_index: thunar-vcs-plugin-0.1.4_4: no entry for
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
On Fri, Oct 07, 2011 at 11:20:28AM +0200, Erwin Lansing wrote:
In preparation for 9.0 the ports tree will be in feature freeze
after release candidate 2 (RC2)is released, currently planned for
October 17.
Depending on your timezone, October 17 has come and gone and the ports
tree has
high-level overview) documentation is in the
portbuild article[1]. Note that the new codebase mentioned there has moved
to projects/ in svn.
Erwin
1: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/portbuild/index.html
--
Erwin Lansing http://droso.org
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: fvwm-themes-0.7.0_3: no entry for /usr/ports/x11-wm/fvwm2-devel
make_index: fvwm-themes-0.7.0_3: no entry for /usr/ports/x11-wm/fvwm2-devel
make_index: fvwm-crystal-3.0.6_5: no entry for
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: fvwm-crystal-3.0.6_5: no entry for /usr/ports/x11-wm/fvwm2-devel
Committers on the hook:
bf clsung cy swills wen zi
Most recent CVS update was:
U MOVED
U devel/p5-Module-Install/Makefile
U
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: fvwm-crystal-3.0.6_5: no entry for /usr/ports/x11-wm/fvwm2-devel
Committers on the hook:
bf clsung cy ehaupt flo gahr jadawin lwhsu sunpoet swills wen zi
Most recent CVS update was:
U archivers/tardy/Makefile
U
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: fvwm-crystal-3.0.6_5: no entry for /usr/ports/x11-wm/fvwm2-devel
Committers on the hook:
bf clsung cy ehaupt flo gahr jadawin lwhsu mm sunpoet swills wen zi
Most recent CVS update was:
U
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
of the above patch.
The KNOB's existence allow us to turn on the fix only for broken
ports, and easily know what these broken ports are -- so we can
poke maintainers from time to time about upstream fixes, ...
Erwin is currently running a build on i386-10 with this and the
following
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: rubygem-sinatra-1.3.1: no entry for
/usr/ports/www/rubygem-rack-protection
Committers on the hook:
osa stephen swills
Most recent CVS update was:
U databases/redis/Makefile
U databases/redis/distinfo
U
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
on
pointyhat and occassionally someone from portmgr contacts the
maintainers, but if you have some code available I'd be happy to set
this up as a weekly reminder to maintainers.
Erwin
--
Erwin Lansing http://droso.org
Prediction is very difficult
especially about
code 1
Stop in /a/erwin/tindex/ports.
*** Error code 1
Stop in /a/erwin/tindex/ports.
1 error
Committers on the hook:
danfe eadler lwhsu miwi sunpoet
Most recent CVS update was:
U astro/stellarium/Makefile
U astro/stellarium/distinfo
U astro/stellarium/pkg-plist
U databases/fastdb/Makefile
U
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
conflict with
ports maintained by another person, please coordinate your efforts with
them.
Thanks,
Erwin Annoying Reminder Guy III Lansing
LATEST_LINK PORTNAME MAINTAINER
==
idnkit
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: ja-mozc-tool-1.3.911.102: no entry for /usr/ports/lang/gcc42
make_index: ja-scim-mozc-1.3.911.102: no entry for /usr/ports/lang/gcc42
make_index: ja-mozc-server-1.3.911.102: no entry for /usr/ports/lang/gcc42
1 - 100 of 1042 matches
Mail list logo
