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/cowbell broken because: No more public distfiles build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=cowbell portname: audio/liquidsoap broken because: Fails to link build errors: http://beefy2.isc.freebsd.org/bulk/93amd64-RELENG_9_3/latest/logs/errors/liquidsoap-1.0.0_3.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=liquidsoap portname: audio/raproxy broken because: Unfetchable build errors: http://beefy1.isc.freebsd.org/bulk/91i386-quarterly/latest/logs/errors/raproxy-3.0b1_1.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=raproxy portname: audio/wmauda broken because: Does not work with audacious 3.5 or later build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=wmauda portname: audio/x11amp broken because: hangs at start with gtk and linker errors build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=x11amp portname: biology/blast broken because: Mark as broken: no checksum provided build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=blast portname: biology/embassy broken because: does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=embassy portname: cad/alliance broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=alliance portname: chinese/big5con broken because: build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=big5con portname: chinese/hztty broken because: build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=hztty portname: chinese/miniChinput broken because: Hard code make, gcc, g++ and more everywhere build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=miniChinput portname: chinese/msttf broken because: no distinfo provided build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=msttf portname: databases/firebird21-client broken because: Does not respect CC and hardcode gcc at some places build errors: http://beefy1.isc.freebsd.org/bulk/10i386-quarterly/latest/logs/errors/firebird21-client-2.1.5_1.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=firebird21-client portname: databases/flare broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=flare portname: databases/kinterbasdb broken because: Does not build with modern compilers build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=kinterbasdb portname:
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: archivers/rpm5 broken because: Does not package build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=rpm5 portname: audio/audacious-dumb broken because: Does not work with audacious 3.5 or later build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=audacious-dumb portname: audio/aureal-kmod broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=aureal-kmod portname: audio/cowbell broken because: No more public distfiles build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=cowbell portname: audio/lastfm-desktop broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=lastfm-desktop portname: audio/liquidsoap broken because: Fails to link build errors: http://beefy2.isc.freebsd.org/bulk/93amd64-RELENG_9_3/latest/logs/errors/liquidsoap-1.0.0_3.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=liquidsoap portname: audio/qmidinet broken because: Fails to configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=qmidinet portname: audio/raproxy broken because: Unfetchable build errors: http://beefy1.isc.freebsd.org/bulk/91i386-quarterly/latest/logs/errors/raproxy-3.0b1_1.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=raproxy portname: audio/wmauda broken because: Does not work with audacious 3.5 or later build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=wmauda portname: audio/x11amp broken because: hangs at start with gtk and linker errors build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=x11amp portname: audio/xmms-openspc broken because: does not build on FreeBSD 10.x and later build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=xmms-openspc portname: biology/blast broken because: Mark as broken: no checksum provided build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=blast portname: biology/embassy broken because: does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=embassy portname: cad/alliance broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=alliance portname: chinese/big5con broken because: build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=big5con portname: chinese/hztty broken because: build errors: none. overview:
FreeBSD ports which are currently marked forbidden
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: audio/linux-f10-libaudiofile forbidden because: http://www.freshports.org/vuxml.php?vid=09f47c51-c1a6-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-f10-libaudiofile portname: audio/linux-f10-nas-libs forbidden because: http://www.freshports.org/vuxml.php?vid=bf7912f5-c1a8-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-f10-nas-libs portname: chinese/acroread8-zh_CN forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=acroread8-zh_CN portname: chinese/acroread8-zh_TW forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=acroread8-zh_TW portname: devel/linux-f10-dbus-glib forbidden because: http://www.freshports.org/vuxml.php?vid=77bb0541-c1aa-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-f10-dbus-glib portname: french/acroread8 forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=frenchportname=acroread8 portname: french/acroread9 forbidden because: No longer maintained upstream since 2013-06-26 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=frenchportname=acroread9 portname: ftp/linux-f10-curl forbidden because: http://www.freshports.org/vuxml.php?vid=9aecb94c-c1ad-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ftpportname=linux-f10-curl portname: german/acroread8 forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=germanportname=acroread8 portname: german/acroread9 forbidden because: No longer maintained upstream since 2013-06-26 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=germanportname=acroread9 portname: graphics/linux-f10-png forbidden because: http://www.freshports.org/vuxml.php?vid=262b92fe-81c8-11e1-8899-001ec9578670 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-f10-png portname: graphics/linux-f10-tiff forbidden because: http://www.freshports.org/vuxml.php?vid=8816bf3a-7929-11df-bcce-0018f3e2eb82 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-f10-tiff portname: japanese/acroread8 forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japaneseportname=acroread8 portname: japanese/acroread9 forbidden because: No longer maintained upstream since 2013-06-26 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japaneseportname=acroread9 portname: korean/acroread8 forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=koreanportname=acroread8 portname: net/dante forbidden because: Building on 10+ triggers a nasty bug with unix domain sockets build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=netportname=dante portname: net/linux-f10-openldap forbidden because: http://www.freshports.org/vuxml.php?vid=abad20bf-c1b4-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=netportname=linux-f10-openldap portname: net/ntp forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=netportname=ntp portname:
sams port disappeared
Hello! Today updated the ports collection and found that the port sams (www/sams) disappeared. Why is this, and when it appears? ___ 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: sams port disappeared
On 08/07/14 10:46, Михаил Величко wrote: Hello! Today updated the ports collection and found that the port sams (www/sams) disappeared. Why is this, and when it appears? it was removed since it depended on PHP 4, which is not supported anymore and itself removed long time ago from the tree: http://svnweb.freebsd.org/ports?view=revisionrevision=351683 (usually you can find the asnwer to these questions by using freshports: http://www.freshports.org/ ) It could reappear if someone takes the port and makes it work with a current version of PHP and submits it via bugzilla. BTW, the description says squid 2.x accounting. squid 2.x is on it's way to being obsolete too. -- Guido Falsi m...@madpilot.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ net-mgmt/pandorafms_agent | 4.0.1 | 5.1-140807 +-+ net-mgmt/pandorafms_console | 4.0.1 | 5.1-140807 +-+ net-mgmt/pandorafms_server | 4.0.1 | 5.1-140807 +-+ www/groupoffice | 3.7.24 | 6.0.10 +-+ x11/roxterm | 2.8.3 | 2.9.2 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
poudriere ports -c svn co ports
Hello, I will move from pkg_* tools to pkgng on my build host to create packages for my other laptops/netbooks. # poudriere ports -c will use a snapshot of the ports to build them; is it somehow possible to use a ports tree fetched by 'svn co' from head? Thanks matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ 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: poudriere ports -c svn co ports
07.08.2014 15:18, Matthias Apitz пишет: I will move from pkg_* tools to pkgng on my build host to create packages for my other laptops/netbooks. # poudriere ports -c will use a snapshot of the ports to build them; is it somehow possible to use a ports tree fetched by 'svn co' from head? I think that you are interested at -m (method) option for the command poudriere ports, create a ports tree: - % poudriere ports -c -p portstree_name -m svn+https - Update a portstree: - % poudriere ports -u -p portstree_name - In case of svn+https method the portstree will be updated to the HEAD. Look at POUDRIERE(8) for more info. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org 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: 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: vendir distfile has no top level directory
On Aug 7, 2014, at 1:08 AM, olli hauer oha...@gmx.de wrote: On 2014-08-07 05:18, Dan Langille wrote: I’m having a problem upgrading www/bacula-web to the latest version (see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191583). The problem: the vendor tarball has no top level directory. e.g. [root@testing ~/tmp/distfiles]# tar -xf /var/ports/distfiles/bacula-web-6.0.1.tgz [root@testing ~/tmp/distfiles]# ls DOCS application core joblogs.php pools.php README backupjob-report.phpclient-report.php index.php jobs.phptest.php [root@testing ~/tmp/distfiles]# Compare that to bacula, where I get: [root@testing ~/tmp/distfiles]# tar -xf /var/ports/distfiles/bacula-7.0.4.tar.gz [root@testing ~/tmp/distfiles]# ls bacula-7.0.4 Is there an optimal way to cater for this without pushing the issue upstream? — Hi Dan, you can specify NO_WRKSUBDIR=yes or overwrite the do-extract target. do-extract is what I will use, thank you. PS: I haven't found the 6.0.x source on sf.net only 5.0.x and 7.0.x The project seems to have moved from bacula.org to web-bacula.org and I think they host only there. — Dan Langille signature.asc Description: Message signed with OpenPGP using GPGMail
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
FreeBSD Port: graphics/GraphicsMagick
Error installing GraphicsMagick on FreeBSD 10.0-RELEASE Begin output of pkg install -y GraphicsMagick STDOUT: Updating repository catalogue FreeBSD repository is up-to-date All repositories are up-to-date The following 22 packages will be affected (of 0 checked): New packages to be INSTALLED: GraphicsMagick: 1.3.19_2,1 i386-wine-devel: 1.7.23,1 gcc: 4.7.4 mpfr: 3.1.2_2 gmp: 5.1.3_2 mpc: 1.0.2 gcc-ecj: 4.5 binutils: 2.24 dgs: 0.5.9.1_12 ghostscript9: 9.06_7 libpaper: 1.1.24_2 gsfonts: 8.11_6 cups-image: 1.7.3_1 cups-client: 1.7.3_2 svgalib: 1.4.3_7 lcms2: 2.6_3 jbig2dec: 0.11_2 libidn: 1.28_1 glib12: 1.2.10_13 webp: 0.4.0 giflib-nox11: 4.2.3_3 libwmf: 0.2.8.4_11 The process will require 707 MB more space 123 MB to be downloaded Fetching GraphicsMagick-1.3.19_2,1.txz... done Fetching i386-wine-devel-1.7.23,1.txz... done Fetching gcc-4.7.4.txz... done Fetching mpfr-3.1.2_2.txz... done Fetching gmp-5.1.3_2.txz... done Fetching mpc-1.0.2.txz... done Fetching gcc-ecj-4.5.txz... done Fetching binutils-2.24.txz... done Fetching dgs-0.5.9.1_12.txz... done Fetching dgs-0.5.9.1_12.txz... done STDERR: pkg: cached package dgs-0.5.9.1_12: size mismatch, fetching from remote pkg: cached package dgs-0.5.9.1_12: size mismatch, cannot continue End output of pkg install -y GraphicsMagick Anand ___ 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
pkg-devel fails to register any port
Hello, since the update to pkg-1.4.0.p.a6 it now fails to register any port (built with `make install` or portmaster) with the message like: === Installing for libgcrypt-1.6.1_3 === Checking if security/libgcrypt already installed === Registering installation for libgcrypt-1.6.1_3 pkg-static: sqlite error while executing INSERT INTO pkg_shlibs_required(package_id, shlib_id) VALUES (?1, (SELECT id FROM shlibs WHERE name = ?2)) in file pkgdb.c:1870: UNIQUE constraint failed: pkg_shlibs_required.package_id, pkg_shlibs_required.shlib_id *** Error code 70 Stop. Is this a known problem? -- Regards, Ruslan T.O.S. Of Reality ___ 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] 364313: 4x leftovers
sysutils/bacula-server: update to 7.0.4 PR: 191311 Submitted by: maintainer - Build ID: 20140807192600-6096 Job owner: w...@freebsd.org Buildtime: 17 minutes Enddate: Thu, 07 Aug 2014 19:43:19 GMT Revision: 364313 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=364313 - Port:sysutils/bacula-server 7.0.4 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140807192600-6096-393446/bacula-server-7.0.4.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140807192600-6096-393447/bacula-server-7.0.4.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140807192600-6096-393448/bacula-server-7.0.4.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140807192600-6096-393449/bacula-server-7.0.4.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140807192600-6096 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] 364317: 4x leftovers
sysutils/bacula-server: revert back to bacula-barcodes.sample Reported by:antoine - Build ID: 20140807193400-16905 Job owner: w...@freebsd.org Buildtime: 13 minutes Enddate: Thu, 07 Aug 2014 19:47:00 GMT Revision: 364317 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=364317 - Port:sysutils/bacula-server 7.0.4 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140807193400-16905-393462/bacula-server-7.0.4.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140807193400-16905-393463/bacula-server-7.0.4.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140807193400-16905-393464/bacula-server-7.0.4.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140807193400-16905-393465/bacula-server-7.0.4.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140807193400-16905 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
FreeBSD Port: doxygen-1.8.3.1_1,1
Hi, I tried building doxygen on FreeBSD 10.0 today, but the build failed : clang++ -c -pipe -O2 -Wall -W -pthread -D_THREAD_SAFE -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_XML_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/local/share/qt4/mkspecs/freebsd-clang -I. -I/usr/local/include/qt4/QtCore -I/usr/local/include/qt4/QtGui -I/usr/local/include/qt4/QtXml -I/usr/local/include/qt4 -I. -Imoc -I/usr/local/include/qt4 -I/usr/local/include -o obj/config_lex.o config_lex.cpp lex.config.c:1702:16: warning: function 'yyinput' is not needed and will not be emitted [-Wunneeded-internal-declaration] static int yyinput (void) Perhaps the compiler switch '-Wunneeded-internal-declaration' should be removed, or the source code should be modified. Best regards, Ewout Boks ___ 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: OCAML version 3 (legacy)
Hi Euan, I am replying to you and to the list po...@freebsd.org, because the question might be of general interest: On 7 Aug 2014, at 20:17, Euan Thoms wrote: [I need to port some third party software zith OCaml 3.X]. Is it possible that you or somebody else could make a legacy port for OCAML 3.x? I would do it myself but I am not a ports contributor. The last revision of the ports with OCaml 3.x is 345109, did you try to checkout (actually svn export) that revision of the port and build it? If this breaks, maybe you will need to checkout a full port tree at that revision—just because of Mk/*. I hope this helps, Michael ___ 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: pkg-devel fails to register any port
On Thu, Aug 07, 2014 at 10:17:05PM +0400, Ruslan Makhmatkhanov wrote: Hello, since the update to pkg-1.4.0.p.a6 it now fails to register any port (built with `make install` or portmaster) with the message like: === Installing for libgcrypt-1.6.1_3 === Checking if security/libgcrypt already installed === Registering installation for libgcrypt-1.6.1_3 pkg-static: sqlite error while executing INSERT INTO pkg_shlibs_required(package_id, shlib_id) VALUES (?1, (SELECT id FROM shlibs WHERE name = ?2)) in file pkgdb.c:1870: UNIQUE constraint failed: pkg_shlibs_required.package_id, pkg_shlibs_required.shlib_id *** Error code 70 Stop. Is this a known problem? I haven't taken time on it so no I don't know, but when reporting a problem about pkg can you send it on p...@freebsd.org where more pkg developper can view it? I have added it in CC regards, Bapt pgpZxNas3UVk0.pgp Description: PGP signature
Re: FreeBSD Port: doxygen-1.8.3.1_1,1
On 08/07/14 15:06, Ewout Boks wrote:
Hi,
I tried building doxygen on FreeBSD 10.0 today, but the build failed :
clang++ -c -pipe -O2 -Wall -W -pthread -D_THREAD_SAFE -DQT_NO_CAST_FROM_ASCII
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_XML_LIB -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/local/share/qt4/mkspecs/freebsd-clang -I.
-I/usr/local/include/qt4/QtCore -I/usr/local/include/qt4/QtGui
-I/usr/local/include/qt4/QtXml -I/usr/local/include/qt4 -I. -Imoc
-I/usr/local/include/qt4 -I/usr/local/include -o obj/config_lex.o config_lex.cpp
lex.config.c:1702:16: warning: function 'yyinput' is not needed and will not be
emitted
[-Wunneeded-internal-declaration]
static int yyinput (void)
Perhaps the compiler switch '-Wunneeded-internal-declaration' should be
removed, or the source code should be modified.
Best regards,
Ewout Boks
It has nothing to do with the compiler flag or the source code, it has to do
with the fact that doxygen is expecting a newer version of flex than what is in
the base system. I am attaching a patch that I currently have on my local system
that allows it to build, in lieu of the 1.8.7 patch that is being looked in to.
I might have to send this in as a bug report if we can't get the 1.8.7 update
done, though.
Thanks,
Naram Qashat
Index: /usr/ports/devel/doxygen/Makefile
===
--- /usr/ports/devel/doxygen/Makefile (revision 363687)
+++ /usr/ports/devel/doxygen/Makefile (working copy)
@@ -16,7 +16,8 @@
LICENSE= GPLv2
LICENSE_FILE= ${WRKSRC}/LICENSE
-BUILD_DEPENDS= tmake:${PORTSDIR}/devel/tmake
+BUILD_DEPENDS= tmake:${PORTSDIR}/devel/tmake \
+ flex0:${PORTSDIR}/textproc/flex
LIB_DEPENDS= libpng15.so:${PORTSDIR}/graphics/png
USES= bison iconv perl5 gmake
@@ -24,7 +25,8 @@
HAS_CONFIGURE= yes
QT_NONSTANDARD= yes # non-standard configure arguments
CONFIGURE_ARGS= --prefix ${PREFIX} --perl ${PERL} --make ${MAKE_CMD} \
- --install ${INSTALL}
+ --install ${INSTALL} --flex ${LOCALBASE}/bin/flex
+MAKE_JOBS_UNSAFE= yes
REINPLACE_ARGS= -i ''
EXTRACT_AFTER_ARGS= --exclude '*/libmd5' \
@@ -52,7 +54,7 @@
ALL_TARGET+= pdf
USE_TEX= latex:build
USE_GHOSTSCRIPT_BUILD= yes
-MAKE_ARGS+= HAVE_PDFDOCS=yes
+MAKE_ARGS+= HAVE_LATEX=yes
.endif # PDFDOCS
.endif # HTMLDOCS
___
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 Port: jdresolve-0.6.1_1
I installed the jdresolve port on FreeBSD 10.0-RELEASE-p6 using
Perl 5.16.3 and Net::DNS version 0.78 (the latest version as of
8/07/2014).
When I ran jdresolve against my Apache log file, I was getting
the string Net::DNS::DomainName1035=HASH(0x805788a08) instead
of the host names I was expecting. This is indicative of a
hash dereferencing error that is occurring due to changes in
the Net::DNS Perl modules.
I traced the problem in jdresolve to line 867, which contained
the following code:
$hosts{$query}{NAME} = $_-{ptrdname};
The $_ object is a Net:DNS:RR object, and ptrdname is a hash
reference containing a number of items. That reference contains
a reference to another hash called label, which contains a reference
to an array that has the individual name segments of the host name.
For example, if we were resolving the FreeBSD web server's IP address,
the array would contain the following items:
www
freebsd
org
These segments needs to be assembled into a complete host name
for use by jdresolve. The fix is to replace the old line of code
with this line of code:
$hosts{$query}{NAME} = join(.,@{$_-{ptrdname}-{label}});
This corrects the name resolution error in jdresolve. You can test
this fix by obtaining a copy of an Apache log file and running the
following test:
jdresolve access.log replacement.log
The replacement.log file will contain proper host names instead
of IP addresses. Just thought you might want to know.
Best,
Dave Stoddard
dgs at accelix.net
301-455-0245 : cell
___
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
