FreeBSD ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: accessibility/yasr broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=yasr portname: audio/gdam broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gdam portname: audio/mp3towav-bundle broken because: fails to build build errors: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.8.20130510010703.pointyhat/mp3towav-bundle-0.4.1_2.log (May 13 14:33:07 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=mp3towav-bundle portname: benchmarks/polygraph31 broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarksportname=polygraph31 portname: biology/dotter broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=dotter portname: cad/salome-geom broken because: fails to build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=salome-geom portname: cad/salome-med broken because: Fails to fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=salome-med portname: cad/salome-yacs broken because: fails to build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=salome-yacs portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=big5con portname: chinese/bitchx broken because: patch reject build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=bitchx portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=hztty portname: comms/hso-kmod broken because: does not build with USB2, please try comms/uhso-kmod instead build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=hso-kmod portname: comms/ib-kmod broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=ib-kmod portname: comms/uticom broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=uticom portname: converters/p5-Unicode-Lite broken because: Overwrites bin/map from converters/p5-Unicode-Map build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=convertersportname=p5-Unicode-Lite portname: converters/pdf2djvu broken because: does not build build errors:
FreeBSD unmaintained ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/mp3towav-bundle broken because: fails to build build errors: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.8.20130510010703.pointyhat/mp3towav-bundle-0.4.1_2.log (May 13 14:33:07 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=mp3towav-bundle portname: biology/dotter broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=dotter portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=big5con portname: chinese/bitchx broken because: patch reject build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=bitchx portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=hztty portname: converters/p5-Unicode-Lite broken because: Overwrites bin/map from converters/p5-Unicode-Map build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=convertersportname=p5-Unicode-Lite portname: databases/msql broken because: Broken on FreeBSD 9+ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=msql portname: deskutils/libopensync-plugin-python-devel broken because: fails to build with recent libopensync build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=libopensync-plugin-python-devel portname: deskutils/libopensync-plugin-vformat-devel broken because: fails to build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=libopensync-plugin-vformat-devel portname: deskutils/simpleagenda broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=simpleagenda portname: devel/dsss broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=dsss portname: devel/libYGP broken because: Does not build with recent boost build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=libYGP portname: devel/lua50-dfui broken because: Does not build build errors: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.10.20130313090402.pointyhat/lua50-dfui-0.1.20050901.log (Mar 14 00:26:27 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=lua50-dfui portname: devel/mico broken because: fails to build build errors: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9.20130611080829.pointyhat/mico-2.3.12_4.log (May 9 08:10:57 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=mico portname:
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 +-+ www/p5-CGI-Application-Server | 0.062 | 0.063 +-+ www/xpi-pentadactyl | 20130407| 20130707 +-+ 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 If wish to stop receiving portscout reminders, please contact portsc...@freebsd.org 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
make config: doesn't work - reports === Options unchanged : no options menu popping up
On boxes running recent /usr/ports and recent soutces( FreeBSD 10.0-CURRENT #0 r252885: Sat Jul 6 16:09:09 CEST 2013) I'm unable to configure some ports, for instance www/firefox: /usr/ports/www/firefox # make config === Options unchanged Even performing make rmconfig and repeating above procedure doesn't change anything. I can not change options anymore! Please CC me, I'm not subsrcribing the list. Thanks, Oliver signature.asc Description: PGP signature
Re: Global destructor order problems
On Thu, 27 Jun 2013 17:04:28 +0300 Konstantin Belousov kostik...@gmail.com wrote: On Thu, Jun 27, 2013 at 03:41:48PM +0200, Dimitry Andric wrote: On 2013-06-27 01:56, Michael Gmelin wrote: On Thu, 27 Jun 2013 00:28:33 +0300 Konstantin Belousov kostik...@gmail.com wrote: On Wed, Jun 26, 2013 at 11:17:41PM +0200, Michael Gmelin wrote: Are you both on the same architecture? I tested both on amd64 and i386. For i386, it was -m32 for clang, and native 32bit gcc 4.8.1, stock build from the tarball. For completeness sake I tested once more using various compilers including gcc 4.8.1 on 10-CURRENT amd64 (see below). I have now tested the lang/gcc44, 46, 47, 48 and 49 ports, on both i386 and amd64. All result in the incorrect destructor order. My build of gcc is stock, not from the ports. Another detail, I built the compiler on stable/9, but use it on both stable and current. I am very curious what makes the my build to generate the code which uses PLT instead of direct reference, but have no time to investigate. I think that we could revert the termination calls to the functions from the dso being unloaded, but this is quite unfortunate, since it will restore the endless series of 'segfault at the process termination' reports. So now what? -- Michael Gmelin ___ 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: make config: doesn't work - reports === Options unchanged : no options menu popping up
O. Hartmann wrote on 07.07.2013 12:25: On boxes running recent /usr/ports and recent soutces( FreeBSD 10.0-CURRENT #0 r252885: Sat Jul 6 16:09:09 CEST 2013) I'm unable to configure some ports, for instance www/firefox: /usr/ports/www/firefox # make config === Options unchanged Even performing make rmconfig and repeating above procedure doesn't change anything. I can not change options anymore! Please CC me, I'm not subsrcribing the list. [...] I've seen this kind of behaviour with dialog4ports in various situations, but since dialog4ports-0.1.1 or so, I've never encountered this again. Here's a few shots in the dark: - Maybe you're running an outdated version of dialog4ports. Remove dialog4ports, then make config in www/firefox again. This will trigger installation of whatever the most recent version of dialog4ports is in your ports tree. - Check your environment. Unset DIALOG4PORTS or DIALOG, if they're set, then try make config again. MfG CoCo ___ 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: make config: doesn't work - reports === Options unchanged : no options menu popping up
On Sun, 07 Jul 2013 14:36:37 +0200 Marco Steinbach c...@executive-computing.de wrote: O. Hartmann wrote on 07.07.2013 12:25: On boxes running recent /usr/ports and recent soutces( FreeBSD 10.0-CURRENT #0 r252885: Sat Jul 6 16:09:09 CEST 2013) I'm unable to configure some ports, for instance www/firefox: /usr/ports/www/firefox # make config === Options unchanged Even performing make rmconfig and repeating above procedure doesn't change anything. I can not change options anymore! Please CC me, I'm not subsrcribing the list. [...] I've seen this kind of behaviour with dialog4ports in various situations, but since dialog4ports-0.1.1 or so, I've never encountered this again. Here's a few shots in the dark: - Maybe you're running an outdated version of dialog4ports. Remove dialog4ports, then make config in www/firefox again. This will trigger installation of whatever the most recent version of dialog4ports is in your ports tree. - Check your environment. Unset DIALOG4PORTS or DIALOG, if they're set, then try make config again. MfG CoCo Thanks for the hint. rebuilding dialog4ports made the problem go away. It is strange. I usually have up to date ports, even dialog4ports. But since this happens on CURRENT (I didn't see this on 9.1-STBALE yet) I guess it is due to CURRENT is a moving target ... Regards, Oliver signature.asc Description: PGP signature
A note re: updating devel/apr (UPDATING entry 20130706)
Empirically, I have found that the given instructions (for portmaster) work well -- if Apache's httpd is not running during the portmaster -r apr run. If, however, Apache's httpd is running, I see such things as: ... portmaster -d -r apr === Working on: apr-1.4.6.1.4.1_3 === Gathering distinfo list for installed ports ... === Returning to list of ports depending on apr-1.4.6.1.4.1_3 === The update for serf-1.2.1 is already done === Checking done for ports that depend on apr-1.4.6.1.4.1_3 === Total ports: 1 (7) 0;portmaster: Total ports: 1 (7)^G === The following actions will be taken if you choose to proceed: Upgrade apr-1.4.6.1.4.1_3 to apr-1.4.8.1.5.2 Upgrade subversion-1.8.0_1 to subversion-1.8.0_2 Upgrade apache22-2.2.24 to apache22-2.2.24_1 Upgrade serf-1.2.1 to serf-1.2.1_1 Upgrade py27-subversion-1.8.0_1 to py27-subversion-1.8.0_2 Re-install viewvc-1.1.20 Re-install porttools-0.99_8 Upgrade sudo-1.8.7 to sudo-1.8.7_1 === Proceed? y/n [y] === Starting build for multiple ports === === apr-1.4.6.1.4.1_3 1/1 ... reating a backup package for old version apr-1.4.6.1.4.1_3 pkg_delete: package 'apr-1.4.6.1.4.1_3' is required by these other packages and may not be deinstalled (but I'll delete it anyway): apache22-2.2.24 viewvc-1.1.20 serf-1.2.1 subversion-1.8.0_1 py27-subversion-1.8.0_1 porttools-0.99_8 === Starting check for runtime dependencies === Gathering dependency list for devel/apr1 from ports === Dependency check complete for devel/apr1 === apr-1.4.6.1.4.1_3 1/1 0;portmaster: apr-1.4.6.1.4.1_3 1/1^G === Installing for apr-1.4.8.1.5.2 ... /usr/bin/install -m 644 aprutil.exp /usr/local/lib /usr/bin/install -m 755 apu-config.out /usr/local/bin/apu-1-config === Running ldconfig /sbin/ldconfig -m /usr/local/lib === Registering installation for apr-1.4.8.1.5.2 === SECURITY REPORT: ... === Updating dependency entry for apr-1.4.8.1.5.2 in each dependent port === Upgrade of apr-1.4.6.1.4.1_3 to apr-1.4.8.1.5.2 succeeded === Updating ports that depend on apr-1.4.6.1.4.1_3 0;portmaster: Updating ports that depend on apr-1.4.6.1.4.1_3 ^G === Launching child to reinstall subversion-1.8.0_1 === Updating dependent ports subversion-1.8.0_1 (1/7) 0;portmaster: Updating dependent ports subversion-1.8.0_1 (1/7)^G === Currently installed version: subversion-1.8.0_1 === Port directory: /usr/ports/devel/subversion === Starting check for build dependencies === Gathering dependency list for devel/subversion from ports Shared object libaprutil-1.so.4 not found, required by httpd Shared object libaprutil-1.so.4 not found, required by httpd apxs:Error: Sorry, no shared object support for Apache. apxs:Error: available under your platform. Make sure. apxs:Error: the Apache module mod_so is compiled into. apxs:Error: your server binary `/usr/local/sbin/httpd'.. /usr/ports/Mk/bsd.apache.mk, line 284: warning: /usr/local/sbin/apxs -q MPM_NAME returned non-zero status pkg_info: option requires an argument -- O usage: pkg_info [-bcdDEfgGiIjkKLmopPqQrRsvVxX] [-e package] [-l prefix] [-t template] -a | pkg-name ... pkg_info [-qQ] -W filename pkg_info [-qQ] -O origin pkg_info === Launching child to reinstall === Updating dependent ports (2/7) 0;portmaster: Updating dependent ports (2/7)^G === No /usr/ports/usr/ports exists, and no information === about usr/ports can be found in /usr/ports/MOVED === No valid installed port, or port directory given === Try portmaster --help === Update for failed === Aborting update === Update for subversion-1.8.0_1 failed === Aborting update === Killing background jobs Terminated === The following actions were performed: Upgrade of apr-1.4.6.1.4.1_3 to apr-1.4.8.1.5.2 === You can restart from the point of failure with this command line: portmaster flags devel/subversion www/apache22 www/serf devel/py-subversion devel/viewvc ports-mgmt/porttools security/sudo === Exiting [end of typescript excerpt] I finally managed to get through the update -- and updates on other machines has been relatively painless -- but I'm sending this note out to try to help others avoid the above. Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgptCjD7D0PnX.pgp Description: PGP signature
help with making a port
I am attempting to put together a port for a new program and I am getting a very odd error message (i.e. it says the port conflicts with itself!?!?!?!): pkg-static: foo-0.1 conflicts with foo-0.1 (installs files into the same place). Problematic file: /usr/local/share/foo/foo.jar What causes this and how do I fix the make file? ___ 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
Fwd: help with making a port
-- Forwarded message -- From: Aryeh Friedman aryeh.fried...@gmail.com Date: Sun, Jul 7, 2013 at 1:12 PM Subject: help with making a port To: FreeBSD Ports ML freebsd-ports@freebsd.org I am attempting to put together a port for a new program and I am getting a very odd error message (i.e. it says the port conflicts with itself!?!?!?!): pkg-static: foo-0.1 conflicts with foo-0.1 (installs files into the same place). Problematic file: /usr/local/share/foo/foo.jar What causes this and how do I fix the make file? ___ 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
Fwd: help with making a port
GMail is being weird this is a 3rd try at reposting -- Forwarded message -- From: Aryeh Friedman aryeh.fried...@gmail.com Date: Sun, Jul 7, 2013 at 1:12 PM Subject: help with making a port To: FreeBSD Ports ML freebsd-ports@freebsd.org I am attempting to put together a port for a new program and I am getting a very odd error message (i.e. it says the port conflicts with itself!?!?!?!): pkg-static: foo-0.1 conflicts with foo-0.1 (installs files into the same place). Problematic file: /usr/local/share/foo/foo.jar What causes this and how do I fix the make file? ___ 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: help with making a port
On Sun, Jul 7, 2013 at 10:12 AM, Aryeh Friedman aryeh.fried...@gmail.comwrote: I am attempting to put together a port for a new program and I am getting a very odd error message (i.e. it says the port conflicts with itself!?!?!?!): pkg-static: foo-0.1 conflicts with foo-0.1 (installs files into the same place). Problematic file: /usr/local/share/foo/foo.jar What causes this and how do I fix the make file? Posting your port code can only help in assisting. Thanks. -jgh -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve ___ 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: help with making a port
It uses a non-standard build system (devel/cook) but here is the Makefile for the port itself (not the program). Also note for legal reasons (we are still in the process of getting a trademark on the name) I have changed the actual port name, category and comment [the real values are known to one of the 10-CURRENT developers we are working with though]. Also note I have not added any of the depends stuff yet: # $FreeBSD$ PORTNAME= foo PORTVERSION= 0.1 CATEGORIES= bar MASTER_SITES= ftp://foo.org/foo/ MAINTAINER= supp...@foo.org COMMENT= A foobar platform .include bsd.port.mk On Sun, Jul 7, 2013 at 1:36 PM, Jason Helfman j...@freebsd.org wrote: On Sun, Jul 7, 2013 at 10:12 AM, Aryeh Friedman aryeh.fried...@gmail.com wrote: I am attempting to put together a port for a new program and I am getting a very odd error message (i.e. it says the port conflicts with itself!?!?!?!): pkg-static: foo-0.1 conflicts with foo-0.1 (installs files into the same place). Problematic file: /usr/local/share/foo/foo.jar What causes this and how do I fix the make file? Posting your port code can only help in assisting. Thanks. -jgh -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve ___ 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: help with making a port
oops forgot the pkg-plist: share/foo/foo.jar etc/rc.d/foo etc/foo/instances apache-tomcat-7.0/webapps/foo.war On Sun, Jul 7, 2013 at 1:42 PM, Aryeh Friedman aryeh.fried...@gmail.com wrote: It uses a non-standard build system (devel/cook) but here is the Makefile for the port itself (not the program). Also note for legal reasons (we are still in the process of getting a trademark on the name) I have changed the actual port name, category and comment [the real values are known to one of the 10-CURRENT developers we are working with though]. Also note I have not added any of the depends stuff yet: # $FreeBSD$ PORTNAME= foo PORTVERSION= 0.1 CATEGORIES= bar MASTER_SITES= ftp://foo.org/foo/ MAINTAINER= supp...@foo.org COMMENT= A foobar platform .include bsd.port.mk On Sun, Jul 7, 2013 at 1:36 PM, Jason Helfman j...@freebsd.org wrote: On Sun, Jul 7, 2013 at 10:12 AM, Aryeh Friedman aryeh.fried...@gmail.com wrote: I am attempting to put together a port for a new program and I am getting a very odd error message (i.e. it says the port conflicts with itself!?!?!?!): pkg-static: foo-0.1 conflicts with foo-0.1 (installs files into the same place). Problematic file: /usr/local/share/foo/foo.jar What causes this and how do I fix the make file? Posting your port code can only help in assisting. Thanks. -jgh -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve ___ 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: help with making a port
On Sun, Jul 7, 2013 at 10:44 AM, Aryeh Friedman aryeh.fried...@gmail.comwrote: oops forgot the pkg-plist: share/foo/foo.jar etc/rc.d/foo etc/foo/instances apache-tomcat-7.0/webapps/foo.war On Sun, Jul 7, 2013 at 1:42 PM, Aryeh Friedman aryeh.fried...@gmail.com wrote: It uses a non-standard build system (devel/cook) but here is the Makefile for the port itself (not the program). Also note for legal reasons (we are still in the process of getting a trademark on the name) I have changed the actual port name, category and comment [the real values are known to one of the 10-CURRENT developers we are working with though]. Also note I have not added any of the depends stuff yet: # $FreeBSD$ PORTNAME= foo PORTVERSION= 0.1 CATEGORIES= bar MASTER_SITES= ftp://foo.org/foo/ MAINTAINER= supp...@foo.org COMMENT= A foobar platform .include bsd.port.mk Well, nothing looks suspect at this point. Perhaps you have another port installed that is conflicting with the same file that is installed in that location. Maybe see what package that file in conflict is registered to. On a side note, it is highly unrecommended to install a war file, as that will leave the filesystem unclean on de-installation. It is standard practice to expand the war file in the work directory of the port, then install the files contained within the war under the application server (such as tomcat), and add those files to the plist. I have many examples of this if you need assistance. -jgh -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve ___ 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: help with making a port
Looking in /var/db/pkg and /var/db/ports I see nothing... anywhere else to look? ___ 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
www/seamonkey update distinfo doesn't match what enigmail is providing
Hi, distinfo for enigmail-1.5.2.tar.gz says the size should be 1211342, however the enigmail download comes out at 1211395 bytes with a different sha256 hash. Leads to the expected: === Found saved configuration for seamonkey-2.19 = enigmail-1.5.2.tar.gz doesn't seem to exist in /usr/ports/distfiles//. = Attempting to fetch http://www.enigmail.net/download/source/enigmail-1.5.2.tar.gz fetch: http://www.enigmail.net/download/source/enigmail-1.5.2.tar.gz: size mismatch: expected 1211342, actual 1211395 = Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/enigmail-1.5.2.tar.gz fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/enigmail-1.5.2.tar.gz: File unavailable (e.g., file not found, no access) = Couldn't fetch it - please try to retrieve this = port manually into /usr/ports/distfiles// and try again. *** [do-fetch] Error code 1 Stop in /usr/ports/www/seamonkey. *** [build] Error code 1 Stop in /usr/ports/www/seamonkey. Thanks, Gary ___ 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: help with making a port
pkg which /path/to/file or pkg_info -W /path/to/file Odd though that you checked there, and it wasn't recorded -jgh On Sun, Jul 7, 2013 at 11:55 AM, Aryeh Friedman aryeh.fried...@gmail.comwrote: Looking in /var/db/pkg and /var/db/ports I see nothing... anywhere else to look? -- -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve ___ 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: help with making a port
On Sun, Jul 7, 2013 at 3:51 PM, Jason Helfman j...@freebsd.org wrote: pkg which /path/to/file or pkg_info -W /path/to/file Odd though that you checked there, and it wasn't recorded aryeh@dev:/home/aryeh% pkg_info -W /usr/local/share/foo/foo.jar pkg_info: You appear to be using the newer pkg(1) tool on this system for package management, rather than the legacy package management tools (pkg_*). The legacy tools should no longer be used on this system. pkg_info: /var/db/pkg/aegis-4.24.3/+CONTENTS: No such file or directory aryeh@dev:/home/aryeh% pkg_info which /usr/local/share/foo/foo.jar pkg_info: You appear to be using the newer pkg(1) tool on this system for package management, rather than the legacy package management tools (pkg_*). The legacy tools should no longer be used on this system. pkg_info: can't find package 'which' installed or in a file! tar: +*: Not found in archive tar: Error exit delayed from previous errors. pkg_info: tar extract of /usr/local/share/foo/foo.jar failed! pkg_info: error during unpacking, no info for '/usr/local/share/foo/foo.jar' available ___ 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
[QAT] r322465: 4x leftovers
. Update to 2.2.12. . Pet portlint some: . Switch to new style header. . Use MASTER_SITE_AFTERSTEP. . s/file/f/ in .for loops. - Build ID: 20130707230200-61307 Job owner: gle...@freebsd.org Buildtime: 8 minutes Enddate: Sun, 07 Jul 2013 23:09:52 GMT Revision: r322465 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=322465 - Port:x11-wm/afterstep-stable 2.2.12 Buildgroup: 9.1-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gle...@freebsd.org/20130707230200-61307-159116/afterstep-2.2.12.log Buildgroup: 9.1-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gle...@freebsd.org/20130707230200-61307-159117/afterstep-2.2.12.log Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gle...@freebsd.org/20130707230200-61307-159118/afterstep-2.2.12.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gle...@freebsd.org/20130707230200-61307-159119/afterstep-2.2.12.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20130707230200-61307 redports https://qat.redports.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
[QAT] r322466: 4x leftovers
. More portlint petting (fix patch file names). - Build ID: 20130707230600-63614 Job owner: gle...@freebsd.org Buildtime: 21 minutes Enddate: Sun, 07 Jul 2013 23:27:25 GMT Revision: r322466 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=322466 - Port:x11-wm/afterstep-stable 2.2.12 Buildgroup: 9.1-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gle...@freebsd.org/20130707230600-63614-159120/afterstep-2.2.12.log Buildgroup: 9.1-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gle...@freebsd.org/20130707230600-63614-159121/afterstep-2.2.12.log Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gle...@freebsd.org/20130707230600-63614-159122/afterstep-2.2.12.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gle...@freebsd.org/20130707230600-63614-159123/afterstep-2.2.12.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20130707230600-63614 redports https://qat.redports.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: help with making a port
On 08/07/2013 05:32, Aryeh Friedman wrote: On Sun, Jul 7, 2013 at 3:51 PM, Jason Helfman j...@freebsd.org wrote: pkg which /path/to/file or pkg_info -W /path/to/file aryeh@dev:/home/aryeh% pkg_info -W /usr/local/share/foo/foo.jar pkg_info: You appear to be using the newer pkg(1) tool on this system Of the two examples 'pkg_info -W' is the old way and 'pkg which' is the new way. The error from pkg_info -W indicates you have the new package system setup and need to use the pkg which command. Is this your first attempt at making the port? Maybe you have an old attempt still in place. Did you move the port to a new category folder? As foo-0.1 isn't the real name of the port, are you certain that the name you are using is a new unique name? ___ 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: A note re: updating devel/apr (UPDATING entry 20130706)
On Sun, 7 Jul 2013 06:47:38 -0700 David Wolfskill da...@catwhisker.org wrote: Empirically, I have found that the given instructions (for portmaster) work well -- if Apache's httpd is not running during the portmaster -r apr run. I ran into problems as well, but they weren't solved even by stopping apache. I had to rebuild apache first, and after that portmaster -d -r apr finished fine. -- Marko Cupać ___ 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
