Re: Cacti staged and migration issue (was Re: FreeBSD unmaintained ports which are currently scheduled for deletion)
On 08/15/2014 14:16, Kurt Jaeger wrote: Hi! Consequently, I have no idea how to set the owner/group on those directories in stagedir. As can be seen, with some help I was able to find a solution. I also changed the patches to shebangfixes 8-} But: There's a real issue coming up in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192618#c13 Can you have a look and probably provide a write-up on how to migrate a running cacti install to the new hier(7) setup ? I've been using the updated port since last night on a new server install, working well so far. On my old server I would have had to update the configs but I've been meaning to replace it anyway. Thanks. I think it would be a good idea copy or move the pkg-message updated path tips to /usr/ports/UPDATING to increase chances of it being read. ___ 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
Cacti staged and migration issue (was Re: FreeBSD unmaintained ports which are currently scheduled for deletion)
Hi! Consequently, I have no idea how to set the owner/group on those directories in stagedir. As can be seen, with some help I was able to find a solution. I also changed the patches to shebangfixes 8-} But: There's a real issue coming up in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192618#c13 Can you have a look and probably provide a write-up on how to migrate a running cacti install to the new hier(7) setup ? -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote: On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of Dennis Glatting, and lo! it spake thus: do_install in the Makefile does the chown. Generally you'd want to do something more like using @owner/@group in plist, rather than chown'ing in the stage. Doing that would break building as non-root, too. What's the order? plist cannot change owner/group unless it is defined. Or, does plist execution happen /after/ the make process creates the owner/group entries? ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
Hi! On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote: On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of Dennis Glatting, and lo! it spake thus: do_install in the Makefile does the chown. Generally you'd want to do something more like using @owner/@group in plist, rather than chown'ing in the stage. Doing that would break building as non-root, too. What's the order? plist cannot change owner/group unless it is defined. Or, does plist execution happen /after/ the make process creates the owner/group entries? If you some file bin/myfile1 in the pkg-plist which need to be owned by some user etc, then: [...] bin/myfile0 @owner www @group www bin/myfile1 @owner root @group wheel bin/myfile2 [...] should probably work. Can you try it ? -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On 2014-08-13 18:37, Dennis Glatting wrote: On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote: On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of Dennis Glatting, and lo! it spake thus: do_install in the Makefile does the chown. Generally you'd want to do something more like using @owner/@group in plist, rather than chown'ing in the stage. Doing that would break building as non-root, too. What's the order? plist cannot change owner/group unless it is defined. Or, does plist execution happen /after/ the make process creates the owner/group entries? In case the port defines USERS and GROUPS from ports/(U|G)IDs, then this GROUPS/USERS are created in a early step during port / packet installation and they are available before pkg-plist is processed. USERS= $user (list) from UIDs GROUPS= $group (list) from GIDs In case the port requires user / group not in UIDs/GIDs then request an entry for them. -- olli ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On Wed, 2014-08-13 at 18:43 +0200, Kurt Jaeger wrote: Hi! On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote: On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of Dennis Glatting, and lo! it spake thus: do_install in the Makefile does the chown. Generally you'd want to do something more like using @owner/@group in plist, rather than chown'ing in the stage. Doing that would break building as non-root, too. What's the order? plist cannot change owner/group unless it is defined. Or, does plist execution happen /after/ the make process creates the owner/group entries? If you some file bin/myfile1 in the pkg-plist which need to be owned by some user etc, then: [...] bin/myfile0 @owner www @group www bin/myfile1 @owner root @group wheel bin/myfile2 [...] should probably work. Can you try it ? I am setting permissions on directories and the man page for pkg-create isn't clear. It says: @owner user Set default ownership for all subsequent files to user. Use without an arg to set back to default (root) ownership. Perhaps it means files in the generic? Another issue I is the directories are made in the Makefile (do_install) because pkg-create doesn't mention a mkdir function. The Porter's Handbook mentions @exec mkdir however the StageDir WIKI states it is ignored and directory creation should remain in post-install, specifically: Directory creation should remain in the post-install: target (in particular because pkgng doesn't work like pkg_install in that area and pkgng ignores the @exec mkdir, and directly packs the directory even if empty). Consequently, I have no idea how to set the owner/group on those directories in stagedir. ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
Done. Thanks. On Tue, 2014-08-12 at 06:58 +0200, Kurt Jaeger wrote: Hi! On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote: portname: net-mgmt/cacti description:Web-driven graphing interface for RRDTool maintainer: po...@freebsd.org deprecated because: Not staged. See Deleting Cacti would be a problem. Can you submit a patch ? I have a directory tree tested and ready. There are changes, deletions, and additions so I did not create a diff tree against what is currently in the ports tree. I normally use diff -r -u -N old-dir new-dir to create diffs if there are changes, deletions and additions. You can also create a shar of the whole directory: tar cf cacti.shar --format shar cacti What do I do with this? Then you can either create a new problem report (PR) on the bug tracker and add the shar/diff to that problem report as attachment. The bug tracker can be found here: https://bugs.freebsd.org/bugzilla/ Or you put it on some website, post/mail the URL and I'll create the PR. ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
Hi! Done. Thanks. Found it at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192618 Looks cool! I'll test it on poudriere, but it's CEST here and I have to get up early, so it will take probably until tomorrow evening to get to it. -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On Tue, 2014-08-12 at 21:34 +0200, Kurt Jaeger wrote: Hi! Done. Thanks. Found it at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192618 Looks cool! I'll test it on poudriere, but it's CEST here and I have to get up early, so it will take probably until tomorrow evening to get to it. Kewlness. I'm interested in what comes out. ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
Hi! I'll test it on poudriere, but it's CEST here and I have to get up early, so it will take probably until tomorrow evening to get to it. There is one issue with the ordering of 'add the cacti user/group' and 'using it for a chown', but I do not know the fix right away. Will look at it when I find a bit more time. === Generating temporary packing list === Creating users and/or groups. /bin/mkdir -p /usr/local/home/pi/myp/net-mgmt/cacti/work/stage//usr/local/share/cacti /bin/mkdir -p /usr/local/home/pi/myp/net-mgmt/cacti/work/stage/var/log/cacti /bin/mkdir -p /usr/local/home/pi/myp/net-mgmt/cacti/work/stage/var/db/cacti/rra /bin/mkdir -p /usr/local/home/pi/myp/net-mgmt/cacti/work/stage/var/db/cacti/scripts /usr/sbin/chown -R cacti:cacti /usr/local/home/pi/myp/net-mgmt/cacti/work/stage/var/log/cacti /usr/local/home/pi/myp/net-mgmt/cacti/work/stage/var/log/cacti chown: cacti: illegal group name *** Error code 1 -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On Wed, 2014-08-13 at 06:17 +0200, Kurt Jaeger wrote: Hi! I'll test it on poudriere, but it's CEST here and I have to get up early, so it will take probably until tomorrow evening to get to it. There is one issue with the ordering of 'add the cacti user/group' and 'using it for a chown', but I do not know the fix right away. Will look at it when I find a bit more time. === Generating temporary packing list === Creating users and/or groups. /bin/mkdir -p /usr/local/home/pi/myp/net-mgmt/cacti/work/stage//usr/local/share/cacti /bin/mkdir -p /usr/local/home/pi/myp/net-mgmt/cacti/work/stage/var/log/cacti /bin/mkdir -p /usr/local/home/pi/myp/net-mgmt/cacti/work/stage/var/db/cacti/rra /bin/mkdir -p /usr/local/home/pi/myp/net-mgmt/cacti/work/stage/var/db/cacti/scripts /usr/sbin/chown -R cacti:cacti /usr/local/home/pi/myp/net-mgmt/cacti/work/stage/var/log/cacti /usr/local/home/pi/myp/net-mgmt/cacti/work/stage/var/log/cacti chown: cacti: illegal group name *** Error code 1 do_install in the Makefile does the chown. The user+group cacti is defined (USERS+GROUPS) but I guess its installation in passwd/group comes later in the process. The passwd/group insertion use to be done in a script in files, which I did away with. Hmm... ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of Dennis Glatting, and lo! it spake thus: do_install in the Makefile does the chown. Generally you'd want to do something more like using @owner/@group in plist, rather than chown'ing in the stage. Doing that would break building as non-root, too. -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On Thu, 2014-08-07 at 17:36 +0200, Kurt Jaeger wrote: Hi! On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote: portname: net-mgmt/cacti description:Web-driven graphing interface for RRDTool maintainer: po...@freebsd.org deprecated because: Not staged. See Deleting Cacti would be a problem. Can you submit a patch ? I have a directory tree tested and ready. There are changes, deletions, and additions so I did not create a diff tree against what is currently in the ports tree. What do I do with this? ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
Hi! On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote: portname: net-mgmt/cacti description:Web-driven graphing interface for RRDTool maintainer: po...@freebsd.org deprecated because: Not staged. See Deleting Cacti would be a problem. Can you submit a patch ? I have a directory tree tested and ready. There are changes, deletions, and additions so I did not create a diff tree against what is currently in the ports tree. I normally use diff -r -u -N old-dir new-dir to create diffs if there are changes, deletions and additions. You can also create a shar of the whole directory: tar cf cacti.shar --format shar cacti What do I do with this? Then you can either create a new problem report (PR) on the bug tracker and add the shar/diff to that problem report as attachment. The bug tracker can be found here: https://bugs.freebsd.org/bugzilla/ Or you put it on some website, post/mail the URL and I'll create the PR. -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote: portname: net-mgmt/cacti description:Web-driven graphing interface for RRDTool maintainer: po...@freebsd.org deprecated because: Not staged. See http://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-May/80.html expiration date:2014-08-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmtportname=cacti Deleting Cacti would be a problem. ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
Hi! On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote: portname: net-mgmt/cacti description:Web-driven graphing interface for RRDTool maintainer: po...@freebsd.org deprecated because: Not staged. See Deleting Cacti would be a problem. Can you submit a patch ? -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On Thu, 2014-08-07 at 17:36 +0200, Kurt Jaeger wrote: Hi! On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote: portname: net-mgmt/cacti description:Web-driven graphing interface for RRDTool maintainer: po...@freebsd.org deprecated because: Not staged. See Deleting Cacti would be a problem. Can you submit a patch ? Is it not being maintained? I hate this tool (Cacti) but I have to support it for a client. If that means taking over maintenance, then I offer to do so. However, I am not a port maintainer, although I have done some local stuff, so there is a learning curve. A mentor would help. Ditto www/squid where the latest rev is 3.5 but ports is 3.3. I am running a patched 3.4. ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
Am 07.08.2014 um 18:07 schrieb Dennis Glatting: On Thu, 2014-08-07 at 17:36 +0200, Kurt Jaeger wrote: Hi! On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote: portname: net-mgmt/cacti description:Web-driven graphing interface for RRDTool maintainer: po...@freebsd.org deprecated because: Not staged. See Deleting Cacti would be a problem. Can you submit a patch ? Is it not being maintained? No. Setting MAINTAINER=po...@freebsd.org is the placeholder for unmaintained ports. I hate this tool (Cacti) but I have to support it for a client. If that means taking over maintenance, then I offer to do so. However, I am not a port maintainer, although I have done some local stuff, so there is a learning curve. A mentor would help. We have the Porter's Handbook which is a reasonable starting point, and we have the ports mailing list here for support - just toss your questions here. Regarding staging in particular, we also have https://wiki.freebsd.org/ports/StageDir. Ditto www/squid where the latest rev is 3.5 but ports is 3.3. I am running a patched 3.4. The formalities for a ports maintainer are minimal, your e-mail would already be sufficient. Make a copy of the original cacti directory, change it until you think it's good, then make a diff (diff -Nur /old/directory /new/directory) and upload it somewhere, or if you think it's already good to go, file it to our bugzilla and mention the bug ID here, mentioning you made a patch to make it support staging to prevent expiry. ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On 8/08/2014 2:07 AM, Dennis Glatting wrote: On Thu, 2014-08-07 at 17:36 +0200, Kurt Jaeger wrote: Hi! On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote: portname: net-mgmt/cacti description:Web-driven graphing interface for RRDTool maintainer: po...@freebsd.org deprecated because: Not staged. See Deleting Cacti would be a problem. Can you submit a patch ? Is it not being maintained? I hate this tool (Cacti) but I have to support it for a client. If that means taking over maintenance, then I offer to do so. However, I am not a port maintainer, although I have done some local stuff, so there is a learning curve. A mentor would help. Happy to help out Dennis, and there's more of us on IRC who can support you: #bsdports - Efnet #freebsd-ports - Freenode Ditto www/squid where the latest rev is 3.5 but ports is 3.3. I am running a patched 3.4. ___ 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
On 21 April 2013 11:55, Koichiro IWAO m...@vmeta.jp wrote: 2013-04-21 17:30 に lini...@freebsd.org さんは書きました: portname: net-im/rubygem-termtter description:Terminal based Twitter client maintainer: d...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-importname=rubygem-termtter I strongly disagree to delete net-im/rubygem-termtter. It is mismarked as BROKEN by portmgr for one year even if it perfectly works with ruby 1.9. Don't worry, GNATS is checked before any ports are deleted; it won't go anywhere. Most of us have a load of commits queued during the hard freeze, and they haven't gone in yet. Chris ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On 2013-04-21 12:55, Koichiro IWAO wrote: 2013-04-21 17:30 に lini...@freebsd.org さんは書きました: portname: net-im/rubygem-termtter description:Terminal based Twitter client maintainer: d...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-importname=rubygem-termtter I strongly disagree to delete net-im/rubygem-termtter. It is mismarked as BROKEN by portmgr for one year even if it perfectly works with ruby 1.9. Would you mind to test the following patch (update to 2.1.0). http://people.freebsd.org/~ohauer/diffs/rubygem-termtter.diff The patch updates the port to version 2.1.0 (ruby 1.9 is supported since 1.3.x) Patch is not tested, I avoid to install ruby on my machines. ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
I found some problems in your patch. - probably distinfo is not correct - net/rubygem-rubytter needs to be updated to 1.5.0 or newer 2013-04-22 3:47 olli hauer wrote: The patch updates the port to version 2.1.0 (ruby 1.9 is supported since 1.3.x) I can't make out why the port was marked as broken almost 2 years ago. When the port was marked as broken, PORTVERSION was 1.9.0 (already newer than 1.3.x). It can't be broken with ruby 1.9. -- `whois vmeta.jp | nkf -w` meta m...@vmeta.jp 2013-04-22 3:47 olli hauer wrote: On 2013-04-21 12:55, Koichiro IWAO wrote: 2013-04-21 17:30 に lini...@freebsd.org さんは書きました: portname: net-im/rubygem-termtter description:Terminal based Twitter client maintainer: d...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-importname=rubygem-termtter I strongly disagree to delete net-im/rubygem-termtter. It is mismarked as BROKEN by portmgr for one year even if it perfectly works with ruby 1.9. Would you mind to test the following patch (update to 2.1.0). http://people.freebsd.org/~ohauer/diffs/rubygem-termtter.diff The patch updates the port to version 2.1.0 (ruby 1.9 is supported since 1.3.x) Patch is not tested, I avoid to install ruby on my machines. -- `whois vmeta.jp | nkf -w` meta m...@vmeta.jp ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
The problem with portsmon not updating its ports tree has now been solved. 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: FreeBSD unmaintained ports which are currently scheduled for deletion
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/12/2011 10:06, per...@pluto.rain.com wrote: lini...@freebsd.org wrote: portname: misc/gtkfind description: The program to use to have to remember all the options to find(1) maintainer: po...@freebsd.org deprecated because: No more public distfiles, no more upstream expiration date: 2011-12-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=miscportname=gtkfind This was supposed to have been resuscitated. Is its continued inclusion here fallout from the svn/cvs issue, or is there another problem? Don't worry, it's still definitely undeprecated :) Mark, has the tree got out of date again? Chris -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJO8wB6AAoJELCEktHh68rEd6EH/je2T2kBAj2M7ZtMnfb1pA1g s0uhGWUk8YxE0UQuqxty9S0ZRQ/+tOzHS+7PDfvW/MMxVpv6c3nlin+BdlqTrMWV baIjvSr6KBKnSHb6j/LJflAfO9vZVNO5TUNk8dX14qdyon9o1Po7Orf/Hj1gt7by /HgQWuVomSYluQa1i/uIg2I+/iYiPAvV5cNTruJt1Fj5VfEdDPRXVeCUob85HCWJ T6HW67zZnxNlE4oAYrznwGuBle8IsVRbbwwVvnjxCv3/uB8yVIwtW44zdo+Mqc3B GRPwHfLmwhPZ8BaCNvuStYNlqwiiRoAOSgGT3fxtslAe9wV3vLr0gqqo4NQp10Y= =VKNz -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
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
lini...@freebsd.org wrote: portname: misc/gtkfind description:The program to use to have to remember all the options to find(1) maintainer: po...@freebsd.org deprecated because: No more public distfiles, no more upstream expiration date:2011-12-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=miscportname=gtkfind This was supposed to have been resuscitated. Is its continued inclusion here fallout from the svn/cvs issue, or is there another problem? ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On Sun, Dec 11, 2011 at 03:07:44AM -0800, per...@pluto.rain.com wrote: Chris Rees cr...@freebsd.org wrote: Also, its last update appears to be in 2003, and it's long dead s/long dead/in good enough shape to be useful/ Indeed: Project Activity != Project Health http://blogstrapping.com/?page=2011.065.16.43.41 ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On 11 December 2011 18:01, Chad Perrin c...@apotheon.net wrote: On Sun, Dec 11, 2011 at 03:07:44AM -0800, per...@pluto.rain.com wrote: Chris Rees cr...@freebsd.org wrote: Also, its last update appears to be in 2003, and it's long dead s/long dead/in good enough shape to be useful/ Indeed: Project Activity != Project Health http://blogstrapping.com/?page=2011.065.16.43.41 Perry, has kindly (and not for the first time either) stepped up to put his name on the port, which now means that it can stay, and any problems can be addressed by him. If he's right he need never answer any emails about it :) Chris ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On Sun, Dec 11, 2011 at 06:45:48PM +, Chris Rees wrote: On 11 December 2011 18:01, Chad Perrin c...@apotheon.net wrote: On Sun, Dec 11, 2011 at 03:07:44AM -0800, per...@pluto.rain.com wrote: Chris Rees cr...@freebsd.org wrote: Also, its last update appears to be in 2003, and it's long dead s/long dead/in good enough shape to be useful/ Indeed: Project Activity != Project Health http://blogstrapping.com/?page=2011.065.16.43.41 Perry, has kindly (and not for the first time either) stepped up to put his name on the port, which now means that it can stay, and any problems can be addressed by him. If he's right he need never answer any emails about it :) That sounds a bit like the situation with the port I'm maintaining. ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
lini...@freebsd.org wrote: portname: misc/gtkfind description:The program to use to have to remember all the options to find(1) maintainer: po...@freebsd.org deprecated because: No more public distfiles, no more upstream Looking at the Makefile, it appears that this port does not claim to have a MASTER_SITES other than MASTER_SITE_BACKUP, i.e. the FreeBSD servers. IOW, it looks as if we _are_ the upstream. expiration date:2011-12-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=miscportname=gtkfind ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On Sat, Dec 10, 2011 at 08:00:05AM -0800, per...@pluto.rain.com wrote: lini...@freebsd.org wrote: portname: misc/gtkfind description:The program to use to have to remember all the options to find(1) maintainer: po...@freebsd.org deprecated because: No more public distfiles, no more upstream Looking at the Makefile, it appears that this port does not claim to have a MASTER_SITES other than MASTER_SITE_BACKUP, i.e. the FreeBSD servers. IOW, it looks as if we _are_ the upstream. In other word all upstream died and as our mirror were the only place to find the distfiles $someone add it as a master_site. regards, Bapt pgpneaRhup29o.pgp Description: PGP signature
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/12/2011 16:00, per...@pluto.rain.com wrote: lini...@freebsd.org wrote: portname: misc/gtkfind description: The program to use to have to remember all the options to find(1) maintainer: po...@freebsd.org deprecated because: No more public distfiles, no more upstream Looking at the Makefile, it appears that this port does not claim to have a MASTER_SITES other than MASTER_SITE_BACKUP, i.e. the FreeBSD servers. IOW, it looks as if we _are_ the upstream. Hm. Are you interested in using it? I don't mind hosting it but it could do with a maintainer. Remember, we're only the upstream if someone is responsible for it. Also, its last update appears to be in 2003, and it's long dead Chris -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJO4zY3AAoJELCEktHh68rElUMH/iMtb1V0gHjetuFWHwg4VQmU ozv9rXICbaQhDLOCsg9OWt/qDmEIV2YIP54924cdqPQ9C3tDJac3raGjdlva03NG i0eElsnNl5SiS2yDzkH63LWJN6lxQu/TmuzQjO03n+VaMLfxyPA6hVX7fl+a8tYS no8RZbzMTCEGM5C4qxMXM3X/30JXsLccUG6epTurp7cpmZRXvTx5P/JwyI2uoIrV sXq+I1KRy127nOzMl3gSJCNDNAGX7a5ItXCBJJDW6BTxs1FyAvuH2lXG8CMYK+cC zzEGC3FAQlDCVSjEpNZiUMG6lgep3+GjDXtrsloAi8CZtzIW4EMRT8uZrShfk6U= =4hlg -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
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
Chris Rees cr...@freebsd.org wrote: portname: misc/gtkfind ... Looking at the Makefile, it appears that this port does not claim to have a MASTER_SITES other than MASTER_SITE_BACKUP, i.e. the FreeBSD servers. IOW, it looks as if we _are_ the upstream. Hm. Are you interested in using it? I don't mind hosting it but it could do with a maintainer. Remember, we're only the upstream if someone is responsible for it. I will maintain it if no one else comes forward. Also, its last update appears to be in 2003, and it's long dead s/long dead/in good enough shape to be useful/ :) ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/11/2011 04:07 AM, per...@pluto.rain.com wrote: Chris Rees cr...@freebsd.org wrote: portname: misc/gtkfind ... Looking at the Makefile, it appears that this port does not claim to have a MASTER_SITES other than MASTER_SITE_BACKUP, i.e. the FreeBSD servers. IOW, it looks as if we _are_ the upstream. Hm. Are you interested in using it? I don't mind hosting it but it could do with a maintainer. Remember, we're only the upstream if someone is responsible for it. I can also reliably host this so there is more than one upstream. Lemme know if you need me. :) I will maintain it if no one else comes forward. Also, its last update appears to be in 2003, and it's long dead s/long dead/in good enough shape to be useful/ :) Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7kXc0ACgkQGK3MsUbJZn4MegCfVC/9DQ9hb9o2jcllu9tCQnMb N1sAnAxjmYLiTfDDnG1mMyWP+LAXmq01 =U2LH -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
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
On 21 October 2011 07:31, lini...@freebsd.org wrote: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: databases/postgresql-plpython description: A module for using Python to write SQL functions maintainer: po...@freebsd.org deprecated because: (error in parsing Makefile) expiration date: 2011-04-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=postgresql-plpython How did this one get in this email? It was fixed two weeks ago... Chris ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
Chris Rees wrote on 22.10.2011 18:34: On 21 October 2011 07:31,lini...@freebsd.org wrote: portname: databases/postgresql-plpython description:A module for using Python to write SQL functions maintainer: po...@freebsd.org deprecated because: (error in parsing Makefile) expiration date:2011-04-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=postgresql-plpython How did this one get in this email? It was fixed two weeks ago... Chris Looks like that this portsmon working with some outdated ports tree, because it builds? (not sure what the name postgresql-plpython-7.4.30_1 actually mean) with postgresql 7.4, that's marked as deprecated in it's ports tree and doesn't exist in current ports tree. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
Bitrot on the original portsmon, due to be replaced by a new instance. Feel free to ignore. 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On 8 October 2011 10:53, per...@pluto.rain.com wrote: lini...@freebsd.org wrote: portname: net-mgmt/portmon deprecated because: No more public distfiles I was able to fetch it earlier today: $ ( cd /usr/ports/net-mgmt/portmon make fetch-recursive ) === Fetching all distfiles for portmon-2.0 and dependencies === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE = portmon-2.0.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch from http://voodoo.bawue.com/download/. portmon-2.0.tar.gz 100% of 104 kB 71 kBps Looks like a false negative when bapt tested it, I've undeprecated it since the stated reason is no longer true. Chris ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On Sat, Oct 08, 2011 at 10:27:12AM +0100, Chris Rees wrote: On 8 October 2011 10:53, per...@pluto.rain.com wrote: lini...@freebsd.org wrote: portname: net-mgmt/portmon deprecated because: No more public distfiles I was able to fetch it earlier today: $ ( cd /usr/ports/net-mgmt/portmon make fetch-recursive ) === Fetching all distfiles for portmon-2.0 and dependencies === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE = portmon-2.0.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch from http://voodoo.bawue.com/download/. portmon-2.0.tar.gz 100% of 104 kB 71 kBps Looks like a false negative when bapt tested it, I've undeprecated it since the stated reason is no longer true. This one in particular as been test for times with in three weeks to make sure (because I'm a user of it) upstream was down. I'm happy to see that it is up again. regards, Bapt pgpKmqQO0JevH.pgp Description: PGP signature
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
On 8 Oct 2011 23:29, Baptiste Daroussin b...@freebsd.org wrote: On Sat, Oct 08, 2011 at 10:27:12AM +0100, Chris Rees wrote: On 8 October 2011 10:53, per...@pluto.rain.com wrote: lini...@freebsd.org wrote: portname: net-mgmt/portmon deprecated because: No more public distfiles I was able to fetch it earlier today: $ ( cd /usr/ports/net-mgmt/portmon make fetch-recursive ) === Fetching all distfiles for portmon-2.0 and dependencies === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE = portmon-2.0.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch from http://voodoo.bawue.com/download/. portmon-2.0.tar.gz100% of 104 kB 71 kBps Looks like a false negative when bapt tested it, I've undeprecated it since the stated reason is no longer true. This one in particular as been test for times with in three weeks to make sure (because I'm a user of it) upstream was down. I'm happy to see that it is up again. I'll see about sticking the distfiles on my mirror too then, if upstream is unreliable. Chris ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
lini...@freebsd.org wrote: portname: net-mgmt/portmon deprecated because: No more public distfiles I was able to fetch it earlier today: $ ( cd /usr/ports/net-mgmt/portmon make fetch-recursive ) === Fetching all distfiles for portmon-2.0 and dependencies === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE = portmon-2.0.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch from http://voodoo.bawue.com/download/. portmon-2.0.tar.gz100% of 104 kB 71 kBps ___ 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: Re: FreeBSD unmaintained ports which are currently scheduled for deletion
On 24 August 2011 14:47, Mikhail T. mi+t...@aldan.algebra.com wrote:
On -10.01.-28163 14:59, Peter Jeremy wrote:
portname: sysutils/cpuburn
Actually, the mastersite has been discontinued by the ISP. It looks
like it's still available elsewhere but I can't find a replacement
mastersite.
So this one is correct???
It seems to be - which is unfortunate.
Can it be unbroken by using the Internet archive?
--- Makefile 2 Aug 2011 17:03:41 - 1.9
+++ Makefile 24 Aug 2011 13:46:21 -
@@ -9,5 +9,5 @@
PORTVERSION= 1.4
CATEGORIES= sysutils
-MASTER_SITES= http://pages.sbcglobal.net/redelm/
+MASTER_SITES=
http://web.archive.org/web/20070304200856/http://pages.sbcglobal.net/redelm/
DISTNAME= cpuburn_${PORTVERSION:S/./_/g}
EXTRACT_SUFX= _tar.gz
If so, quite a few other victims of this latest purging can be given a new
life.
Mi,
Matthias recently made reference on this subject, if you care to take a look:
http://lists.freebsd.org/pipermail/cvs-ports/2011-August/223266.html
Thanks for sorting cpuburn by the way.
Chris
--
Chris Rees | FreeBSD Developer
cr...@freebsd.org | http://people.freebsd.org/~crees
___
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: FreeBSD unmaintained ports which are currently scheduled for deletion
Am 24.08.2011 15:47, schrieb Mikhail T.:
On -10.01.-28163 14:59, Peter Jeremy wrote:
portname: sysutils/cpuburn
Actually, the mastersite has been discontinued by the ISP. It
looks
like it's still available elsewhere but I can't find a replacement
mastersite.
So this one is correct???
It seems to be - which is unfortunate.
Can it be unbroken by using the Internet archive?
--- Makefile2 Aug 2011 17:03:41 - 1.9
+++ Makefile24 Aug 2011 13:46:21 -
@@ -9,5 +9,5 @@
PORTVERSION= 1.4
CATEGORIES=sysutils
-MASTER_SITES= http://pages.sbcglobal.net/redelm/
+MASTER_SITES=
http://web.archive.org/web/20070304200856/http://pages.sbcglobal.net/redelm/
DISTNAME= cpuburn_${PORTVERSION:S/./_/g}
EXTRACT_SUFX= _tar.gz
If so, quite a few other victims of this latest purging can be given a
new life. Yours,
Wrong way. Either you become or find the/a new upstream maintainer or
it gets removed. We don't need to prolong life of otherwise dead
software. Again, FreeBSD ports are not a museum. For further
arguments, Chris has linked to an earlier message I'd sent.
If a port is really that important, someone can/will pick it up.
___
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: FreeBSD unmaintained ports which are currently scheduled for deletion
On 25.08.2011 08:48, Chris Rees wrote: On 24 August 2011 14:47, Mikhail T.mi+t...@aldan.algebra.com wrote: Can it be unbroken by using the Internet archive? ... If so, quite a few other victims of this latest purging can be given a new life. Matthias recently made reference on this subject, if you care to take a look: http://lists.freebsd.org/pipermail/cvs-ports/2011-August/223266.html Thanks for the pointer. I disagree with Matthias very strongly on this -- and made my disagreement known in the past. It remains my deeply-held opinion, that only those ports, which fail to build, ought to be removed from the tree. I'm happy to learn, amdmi3@ is of similar persuasion. Matthias warns, that something we mirrored years ago could be missing crucial patches -- but that's inevitable even with actively-maintained ports, and FreeBSD, wisely, makes no promises of software quality or security. Matthias' proposal to remove unmaintained ports makes it impossible to find a PERFECT program, port it and wash one's hands away from it. Sooner or later somebody will come to claim, your software is too old and thus /could/ contain security holes, and therefor must be removed. Because we have too many ports or something. Perhaps more importantly, Matthias' argument is different from the problem at hand -- he seems to dislike old distfiles, but the current campaign targets not the old pieces, but those, for which the master-sites' have disappeared. For example, the sources of audio/adpcm date to 1994, but the port only got into trouble, when the FTP-site hosting it disappeared from the Internet... Likewise, sysutils/cpuburn's sources are from 2003, but the port arose no questions, until ATT discontinued subscribers' web-spaces (where the author was hosting the distfile) two months ago... Do we really want to allow ISPs to affect the contents of our ports collection in this manner? If we were really ruled by consensus, these unfortunate ports would've stayed because, evidently, there is no consensus, as Dmitry and Matthias discuss at the very beginning of the e-mail you linked to... It appears, that the rule currently being applied, is: remove, if there are no master-sites other than FreeBSD's mirrors (the deprecation messages state something else, but this is the real meaning). Though this rule is refreshingly objective, I still don't like it -- FreeBSD claimed there is a port for it long before the catchy there is an app for it, and this remains a major selling point for the OS. But, if the rule's application is unstoppable, then I'd save most of the victims of the current purge by switching them to archive.org. It can even be done automatically by a clever script... Yours, -mi ___ 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: Re: FreeBSD unmaintained ports which are currently scheduled for deletion
On -10.01.-28163 14:59, Peter Jeremy wrote:
portname: sysutils/cpuburn
Actually, the mastersite has been discontinued by the ISP. It looks
like it's still available elsewhere but I can't find a replacement
mastersite.
So this one is correct???
It seems to be - which is unfortunate.
Can it be unbroken by using the Internet archive?
--- Makefile2 Aug 2011 17:03:41 - 1.9
+++ Makefile24 Aug 2011 13:46:21 -
@@ -9,5 +9,5 @@
PORTVERSION= 1.4
CATEGORIES=sysutils
-MASTER_SITES= http://pages.sbcglobal.net/redelm/
+MASTER_SITES=
http://web.archive.org/web/20070304200856/http://pages.sbcglobal.net/redelm/
DISTNAME= cpuburn_${PORTVERSION:S/./_/g}
EXTRACT_SUFX= _tar.gz
If so, quite a few other victims of this latest purging can be given a
new life. Yours,
-mi
___
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: FreeBSD unmaintained ports which are currently scheduled for deletion
On 22 Aug 2011 22:49, Peter Jeremy peterjer...@acm.org wrote: On 2011-Aug-21 08:30:13 +0200, lini...@freebsd.org wrote: portname: cad/tkgate description:A Tcl/Tk based digital circuit editor and simulator maintainer: po...@freebsd.org deprecated because: No more public distfiles expiration date:2011-09-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=tkgate I have no problem fetching this port from the mastersite. I'll take a look. portname: sysutils/cpuburn description:CPU/memory stress testing utilities maintainer: po...@freebsd.org deprecated because: No more public distfiles expiration date:2011-09-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=cpuburn Actually, the mastersite has been discontinued by the ISP. It looks like it's still available elsewhere but I can't find a replacement mastersite. So this one is correct??? Chris ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On 23 August 2011 07:45, Chris Rees utis...@gmail.com wrote: On 22 Aug 2011 22:49, Peter Jeremy peterjer...@acm.org wrote: On 2011-Aug-21 08:30:13 +0200, lini...@freebsd.org wrote: portname: cad/tkgate description: A Tcl/Tk based digital circuit editor and simulator maintainer: po...@freebsd.org deprecated because: No more public distfiles expiration date: 2011-09-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=tkgate I have no problem fetching this port from the mastersite. I'll take a look. You're correct, I've undeprecated this one. Chris -- Chris Rees | FreeBSD Developer cr...@freebsd.org | http://people.freebsd.org/~crees ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On 2011-Aug-23 07:45:04 +0100, Chris Rees utis...@gmail.com wrote: On 22 Aug 2011 22:49, Peter Jeremy peterjer...@acm.org wrote: On 2011-Aug-21 08:30:13 +0200, lini...@freebsd.org wrote: portname: cad/tkgate I have no problem fetching this port from the mastersite. I'll take a look. Thanks for undeprecating this. portname: sysutils/cpuburn Actually, the mastersite has been discontinued by the ISP. It looks like it's still available elsewhere but I can't find a replacement mastersite. So this one is correct??? It seems to be - which is unfortunate. -- Peter Jeremy pgpF7dXMgyo6I.pgp Description: PGP signature
Re: audio/adpcm (Re: FreeBSD unmaintained ports which are currently scheduled for deletion)
On 22 August 2011 03:24, Mikhail T. mi+t...@aldan.algebra.com wrote: On -10.01.-28163 14:59, lini...@freebsd.org wrote: portname: audio/adpcm description: An Intel/DVI IMA ADPCM codec library maintainer:po...@freebsd.org deprecated because: No more public distfiles expiration date: 2011-09-01 build errors: none. overview:http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=adpcm At least in this particular case, I don't think, the removal is warranted. The public distfiles disappeared not because of a deliberate action by the developer or copyright-holder, but simply because the entire ftp.cwi.nl is now gone. Sites continue to host the file -- we should allow CWI.net to sort things out with their FTP-server (or, perhaps, they intend to offer the same code over HTTP later). Could you add those extra sites to MASTER_SITES then please? Chris ___ 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: audio/adpcm (Re: FreeBSD unmaintained ports which are currently scheduled for deletion)
On 22.08.2011 04:46, Chris Rees wrote: On 22 August 2011 03:24, Mikhail T.mi+t...@aldan.algebra.com wrote: On -10.01.-28163 14:59, lini...@freebsd.org wrote: portname: audio/adpcm description:An Intel/DVI IMA ADPCM codec library maintainer:po...@freebsd.org deprecated because: No more public distfiles expiration date:2011-09-01 build errors: none. overview:http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=adpcm At least in this particular case, I don't think, the removal is warranted. The public distfiles disappeared not because of a deliberate action by the developer or copyright-holder, but simply because the entire ftp.cwi.nl is now gone. Sites continue to host the file -- we should allow CWI.net to sort things out with their FTP-server (or, perhaps, they intend to offer the same code over HTTP later). Could you add those extra sites to MASTER_SITES then please? None of them are official -- and various web-pages continue to refer to ftp.cwi.nl as the source. Since FreeBSD mirrors already provide unofficial mirrors, is there a point in adding those at this time? -mi ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On 2011-Aug-21 08:30:13 +0200, lini...@freebsd.org wrote: portname: cad/tkgate description:A Tcl/Tk based digital circuit editor and simulator maintainer: po...@freebsd.org deprecated because: No more public distfiles expiration date:2011-09-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=tkgate I have no problem fetching this port from the mastersite. portname: sysutils/cpuburn description:CPU/memory stress testing utilities maintainer: po...@freebsd.org deprecated because: No more public distfiles expiration date:2011-09-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=cpuburn Actually, the mastersite has been discontinued by the ISP. It looks like it's still available elsewhere but I can't find a replacement mastersite. -- Peter Jeremy pgp92rokiqI78.pgp Description: PGP signature
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
I notice in the list the port math/pari which is not some obscure abandonware, but one of the most proeminent free computer algebra software. So i look at the pari web page and then: niobe% fetch http://pari.math.u-bordeaux.fr/pub/pari/unix/pari-2.5.0.tar.gz pari-2.5.0.tar.gz 100% of 2650 kB 6412 kBps . niobe% ./Configure Configuring pari-2.5.0 (STABLE) Ok. Type make install when you are ready Bye ! niobe% gmake gp Making gp in Ofreebsd-i386 niobe% cd Ofreebsd-i386 niobe% gp-dyn GP/PARI CALCULATOR Version 2.5.0 (released) i386 running freebsd (ix86/GMP-5.0.1 kernel) 32-bit version compiled: Aug 21 2011, gcc-4.2.1 20070719 [FreeBSD] (readline v6.1 enabled, extended help enabled) Copyright (C) 2000-2011 The PARI Group PARI/GP is free software, covered by the GNU General Public License, and comes WITHOUT ANY WARRANTY WHATSOEVER. Type ? for help, \q to quit. Type ?12 for how to get moral (and possibly technical) support. parisize = 400, primelimit = 500509 ? 5*6 %1 = 30 ? In other words everything works completely out of the box, without any intervention. After that people will say that the freebsd ports are the best thing since sliced bread! -- Michel TALON ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On 21 August 2011 10:05, Michel Talon ta...@lpthe.jussieu.fr wrote: I notice in the list the port math/pari which is not some obscure abandonware, but one of the most proeminent free computer algebra software. So i look at the pari web page and then: niobe% fetch http://pari.math.u-bordeaux.fr/pub/pari/unix/pari-2.5.0.tar.gz pari-2.5.0.tar.gz 100% of 2650 kB 6412 kBps . niobe% ./Configure Configuring pari-2.5.0 (STABLE) Ok. Type make install when you are ready Bye ! niobe% gmake gp Making gp in Ofreebsd-i386 niobe% cd Ofreebsd-i386 niobe% gp-dyn GP/PARI CALCULATOR Version 2.5.0 (released) i386 running freebsd (ix86/GMP-5.0.1 kernel) 32-bit version compiled: Aug 21 2011, gcc-4.2.1 20070719 [FreeBSD] (readline v6.1 enabled, extended help enabled) Copyright (C) 2000-2011 The PARI Group PARI/GP is free software, covered by the GNU General Public License, and comes WITHOUT ANY WARRANTY WHATSOEVER. Type ? for help, \q to quit. Type ?12 for how to get moral (and possibly technical) support. parisize = 400, primelimit = 500509 ? 5*6 %1 = 30 ? In other words everything works completely out of the box, without any intervention. Looks like the outdated version we have in ports isn't kept there any more. Would you like to be the port's new maintainer? We can extend the expiration date if you work on getting it to work again. After that people will say that the freebsd ports are the best thing since sliced bread! Not sure I understand what you're saying here. Chris ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
Hi! On 21 August 2011 10:05, Michel Talon ta...@lpthe.jussieu.fr wrote: I notice in the list the port math/pari which is not some obscure abandonware, but one of the most proeminent free computer algebra software. [...] In other words everything works completely out of the box, without any intervention. Looks like the outdated version we have in ports isn't kept there any more. Would you like to be the port's new maintainer? I'll have a look at it. -- p...@opsec.eu+49 171 3101372 9 years to go ! ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
On 21 August 2011 15:34, Kurt Jaeger li...@opsec.eu wrote: Hi! On 21 August 2011 10:05, Michel Talon ta...@lpthe.jussieu.fr wrote: I notice in the list the port math/pari which is not some obscure abandonware, but one of the most proeminent free computer algebra software. [...] In other words everything works completely out of the box, without any intervention. Looks like the outdated version we have in ports isn't kept there any more. Would you like to be the port's new maintainer? I'll have a look at it. Can I take that as 'I'll have maintainership please!'? ;) Chris ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
Kurt Jaeger wrote:
Looks like the outdated version we have in ports isn't kept there any
more. Would you like to be the port's new maintainer?
I'll have a look at it.
I have played a little with the FreeBSD port for pari:
One needs to modify very little the Makefile:
CONFIGURE_ARGS= --prefix=${PREFIX} --share-prefix=${PREFIX}/share\
--mandir=${PREFIX}/man/man1 --with-gmp=${LOCALBASE}
This is so that the man pages go to the correct position.
MAJOR_VERSION= 2
MINOR_VERSION= 5
REV_VERSION=0
I think all the emacs stuff has become useless.
The good distinfo is
niobe# cat distinfo
MD5 (pari-2.5.0.tar.gz) = 6077c6db56fdd32e39a06a9bf320e1f7
SHA256 (pari-2.5.0.tar.gz) =
5dc923b001ca0f8664facfafcd91946be63faf8f0e1df4b11bfac80f89ec37a2
MD5 (pari-2.5.0.tar.gz) = 0b595a1345679ff482785a686c863e9f
SIZE (pari-2.5.0.tar.gz) = 2714449
The patch files in files/ don't apply cleanly and are useless, except
patch-config-TOP_Make.SH
which removes compiling the doc. This may be fine because the doc is on
the web site, and requires TeX for compiling. Anyways the doc
compile needs make - gmake (and then works) but i don't know how to
pass that to the system.
The make install installs less files than what is in pkg-plist.
In /usr/local/bin:
gp gp-2.5 gphelp tex2mail
In /usr/local/include/pari
genpari.h pari.h paricfg.h paridecl.h parigen.h parinf.h
paripriv.h parisys.h
mpinl.hparicast.h paricom.h parierr.h pariinl.h pariold.h
paristio.h paritune.h
In /usr/local/share/pari:
niobe# ls -R /usr/local/share/pari
PARI doc examples misc pari.desc
/usr/local/share/pari/PARI:
822.pm
/usr/local/share/pari/doc:
Makefile appd.tex parimacro.tex refcard.pstutorial.dvi
users.tex usersch3.tex
appa.tex libpari.dvi pdfmacs.tex refcard.tex tutorial.tex
usersch1.tex usersch4.tex
appb.tex paricfg.tex refcard.dvi translations users.dvi
usersch2.tex usersch5.tex
/usr/local/share/pari/examples:
EXPLAIN Makefilecl.gp contfrac.gp lucas.gpsqufof.gp
Inputrc bench.gpclassno.gp extgcd.crho.gp taylor.gp
/usr/local/share/pari/misc:
READMEcolor.dft gpalias gpfloggprc.dft pari.xpm xgp
niobe# ls -R /usr/local/share/pari
PARI doc examples misc pari.desc
/usr/local/share/pari/PARI:
822.pm
/usr/local/share/pari/doc:
Makefile appd.tex parimacro.tex refcard.pstutorial.dvi
users.tex usersch3.tex
appa.tex libpari.dvi pdfmacs.tex refcard.tex tutorial.tex
usersch1.tex usersch4.tex
appb.tex paricfg.tex refcard.dvi translations users.dvi
usersch2.tex usersch5.tex
/usr/local/share/pari/examples:
EXPLAIN Makefilecl.gp contfrac.gp lucas.gpsqufof.gp
Inputrc bench.gpclassno.gp extgcd.crho.gp taylor.gp
/usr/local/share/pari/misc:
READMEcolor.dft gpalias gpfloggprc.dft pari.xpm xgp
And finally the man pages in /usr/local/man/man1
gp-2.5.1 gp.1 gphelp.1 pari.1 tex2mail.1
and the compressed versions.
Good luck
--
Michel TALON
___
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
audio/adpcm (Re: FreeBSD unmaintained ports which are currently scheduled for deletion)
On -10.01.-28163 14:59, lini...@freebsd.org wrote: portname: audio/adpcm description:An Intel/DVI IMA ADPCM codec library maintainer:po...@freebsd.org deprecated because: No more public distfiles expiration date:2011-09-01 build errors: none. overview:http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=adpcm At least in this particular case, I don't think, the removal is warranted. The public distfiles disappeared not because of a deliberate action by the developer or copyright-holder, but simply because the entire ftp.cwi.nl is now gone. Sites continue to host the file -- we should allow CWI.net to sort things out with their FTP-server (or, perhaps, they intend to offer the same code over HTTP later). -mi ___ 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: FreeBSD unmaintained ports which are currently scheduled for deletion
Hi! 07.02.2010 10:30, lini...@freebsd.org пишет: The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. Can please anybody also pick ports/138639 for removal? Seems like maintainer (kuriyama) isn't available in almost five months. Thanks. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/138639 ___ 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
The state of Ada (Re: FreeBSD unmaintained ports which are currently scheduled for deletion)
01/-10/37 14:59, lini...@freebsd.org wrote: portname: devel/adabindx description:An Ada-binding to the X Window System and *tif maintainer:po...@freebsd.org status: BROKEN deprecated because: has been broken for 3 months expiration date:2010-01-08 build errors: none. overview:http://portsmon.FreeBSD.org/portoverview.py?category=develportname=adabindx [...] It looks like a noticeable share of the ports listed have one thing in common -- they depend on Ada. Various gnat-ports would not even build on anything but i386... Is Ada-support really in such a bad shape by the GNU-project, or is it just a FreeBSD problem? -mi ___ 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: The state of Ada (Re: FreeBSD unmaintained ports which are currently scheduled for deletion)
It looks like a noticeable share of the ports listed have one thing in common -- they depend on Ada. Various gnat-ports would not even build on anything but i386... Is Ada-support really in such a bad shape by the GNU-project, or is it just a FreeBSD problem? 'Lo. Current situtation is this: I've spent a great deal of time getting GCC 4.4 ported to FreeBSD on i386 and x86_64. I currently do regular builds of GCC from SVN on 7/8 i386/x86_64, the logs and test results of which are available here: http://gcc.coreland.ath.cx/ No binaries, sorry. I'm limited by bandwidth and disk space. As you can see, GNAT works pretty well on FreeBSD and passes most of ACATS. I created the lang/gnat-gcc44 port a couple of months ago and have worked to ensure that it works on 7/8 i386/x86_64. Unfortunately, there won't be support for other platforms until somebody else decides to do the cross compilation and produce bootstrap binaries (it's not particularly difficult, just time consuming). http://coreland.ath.cx/code/gnatport I've recently written a bsd.gnat.mk file which I hope will soon be committed to the ports system. This will allow all Ada ports to state 'USE_GNAT=yes' and will remove the requirement to have up to four (!) different Ada compilers installed in order to use all existing ports (assuming that they build and work). This also allows one to, for example, set 'USE_GNAT=gnat-gpl' in /etc/make.conf and use the GNAT GPL compiler for all ports. This'll currently only work on i386 as the current version of the compiler seems to lack x86_64 support (maybe the 2010 version will be better). I'll work on converting all existing ports to this system. I also have a large number of my own projects to submit (bindings for various libraries such as SDL, OpenGL, OpenAL and pure Ada libraries). In short, the current state of Ada on FreeBSD is poor but should shortly improve exponentially. M ___ 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: The state of Ada (Re: FreeBSD unmaintained ports which are currently scheduled for deletion)
- Original Message From: freebsd-po...@coreland.ath.cx freebsd-po...@coreland.ath.cx To: John Merryweather Cooper john_m_coo...@yahoo.com Cc: Mikhail T. mi+t...@aldan.algebra.com; ka...@lovetemple.net; eisc...@vigrid.com; freebsd-ports@freebsd.org Sent: Fri, January 8, 2010 10:56:38 AM Subject: Re: The state of Ada (Re: FreeBSD unmaintained ports which are currently scheduled for deletion) It looks like a noticeable share of the ports listed have one thing in common -- they depend on Ada. Various gnat-ports would not even build on anything but i386... Is Ada-support really in such a bad shape by the GNU-project, or is it just a FreeBSD problem? 'Lo. Current situtation is this: I've spent a great deal of time getting GCC 4.4 ported to FreeBSD on i386 and x86_64. I currently do regular builds of GCC from SVN on 7/8 i386/x86_64, the logs and test results of which are available here: http://gcc.coreland.ath.cx/ No binaries, sorry. I'm limited by bandwidth and disk space. As you can see, GNAT works pretty well on FreeBSD and passes most of ACATS. I created the lang/gnat-gcc44 port a couple of months ago and have worked to ensure that it works on 7/8 i386/x86_64. Unfortunately, there won't be support for other platforms until somebody else decides to do the cross compilation and produce bootstrap binaries (it's not particularly difficult, just time consuming). http://coreland.ath.cx/code/gnatport I've recently written a bsd.gnat.mk file which I hope will soon be committed to the ports system. This will allow all Ada ports to state 'USE_GNAT=yes' and will remove the requirement to have up to four (!) different Ada compilers installed in order to use all existing ports (assuming that they build and work). This also allows one to, for example, set 'USE_GNAT=gnat-gpl' in /etc/make.conf and use the GNAT GPL compiler for all ports. This'll currently only work on i386 as the current version of the compiler seems to lack x86_64 support (maybe the 2010 version will be better). I'll work on converting all existing ports to this system. I also have a large number of my own projects to submit (bindings for various libraries such as SDL, OpenGL, OpenAL and pure Ada libraries). In short, the current state of Ada on FreeBSD is poor but should shortly improve exponentially. M USE_GNAT would be a massive improvement. It would allow the dependent ports to potentially strip out the logic necessary to determine which compiler is try to build them (and if it will work). jmc ___ 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: The state of Ada (Re: FreeBSD unmaintained ports which are currently scheduled for deletion)
On Fri, 8 Jan 2010, John Merryweather Cooper wrote: Well, the compiler needs to be upgraded to the latest version. Linux gets a compiler out of the box, but we have to bend one to shape. Most things stay the same, but there are always subtle differences. I'd be happy to help do this (as I'm currently unemployed), but I'm also going through a divorce. You can contact me more directly at j.m.cooper at borgsdemons.com. All the ports that I saw that were broken, were broken *because* the compiler (lang/gnat) was updated. Those ports seemed to be vastly out of date and didn't build with the latest GPL gnat from ACT. -- DE ___ 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: The state of Ada (Re: FreeBSD unmaintained ports which are currently scheduled for deletion)
On Fri, Jan 08, 2010 at 06:56:38PM +, freebsd-po...@coreland.ath.cx wrote: I created the lang/gnat-gcc44 port a couple of months ago and have worked to ensure that it works on 7/8 i386/x86_64. Unfortunately, there won't be support for other platforms until somebody else decides to do the cross compilation and produce bootstrap binaries (it's not particularly difficult, just time consuming). IMHO it's not much worth worrying about the state of Ada on our tier-2 architectures. I just don't see there being any userbase for that. sparc64 has lots of other ports that need attention more than Ada, and the other archs ... just need lots of attention. (Yes, I do know of people using powerpc and ia64 even as desktops, but they're a small, brave, minority.) fwiw, I'm glad you've taken up the banner of fixing this stuff. 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: The state of Ada (Re: FreeBSD unmaintained ports which are currently scheduled for deletion)
- Original Message From: Daniel Eischen deisc...@freebsd.org To: John Merryweather Cooper john_m_coo...@yahoo.com Cc: Mikhail T. mi+t...@aldan.algebra.com; po...@freebsd.org; ka...@lovetemple.net Sent: Fri, January 8, 2010 11:59:05 AM Subject: Re: The state of Ada (Re: FreeBSD unmaintained ports which are currently scheduled for deletion) On Fri, 8 Jan 2010, John Merryweather Cooper wrote: Well, the compiler needs to be upgraded to the latest version. Linux gets a compiler out of the box, but we have to bend one to shape. Most things stay the same, but there are always subtle differences. I'd be happy to help do this (as I'm currently unemployed), but I'm also going through a divorce. You can contact me more directly at j.m.cooper at borgsdemons.com. All the ports that I saw that were broken, were broken *because* the compiler (lang/gnat) was updated. Those ports seemed to be vastly out of date and didn't build with the latest GPL gnat from ACT. -- DE That's largely true--I need to take a look and get things going again. But there's still a parallel compiler path that creates problems. Most ports (before being put into the tree) expect to be built with one of the pre-built compilers from ACT. So name and location problems exist. I'm sorry I've been off the wheel but I sold my soul to Microsoft (at least for awhile) . . . jmc ___ 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: The state of Ada (Re: FreeBSD unmaintained ports which are currently scheduled for deletion)
01/08/10 14:59, Daniel Eischen написав(ла): All the ports that I saw that were broken, were broken *because* the compiler (lang/gnat) was updated. Those ports seemed to be vastly out of date and didn't build with the latest GPL gnat from ACT. Well, I tried to fix one, but my system is amd64, so I couldn't even begin... Good to see, somebody is working on it, though... -mi ___ 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
