INDEX build failed for 8.x
INDEX build failed with errors: Generating INDEX-8 - please wait.."/home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile", line 199: warning: duplicate script for target "pre-install" ignored "/home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile", line 200: warning: duplicate script for target "pre-install" ignored "/home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile", line 201: warning: duplicate script for target "pre-install" ignored "/home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile", line 203: warning: duplicate script for target "pre-install" ignored "/home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile", line 204: warning: duplicate script for target "pre-install" ignored "/home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile", line 206: warning: duplicate script for target "pre-install" ignored Done. make_index: Circular dependency loop found: remmina-plugin-i18n-1.0.0_1 depends upon itself. Committers on the hook: cy danfe fluffy miwi ohauer Most recent SVN update was: Updating '.': UMk/bsd.sites.mk UU mail/pear-MIME_Type/Makefile UU mail/pear-MIME_Type/distinfo Unet/remmina-plugin-xdmcp/Makefile Unet/remmina/Makefile Dnet/remmina/files/remmina.desktop Dnet/remmina/files/patch-remmina_CMakeFiles.txt Anet/remmina/files/patch-FreeRDP-Remmina-b6a55ae Unet/remmina/pkg-plist Unet/remmina-plugin-vnc/Makefile Unet/remmina-plugins/Makefile Unet/remmina-plugins/pkg-plist.plugin Unet/remmina-plugins/bsd.plugin.mk Unet/remmina-plugin-gnome/Makefile UU net/pear-Net_SMTP/Makefile UU net/pear-Net_SMTP/distinfo Unet/freerdp/distinfo Dnet/freerdp/files/patch-libfreerdp-core_fastpath.c Dnet/freerdp/files/patch-libfreerdp-core_orders.c Dnet/freerdp/files/patch-libfreerdp-codec_CMakeLists.txt Dnet/freerdp/files/patch-libfreerdp-gdi_32bpp.c Dnet/freerdp/files/patch-channels-drdynvc-tsmf-ffmpeg-tsmf_ffmpeg.c Dnet/freerdp/files/patch-libfreerdp-codec_color.c Dnet/freerdp/files/patch-libfreerdp-gdi_16bpp.c Dnet/freerdp/files/patch-libfreerdp-gdi_8bpp.c Anet/freerdp/files/patch-channels-tsmf-client-ffmpeg-tsmf_ffmpeg.c Anet/freerdp/files/patch-libfreerdp-locale-timezone.c Unet/freerdp/pkg-plist Unet/freerdp/Makefile Unet/ntp-devel/Makefile Unet/ntp-devel/distinfo Unet/remmina-plugin-nx/Makefile Unet/remmina-plugin-telepathy/Makefile Unet/remmina-plugin-i18n/Makefile Unet/remmina-plugin-rdp/Makefile Udatabases/py-psycopg2/Makefile Udatabases/py-psycopg2/distinfo Ugerman/wordpress/Makefile Ugerman/wordpress/distinfo Udns/pear-Net_DNS2/Makefile Udns/pear-Net_DNS2/distinfo Udevel/pear-HTML_Template_Sigma/Makefile Udevel/pear-HTML_Template_Sigma/distinfo Ddevel/pecl-uploadprogress/files Udevel/pecl-uploadprogress/Makefile UU devel/pecl-uploadprogress/distinfo UU devel/py-setuptools-git/Makefile UU devel/py-setuptools-git/distinfo Udevel/pear-PHP_CodeSniffer/Makefile Udevel/pear-PHP_CodeSniffer/distinfo Udevel/pear-Date_Holidays_Netherlands/Makefile Udevel/pear-Date_Holidays_Netherlands/distinfo Udevel/bugzilla40/Makefile Udevel/bugzilla42/Makefile Udevel/bugzilla44/Makefile Umisc/cloc/Makefile Umisc/cloc/distinfo Ugraphics/lensfun/Makefile Ugraphics/lensfun/distinfo Ugraphics/lensfun/pkg-plist Usecurity/py-bcrypt/Makefile Usecurity/py-bcrypt/distinfo Uirc/p5-POE-Filter-IRCD/Makefile UU irc/p5-POE-Filter-IRCD/distinfo Uirc/p5-POE-Component-IRC/distinfo Uirc/p5-POE-Component-IRC/Makefile Updated to revision 339755. ___ 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"
Re: why are new ports taking so long to commit
Currently there are 1973 ports PR; AFAICR, an all-time high. Many of these are attempting to fix existing ports (1608), particularly, problems with clang and staging. These numbers are overwhelming. You can see the full count at: http://portsmon.freebsd.org/portsoverall.py All I can recommend is that people be patient. mcl ___ 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"
Re: Maximizing the use of binary packages and minimizing building packages
On 14/01/2014 19:35, Matt Reimer wrote: > That's good news. What should I watch for in order to know when Really > Soon Now becomes Now? > The release of pkg-1.3.x Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Maximizing the use of binary packages and minimizing building packages
That's good news. What should I watch for in order to know when Really Soon Now becomes Now? Matt On Tue, Jan 14, 2014 at 12:14 PM, Matthew Seaman wrote: > On 14/01/2014 18:52, Chris Rees wrote: > > Mixing ports and packages is discouraged and can get messy, because > > upgrades can get out of sync... > > Although with recent developments in pkgng, that advice is going to > become outdated Real Soon Now. > > It is already possible to use mostly binary packages but compile some > yourself. However, yes, it can get messy and you need to be careful > about keeping your build tree reasonably in synch with the tree used to > build the official ports. Also, ingeneral, it's much easier to build > your ports when they are at the end of the dependency chain; ie. with > nothing else that depends on them. > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. > PGP: http://www.infracaninophile.co.uk/pgpkey > > > ___ 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"
Re: Maximizing the use of binary packages and minimizing building packages
On 14/01/2014 18:52, Chris Rees wrote: > Mixing ports and packages is discouraged and can get messy, because > upgrades can get out of sync... Although with recent developments in pkgng, that advice is going to become outdated Real Soon Now. It is already possible to use mostly binary packages but compile some yourself. However, yes, it can get messy and you need to be careful about keeping your build tree reasonably in synch with the tree used to build the official ports. Also, ingeneral, it's much easier to build your ports when they are at the end of the dependency chain; ie. with nothing else that depends on them. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Maximizing the use of binary packages and minimizing building packages
On 01/14/14 17:46, Matt Reimer wrote: I'd like to switch from installing and upgrading our packages using portmaster/portupgrade to using pkg + binary packages from the ports cluster as much as possible. I understand that the ports cluster builds its packages using default options, but some of our packages we need built with custom options (e.g. enable mysql for postfix). Is there a tool that can look at /var/db/ports/foo/options and tell which options differ from the default options? Then I could decide whether I can live with the defaults (and therefore use the binary package), or whether to pkg-lock that package and update it by hand using portmaster. Or is there a better way to handle this situation, where I want to use binary packages where possible and only build when necessary? Mixing ports and packages is discouraged and can get messy, because upgrades can get out of sync... Your best bet is to set up a little build server, if you have the hardware-- I just use a computer I have hidden away from my wife for it, which pulls down changes and builds a new repo using Tinderbox every day. It works really well, so if you're interested, I suppose I could bash some of my scripts into shape and document how to do it. Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ 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"
Re: SCHED_ULE bug (was Re: cpuminer mines only on one core regardless of "--threads" option)
14.01.2014, 20:14, "Subbsd" : > On Tue, Jan 14, 2014 at 7:43 PM, Andrey Chernov wrote: > >> On 14.01.2014 17:01, Alexander wrote: >>> on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer >>> from ports and by "pkg install" - result is the same - minerd mines >>> only on one core regardless of "--threads" option. >> ... >>> # top -P >>> CPU 0: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle >>> CPU 1: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle >>> CPU 2: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle >>> CPU 3: 0.0% user, 100% nice, 0.0% system, 0.0% interrupt, 0.0% idle >> This is SCHED_ULE bug, I see _all_ processes (not minerd only in >> particular) stuck to the last CPU too (top's 'C' column is equal to the >> last CPU and never changes), latest -stable i386. It disappears for me >> switching to SCHED_4BSD. >> >> ___ >> 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" > > I think it's the same story seen in the distant 2011: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/163585 reboot didn't help (try on 3 different PCs) I'll try switching to SCHED_4BSD tomorrow (thanks Andrey Chernov) ___ 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"
Maximizing the use of binary packages and minimizing building packages
I'd like to switch from installing and upgrading our packages using portmaster/portupgrade to using pkg + binary packages from the ports cluster as much as possible. I understand that the ports cluster builds its packages using default options, but some of our packages we need built with custom options (e.g. enable mysql for postfix). Is there a tool that can look at /var/db/ports/foo/options and tell which options differ from the default options? Then I could decide whether I can live with the defaults (and therefore use the binary package), or whether to pkg-lock that package and update it by hand using portmaster. Or is there a better way to handle this situation, where I want to use binary packages where possible and only build when necessary? Thanks for your help. Matt ___ 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"
portmgr-lurkers@ promoted to voting members of portmgr@
The FreeBSD Ports Management team is pleased to announce that Mathieu Arnold (mat@) and Antoine Brodin (antoine@) have been promoted to full voting members of the team after a successful launch of the portmgr-lurkers pilot project. Each of them brings new skills and vast experience to the team. Please join me in welcoming them aboard. Thomas on behalf of portmgr@ http://blogs.freebsdish.org/portmgr/2014/01/14/portmgr-lurkers-promoted-to-voting-members-of-portmgr/ ___ 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"
Joe Marcus Clarke steps down from duties on portmgr@
Joe Marcus Clarke, aka marcus@, has stepped down from his duties on the FreeBSD Ports Management Team. Joe was our longest serving member of the team. Among his many accomplishments was being the repocopy source of authority, instrumental in championing tinderbox development and maintaining portlint. On behalf of the Ports Management team, we would like to thank Joe for his many years of service and dedication. Thomas on behalf of portmgr@ http://blogs.freebsdish.org/portmgr/2014/01/14/joe-marcus-clarke-steps-down-from-duties-on-portmgr/ ___ 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"
Re: SCHED_ULE bug (was Re: cpuminer mines only on one core regardless of "--threads" option)
On Tue, Jan 14, 2014 at 7:43 PM, Andrey Chernov wrote: > On 14.01.2014 17:01, Alexander wrote: >> on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer >> from ports and by "pkg install" - result is the same - minerd mines >> only on one core regardless of "--threads" option. > ... >> # top -P >> CPU 0: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle >> CPU 1: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle >> CPU 2: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle >> CPU 3: 0.0% user, 100% nice, 0.0% system, 0.0% interrupt, 0.0% idle > > This is SCHED_ULE bug, I see _all_ processes (not minerd only in > particular) stuck to the last CPU too (top's 'C' column is equal to the > last CPU and never changes), latest -stable i386. It disappears for me > switching to SCHED_4BSD. > > ___ > 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" I think it's the same story seen in the distant 2011: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/163585 ___ 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"
SCHED_ULE bug (was Re: cpuminer mines only on one core regardless of "--threads" option)
On 14.01.2014 17:01, Alexander wrote: > on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer > from ports and by "pkg install" - result is the same - minerd mines > only on one core regardless of "--threads" option. ... > # top -P > CPU 0: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 1: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 2: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 3: 0.0% user, 100% nice, 0.0% system, 0.0% interrupt, 0.0% idle This is SCHED_ULE bug, I see _all_ processes (not minerd only in particular) stuck to the last CPU too (top's 'C' column is equal to the last CPU and never changes), latest -stable i386. It disappears for me switching to SCHED_4BSD. ___ 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"
Re: cpuminer mines only on one core regardless of "--threads" option
14.01.2014, 17:55, "Volodymyr Kostyrko" : > > minerd itself doesn't bind any process/thread to any specific core. And > it just works for me now. > > Can you show your configs or logs? What does `minerd` say, what does > `limit`, is there any other changes to your default configuration that > can possibly limit this. > # /usr/local/bin/minerd --url stratum+tcp://somepoolsite.com: --userpass login.worker:password [2014-01-14 18:05:38] 4 miner threads started, using 'scrypt' algorithm. [2014-01-14 18:05:38] Starting Stratum on stratum+tcp://somepoolsite.com: [2014-01-14 18:05:38] Binding thread 0 to cpu 0 [2014-01-14 18:05:38] Binding thread 1 to cpu 1 [2014-01-14 18:05:38] Binding thread 2 to cpu 2 [2014-01-14 18:05:38] Binding thread 3 to cpu 3 [2014-01-14 18:05:39] Stratum detected new block [2014-01-14 18:05:42] thread 0: 4104 hashes, 1.79 khash/s [2014-01-14 18:05:42] thread 1: 4104 hashes, 1.79 khash/s [2014-01-14 18:05:42] thread 2: 4104 hashes, 1.79 khash/s [2014-01-14 18:05:42] thread 3: 4104 hashes, 1.79 khash/s # top CPU: 0.1% user, 25.0% nice, 0.0% system, 0.0% interrupt, 75.0% idle 82232 root 7 98 19 68392K 6588K RUN 3 0:29 96.09% minerd # top -P CPU 0: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 1: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 2: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 3: 0.0% user, 100% nice, 0.0% system, 0.0% interrupt, 0.0% idle ### # /usr/local/bin/minerd --threads=1 --url stratum+tcp://somepoolsite.com: --userpass login.worker:password [2014-01-14 18:07:55] 1 miner threads started, using 'scrypt' algorithm. [2014-01-14 18:07:55] Starting Stratum on stratum+tcp://somepoolsite.com: [2014-01-14 18:07:57] Stratum detected new block [2014-01-14 18:07:58] thread 0: 4104 hashes, 7.00 khash/s # top CPU: 0.1% user, 25.0% nice, 0.0% system, 0.0% interrupt, 75.0% idle 82247 root 4 122 19 55720K 5160K RUN 3 0:49 98.58% minerd # top -P CPU 0: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 1: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 2: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 3: 0.0% user, 100% nice, 0.0% system, 0.0% interrupt, 0.0% idle that's all logs I think. The same situation on other freebsd 9.1/9.2 x64 PCs ___ 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"
Re: cpuminer mines only on one core regardless of "--threads" option
14.01.2014 15:01, Alexander написав(ла): Hello! on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer from ports and by "pkg install" - result is the same - minerd mines only on one core regardless of "--threads" option. If I start with "--threads" < 1 for example "--threads=3" - minerd start 3 threads BUT in ONE core - so in "top" it looks like 100% on 4-core CPU (but it must be about 300%). Without "--threads" option minerd determines 4-core CPU and start 4 threads in ONE core (4 x 2,5 khash/s, but with "--threads=1" speed is 1 x 10 khash/s, so with "--threads=4" it must be 4 x 10 khash/s) minerd itself doesn't bind any process/thread to any specific core. And it just works for me now. Can you show your configs or logs? What does `minerd` say, what does `limit`, is there any other changes to your default configuration that can possibly limit this. -- Sphinx of black quartz, judge my vow. ___ 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"
cpuminer mines only on one core regardless of "--threads" option
Hello! on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer from ports and by "pkg install" - result is the same - minerd mines only on one core regardless of "--threads" option. If I start with "--threads" < 1 for example "--threads=3" - minerd start 3 threads BUT in ONE core - so in "top" it looks like 100% on 4-core CPU (but it must be about 300%). Without "--threads" option minerd determines 4-core CPU and start 4 threads in ONE core (4 x 2,5 khash/s, but with "--threads=1" speed is 1 x 10 khash/s, so with "--threads=4" it must be 4 x 10 khash/s) On Linux and Windows on my other PCs all works as expected. ___ 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"
Re: security/libssh does not install ssh_threads
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 14.01.14, 9:29, Peter Klett ?: > Hi, > > I'm currently trying to compile the nogui version of > net-p2p/retroshare which has a dependency to libssh-0.5.4. In its > Makefile it includes -lssh and -lssh_threads but the later is not > build / installed by libssh. > [skip] Please update. libssh-0.5.5_1 installs both standard and threaded libs. - -- Dima Panov (flu...@freebsd.org) (KDE, Office)@FreeBSD team Facebook: http://www.facebook.com/fluffy.khv IRC: fluffy@EFNet, fluffykhv@FreeNode twitter: fluffy_khv | skype: dima.panov -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJS1TBdAAoJEPuLoJ3VOY8pal8QAKcXifmM0O0Jv81LewrwyVQF 3E/KE2+az2gx7RsSru9RO0hTXAkUvRh0M15Hogu5+WUX7Ow+tSJHFHUk1D291b2D 1JCNklvzjyfAbZIfFs8HvEiHo9x8YUbIlc/M2OuBls4oAKj7kwiSnCrmvkBqkqqz EmSZlgjlz0lBwBorVtTCBvLhji8BAJVf9xLbnuFqhHBzjurz77675jmmp2hImAcF OniYPzvu4JDmHmdEgqb1dWibTxmZa/eQ7LLnSqI+Y/kiq6iPQWthFYQlp9AN6gFy 4UZDisgVi4JLJ5c9yfelgm9xTroNQzb7/eQS+eezQFD1U+z2Ru7hJ/4h50omHTag lXo6Hv+HxpdU/a+lEkFHJ23QtVlQplpGuBDLFTp4RsUCAPdNcyEhRGKJ7tQsXpcV 6NvrM/zMgaFbZBM9EKvcOK5wjjXxVHtbYCFCZHk4WQvUSmNtMIfUmrGGtZL5iCsj u7eXXB9D59pDm4HloEjoNYe8pSH1HfBgzbWCr9g8CPY5Yibm9Jj7I6uNx+ui9uRb t3dTKSLVqW8VGBJ5n4vzwaAmMImkL+bbHUwGoZgzIi/e0QpMcbYPDtmBTMl1p7mt 8rK5OXFXVX6p6KRTFFxEYcSuLRwVEtLCg0KHcZ4y3e9XZvz+5oQGtDhSkrI7U6Xq rWMsb9ywttN/k2vO2vVL =t1kP -END PGP SIGNATURE- ___ 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"
FreeBSD ports you maintain which are out of date
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, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ games/gtkatlantic | 0.4.3 | 0.4.4 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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"
