Re: OCAML version 3 (legacy)
Hi Euan, 2014-08-11 17:03 GMT+01:00 Euan Thoms e...@potensol.com: However, I was suggesting we have a legacy port for OCAML 3.x, just like we have for php and other important stuff that newer versions breaks things. If you are really in need for the 3.x version of OCaml compiler, you may want to try OPAM [1]. That is the ocaml-opam package [2] in the FreeBSD repositories. Although OPAM is dubbed as a package manager, it can actually manage different compiler versions, using its switch command [3]. Then you could install OCaml packages atop that compiler separately, isolated from other instances, giving the advantage of working with multiple OCaml versions at the same time. [1] https://opam.ocaml.org/ [2] http://www.freshports.org/devel/ocaml-opam [3] https://opam.ocaml.org/doc/Advanced_Usage.html ___ 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
[QAT] 364596: 4x leftovers
news/husky-devel: fix non-gcc builds PR: 192574 Submitted by: maintainer (Oleg Sharoyko) - Build ID: 20140811094400-55573 Job owner: mar...@freebsd.org Buildtime: 32 hours Enddate: Tue, 12 Aug 2014 17:30:55 GMT Revision: 364596 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=364596 - Port:news/husky-devel 1.9.20140519 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~mar...@freebsd.org/20140811094400-55573-395158/husky-devel-1.9.20140519.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~mar...@freebsd.org/20140811094400-55573-395159/husky-devel-1.9.20140519.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~mar...@freebsd.org/20140811094400-55573-395160/husky-devel-1.9.20140519.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~mar...@freebsd.org/20140811094400-55573-395161/husky-devel-1.9.20140519.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140811094400-55573 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
redports and build status
Hi there, I built a port in redports and I received a mail notifying that the builds were finished, but it seems redports couldn't figure out if the builds finished successfully. https://redports.org/buildarchive/20140812170901-30860 Any ideas of why this happened? Thanks in advance. ___ 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: Does pkg automatically download INDEX?
On 08/09/14 18:15, Naram Qashat wrote: On 08/09/14 19:45, Scot Hetzel wrote: On Fri, Aug 8, 2014 at 7:00 PM, Naram Qashat cyberb...@cyberbotx.com wrote: On 08/04/14 07:28, David Wolfskill wrote: On Mon, Aug 04, 2014 at 07:09:33AM -0400, Naram Qashat wrote: On 08/03/14 22:14, David Wolfskill wrote: On Sun, Aug 03, 2014 at 10:10:27PM -0400, Naram Qashat wrote: ... If there is a way to find out when any process is attempting to modify a file, that would probably help me narrow it down, but I'm not aware of anything that can do that, ... Well, chflags schg /usr/ports/INDEX* would *prevent* the modification ... This was a really good suggestion. Glad to help. :-) Peace, david OK, so while no programs have whined or complained, I get the feeling that something on my system is running portsnap without my knowledge. When I had set the schg flag on INDEX-9, an INDEX-9.bz2 file came up. I set the schg flag on that as well, and now I notice there are a bunch of files called .fetch.??.INDEX-9.bz2 (where ?? is a random string), as well as a file called .portsnap.INDEX. As far as I know, I don't have anything configured to run portsnap, but is there something that defaults to running portsnap occasionally? I couldn't find anything that would do that. Do your have a crontab entry that is running portsnap with the -I (update INDEX) option? http://www.pl.freebsd.org/doc/handbook/portsnap.html As far as I can tell, no, none of my crontabs have any references to portsnap in them. This is making me a bit stumped as to why it would be happening. I checked the main /etc/crontab, I checked the crontabs in /var/cron/tabs. I have searched inside of /etc and /usr/local/etc for anything related to portsnap. Nothing that would be doing this is coming up at all. Thanks, Naram Qashat ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org I ran into something similar once, and found out what was happening this way. 1. replace the portsnap executable with a shell script. Rename portsnap to something like /usr/sbin/portsnap.orig 2. This shell script should dump the current ENV and other stuff to a log file. Don't forget to put in a timestamp. And then do: exec /usr/sbin/portsnap.orig $* I did this and found that there was something in one of the .login scripts. G... ___ 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: redports and build status
On Tue, 12 Aug 2014 19:38:27 +0200 Fernando Apesteguía wrote: Hi there, I built a port in redports and I received a mail notifying that the builds were finished, but it seems redports couldn't figure out if the builds finished successfully. https://redports.org/buildarchive/20140812170901-30860 Any ideas of why this happened? Thanks in advance. I'm seeing a lot of these as well. CCing decke@ ___ 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; redports and build status
According to the Buildstatus wiki: finished The job was finished but the buildstatus could not be determined. This might be because of circular dependencies or because of redports internal problems. -- Carlos Jacobo Puga Medina c...@fbsd.es ___ 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] 364743: 4x leftovers
Fix run dependencies Note: the install/deinstall script still look a bit broken - Build ID: 20140812203000-6185 Job owner: anto...@freebsd.org Buildtime: 3 hours Enddate: Tue, 12 Aug 2014 23:11:17 GMT Revision: 364743 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=364743 - Port:print/cm-super 0.3.4_5 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~anto...@freebsd.org/20140812203000-6185-395854/cm-super-0.3.4_5.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~anto...@freebsd.org/20140812203000-6185-395855/cm-super-0.3.4_5.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~anto...@freebsd.org/20140812203000-6185-395856/cm-super-0.3.4_5.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~anto...@freebsd.org/20140812203000-6185-395857/cm-super-0.3.4_5.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140812203000-6185 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: redports and build status
FYI, take a look to this related issue: https://code.google.com/p/redports/issues/detail?id=6 Regards, -- Carlos Jacobo Puga Medina c...@fbsd.es ___ 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
10 failed ports (Staging bugs) - various maintainers...
For the logs, see: http://flashback.sorbs.net/logs/84amd64.isux.com/archive/logs/2014-08-12_17h21m40s/#failed Failed ports PackageOriginPhaseLog ruby19-iconv-1.9.3.547,1converters/ruby-iconvcheck-plistlogfile font-misc-meltho-1.0.3_1x11-fonts/font-misc-meltholeftovers logfile dejavu-2.34_4x11-fonts/dejavuleftoverslogfile font-bh-ttf-1.0.3_1x11-fonts/font-bh-ttfleftoverslogfile idnkit-1.0_4dns/idnkitcheck-plistlogfile json-c-0.11devel/json-ccheck-plistlogfile font-misc-ethiopic-1.0.3_1x11-fonts/font-misc-ethiopic leftoverslogfile ruby19-date2-4.0.19devel/ruby-date2check-plistlogfile ruby19-bdb-0.6.6_3databases/ruby-bdbcheck-plistlogfile openldap-client-2.4.39_1net/openldap24-clientcheck-plistlogfile -- Michelle Sullivan http://www.mhix.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: 10 failed ports (Staging bugs) - various maintainers...
Michelle Sullivan wrote: For the logs, see: http://flashback.sorbs.net/logs/84amd64.isux.com/archive/logs/2014-08-12_17h21m40s/#failed openldap-client-2.4.39_1net/openldap24-clientcheck-plistlogfile Running Q/A tests (stage-qa) Checking for pkg-plist issues (check-plist) === Parsing plist === Checking for items in STAGEDIR missing from pkg-plist Error: Orphaned: %%ETCDIR%%/ldap.conf === Checking for directories owned by MTREEs === Checking for directories handled by dependencies === Checking for items in pkg-plist which are not in STAGEDIR === Error: Plist issues found. *** Error code 1 -- Michelle Sullivan http://www.mhix.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: 10 failed ports (Staging bugs) - various maintainers...
Michelle Sullivan wrote: For the logs, see: http://flashback.sorbs.net/logs/84amd64.isux.com/archive/logs/2014-08-12_17h21m40s/#failed Failed ports PackageOriginPhaseLog dejavu-2.34_4x11-fonts/dejavuleftoverslogfile === Checking shared library dependencies ===phase: deinstall === Deinstalling for x11-fonts/dejavu === Deinstalling dejavu-2.34_4 === Checking for extra files and directories Files or directories left over: %%FONTSDIR%%/fonts.scale === Cleaning for dejavu-2.34_4 build of /usr/ports/x11-fonts/dejavu ended at Tue Aug 12 02:37:22 CEST 2014 build time: 00:00:32 font-misc-ethiopic-1.0.3_1x11-fonts/font-misc-ethiopic === Checking shared library dependencies ===phase: deinstall === Deinstalling for x11-fonts/font-misc-ethiopic === Deinstalling font-misc-ethiopic-1.0.3_1 === Checking for extra files and directories Files or directories left over: lib/X11/fonts/OTF/fonts.scale lib/X11/fonts/TTF/fonts.scale === Cleaning for font-misc-ethiopic-1.0.3_1 build of /usr/ports/x11-fonts/font-misc-ethiopic ended at Tue Aug 12 02:47:19 CEST 2014 build time: 00:00:24 -- Michelle Sullivan http://www.mhix.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: 10 failed ports (Staging bugs) - various maintainers...
Michelle Sullivan wrote: For the logs, see: http://flashback.sorbs.net/logs/84amd64.isux.com/archive/logs/2014-08-12_17h21m40s/#failed Failed ports PackageOriginPhaseLog font-misc-meltho-1.0.3_1x11-fonts/font-misc-meltholeftovers logfile === Checking shared library dependencies ===phase: deinstall === Deinstalling for x11-fonts/font-misc-meltho === Deinstalling font-misc-meltho-1.0.3_1 === Checking for extra files and directories Files or directories left over: lib/X11/fonts/OTF/fonts.scale === Cleaning for font-misc-meltho-1.0.3_1 build of /usr/ports/x11-fonts/font-misc-meltho ended at Tue Aug 12 05:09:09 CEST 2014 build time: 00:00:50 font-bh-ttf-1.0.3_1x11-fonts/font-bh-ttfleftoverslogfile === Checking shared library dependencies ===phase: deinstall === Deinstalling for x11-fonts/font-bh-ttf === Deinstalling font-bh-ttf-1.0.3_1 === Checking for extra files and directories Files or directories left over: lib/X11/fonts/TTF/fonts.scale === Cleaning for font-bh-ttf-1.0.3_1 build of /usr/ports/x11-fonts/font-bh-ttf ended at Tue Aug 12 02:51:14 CEST 2014 build time: 00:00:57 font-misc-ethiopic-1.0.3_1x11-fonts/font-misc-ethiopic leftoverslogfile === Checking shared library dependencies ===phase: deinstall === Deinstalling for x11-fonts/font-misc-ethiopic === Deinstalling font-misc-ethiopic-1.0.3_1 === Checking for extra files and directories Files or directories left over: lib/X11/fonts/OTF/fonts.scale lib/X11/fonts/TTF/fonts.scale === Cleaning for font-misc-ethiopic-1.0.3_1 build of /usr/ports/x11-fonts/font-misc-ethiopic ended at Tue Aug 12 02:47:19 CEST 2014 build time: 00:00:24 Of course here I am complaining but looking I see that some are common to both ports... can this be fixed or not because of the common files? (if not why not?) -- Michelle Sullivan http://www.mhix.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: 10 failed ports (Staging bugs) - various maintainers...
Michelle Sullivan wrote: For the logs, see: http://flashback.sorbs.net/logs/84amd64.isux.com/archive/logs/2014-08-12_17h21m40s/#failed Failed ports PackageOriginPhaseLog ruby19-iconv-1.9.3.547,1converters/ruby-iconvcheck-plistlogfile Checking for pkg-plist issues (check-plist) === Parsing plist === Checking for items in STAGEDIR missing from pkg-plist Error: Orphaned: @dirrmtry %%RUBY_LIBDIR%% === Checking for directories owned by MTREEs === Checking for directories handled by dependencies === Checking for items in pkg-plist which are not in STAGEDIR === Error: Plist issues found. *** Error code 1 ruby19-date2-4.0.19devel/ruby-date2check-plistlogfile Checking for pkg-plist issues (check-plist) === Parsing plist === Checking for items in STAGEDIR missing from pkg-plist Error: Orphaned: @dirrmtry %%RUBY_DOCDIR%% === Checking for directories owned by MTREEs === Checking for directories handled by dependencies === Checking for items in pkg-plist which are not in STAGEDIR === Error: Plist issues found. *** Error code 1 ruby19-bdb-0.6.6_3databases/ruby-bdbcheck-plistlogfile Running Q/A tests (stage-qa) Checking for pkg-plist issues (check-plist) === Parsing plist === Checking for items in STAGEDIR missing from pkg-plist Error: Orphaned: %%RUBY_MODDOCDIR%%/Changes Error: Orphaned: %%RUBY_MODDOCDIR%%/README.en Error: Orphaned: %%RUBY_MODDOCDIR%%/arraylike.rd Error: Orphaned: %%RUBY_MODDOCDIR%%/bdb.rd Error: Orphaned: %%RUBY_MODDOCDIR%%/cursor.rd Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/Btree.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/Common.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/Cursor.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/Env.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/Hash.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/Lock.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/LockDead.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/LockError.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/LockGranted.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/LockHeld.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/Lockid.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/Lsn.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/Queue.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/Recno.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/Recnum.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/Sequence.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/BDB/Txn.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/bdb_rb.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/common_rb.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/comxxx_rb.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/created.rid Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/cursor_rb.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/env_rb.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/exception_rb.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/brick.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/brick_link.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/bug.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/bullet_black.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/bullet_toggle_minus.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/bullet_toggle_plus.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/date.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/find.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/loadingAnimation.gif Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/macFFBgHack.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/package.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/page_green.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/page_white_text.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/page_white_width.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/plugin.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/ruby.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/tag_green.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/wrench.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/wrench_orange.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/images/zoom.png Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/index.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/js/darkfish.js Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/js/jquery.js Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/js/quicksearch.js Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/js/thickbox-compressed.js Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/lock_rb.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/log_rb.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/rdoc.css Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/sequence_rb.html Error: Orphaned: %%RUBY_MODDOCDIR%%/doc/transaction_rb.html Error: Orphaned: %%RUBY_MODDOCDIR%%/env.rd Error: Orphaned: %%RUBY_MODDOCDIR%%/hashlike.rd Error: Orphaned: %%RUBY_MODDOCDIR%%/lock.rd Error: Orphaned: %%RUBY_MODDOCDIR%%/log.rd Error: Orphaned: %%RUBY_MODDOCDIR%%/sequence.rd Error: Orphaned: %%RUBY_MODDOCDIR%%/transaction.rd
Re: 10 failed ports (Staging bugs) - various maintainers...
Michelle Sullivan wrote:
For the logs, see:
http://flashback.sorbs.net/logs/84amd64.isux.com/archive/logs/2014-08-12_17h21m40s/#failed
Failed ports
PackageOriginPhaseLog
json-c-0.11devel/json-ccheck-plistlogfile
===
Running Q/A tests (stage-qa)
Warning: 'lib/libjson-c.so.2' is not stripped consider using ${STRIP_CMD}
Warning: 'lib/libjson.so.1' is not stripped consider using ${STRIP_CMD}
Warning: .la libraries found, port needs USES=libtool
Checking for pkg-plist issues (check-plist)
=== Parsing plist
=== Checking for items in STAGEDIR missing from pkg-plist
=== Checking for directories owned by MTREEs
=== Checking for directories handled by dependencies
=== Checking for items in pkg-plist which are not in STAGEDIR
Error: Missing: @dirrmtry include/json
=== Error: Plist issues found.
*** Error code 1
Stop in /usr/ports/devel/json-c.
--
Michelle Sullivan
http://www.mhix.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: 10 failed ports (Staging bugs) - various maintainers...
Michelle Sullivan wrote: Michelle Sullivan wrote: For the logs, see: http://flashback.sorbs.net/logs/84amd64.isux.com/archive/logs/2014-08-12_17h21m40s/#failed Failed ports PackageOriginPhaseLog idnkit-1.0_4dns/idnkitcheck-plistlogfile Running Q/A tests (stage-qa) Checking for pkg-plist issues (check-plist) === Parsing plist === Checking for items in STAGEDIR missing from pkg-plist Error: Orphaned: etc/idn.conf Error: Orphaned: etc/idnalias.conf === Checking for directories owned by MTREEs === Checking for directories handled by dependencies === Checking for items in pkg-plist which are not in STAGEDIR === Error: Plist issues found. *** Error code 1 (I'll try to get a patch together for this as it's maintained by ports@ ) Patch (credit to 'Zi') diff -Nru idnkit.orig/pkg-plist idnkit/pkg-plist --- idnkit.orig/pkg-plist2014-07-02 18:07:48.0 -0500 +++ idnkit/pkg-plist2014-08-12 21:31:10.0 -0500 @@ -1,11 +1,7 @@ bin/idnconv bin/runidn -@unexec if cmp -s %D/etc/idn.conf %D/etc/idn.conf.sample; then rm -f %D/etc/idn.conf; fi -etc/idn.conf.sample -@exec [ ! -f %B/idn.conf ] cp %B/%f %B/idn.conf -@unexec if cmp -s %D/etc/idnalias.conf %D/etc/idnalias.conf.sample; then rm -f %D/etc/idnalias.conf; fi -etc/idnalias.conf.sample -@exec [ ! -f %B/idnalias.conf ] cp %B/%f %B/idnalias.conf +@sample etc/idn.conf.sample +@sample etc/idnalias.conf.sample include/idn/api.h include/idn/assert.h include/idn/checker.h Reported/Patched in: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192631 -- Michelle Sullivan http://www.mhix.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
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
