[QAT] r337952: 4x leftovers
Install the showchar binary as show_char to avoid a conflict with print/psutils. Bump PORTREVISION - Build ID: 20131229104000-26307 Job owner: r...@freebsd.org Buildtime: 9 minutes Enddate: Sun, 29 Dec 2013 10:48:57 GMT Revision: r337952 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=337952 - Port:misc/biosfont-demos 1.1_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~r...@freebsd.org/20131229104000-26307-245120/biosfont-demos-1.1_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~r...@freebsd.org/20131229104000-26307-245121/biosfont-demos-1.1_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~r...@freebsd.org/20131229104000-26307-245122/biosfont-demos-1.1_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~r...@freebsd.org/20131229104000-26307-245123/biosfont-demos-1.1_2.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20131229104000-26307 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: Berkeley DB cleanup has apparently broken ports where no db is currently installed
On Sat, 28 Dec 2013 23:44:35 -0800 Kevin Oberman rkober...@gmail.com wrote: On Thu, Dec 26, 2013 at 12:56 AM, Doug Barton do...@dougbarton.us wrote: On 12/26/2013 12:41 AM, Matthias Andree wrote: I disagree on the assessments of efforts here. I checked the docs, and the actual .db files are supposed to be compatible, Sure, they are, to some extent, SUPPOSED to be compatible. Experience tells us that is not the case. excepting the corner cases mentioned in the wiki. The manual effort only exists for ports using BDB in transactional mode, while most ports just use it as a key-value data vault. So you're volunteering to walk every user whose stuff gets broken through the repair? Ttbomk, deprecated does not cause build failures, and even if so, WITH_BDB_VER=5 would fix that. portmaster treats DEPRECATED as a fatal error. I did neglect to point that out in my previous post however. Finally, I would like to see technical or other_compelling_ reasons why we would need 48 in the tree in the future. Well shouldn't that argument go the other way around? Shouldn't the people proposing the purge be the ones to provide _compelling_ reasons to do the purge? Doug I updated from 9-Stable to 10.0-RC3 dy before yesterday. I had one odd error during the upgrade, but managed to complete the upgrade. Then I re-built all ports. I had a few issues, all resolved except one that i have opened a PR for, but I did have a very annoying time with Berkeley DB. I had deleted all ports, so I assumed that port requiring Berkeley DB would use db5 or db6. But, as Doug noted, no such luck. As Doug pointed out, this is because some ports require db4x. Specifically, databases/evolution-data-server required db41. No option for any newer version. apr1 required db42+, but that just pulls in db4* forts, so no db5 gets installed, even though the port clearly stats that it works with 5. So 4.2+ really means any db4. version. There is no reason that ports using USE_BDB=4.\+ could not have been found (by a simple grep) and been fixed to use db5 (assuming that they really do work with db5), but they were not. Or the Mk files could have caused the cases where db4.\+ were called for that this could not have installed db5 or even db6 rather than insist on db4. (And, quite oddly, the LOWEST db4 version that allowed was the one installed when no matching db was installed. Rather than mess around with fixing multiple Makefiles while my system was unable to do much of anything, I just removed the DEPRECATED lines form db41, db42, and db43. I'll need to go clean them all up, now. And some don't even make it clear that they will run with db5. And I still have seen no reason that the db4 ports really needed removal. They still work fine and are widely used. Deprecation was just asking for trouble. (Don't forget that a DEPRECATED statement in a port Makefile is fatal.) I will also mention that the man page for portmaster REALLY needs to be updated for pkgng. This wasted just a bit more of my time. Due to the iconv move to base, the quick and dirty rebuild option of portmaster -aD fails miserably. I suspect portupgrade would have a similar problem, but I have not used it in a couple of years, so I can't be sure. A side note on the iconv change: It seems like most ports have been changed to use base iconv where available, so the only criterion was ABI compatibility. The fact that some ports are written for GNU iconv and not POSIX iconv wasn't taken into account. The most prominent example is PHP5, converters/php5-iconv to be precise. Its documentation clearly describes GNU iconv extensions (TRANSLIT/IGNORE) as core features - it does not qualify based on you iconv library, because PHP5 is supposed to be built with GNU iconv. It was changed nevertheless, so upgrading to 10-RELEASE and rebuilding PHP5 will break people's code. I opened ports/184596 a few weeks ago, no response so far: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/184596 On the whole, I have to call this one a really botched change that should be rolled back until it can be implemented to work properly, at least for a clean install of all ports. -- 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
[QAT] r338013: 4x fail, 8x depend (forbidden: triggering a nasty freebsd bug in java/openjdk6), 2x chown, 2x ???, 8x success
Stage ports maintained by me in irc java mail Cleanups in several places - Build ID: 20131229154800-12144 Job owner: cr...@freebsd.org Buildtime: 69 minutes Enddate: Sun, 29 Dec 2013 16:56:51 GMT Revision: r338013 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=338013 - Port:irc/charybdis 3.4.2_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~cr...@freebsd.org/20131229154800-12144-245400/charybdis-3.4.2_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~cr...@freebsd.org/20131229154800-12144-245401/charybdis-3.4.2_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~cr...@freebsd.org/20131229154800-12144-245402/charybdis-3.4.2_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~cr...@freebsd.org/20131229154800-12144-245403/charybdis-3.4.2_1.log - Port:java/castor 1.3.2 Buildgroup: 8.4-QAT/amd64 Buildstatus: DEPEND (FORBIDDEN: TRIGGERING A NASTY FREEBSD BUG IN JAVA/OPENJDK6) Buildgroup: 8.4-QAT/i386 Buildstatus: DEPEND (FORBIDDEN: TRIGGERING A NASTY FREEBSD BUG IN JAVA/OPENJDK6) Buildgroup: 9.2-QAT/amd64 Buildstatus: DEPEND (FORBIDDEN: TRIGGERING A NASTY FREEBSD BUG IN JAVA/OPENJDK6) Buildgroup: 9.2-QAT/i386 Buildstatus: DEPEND (FORBIDDEN: TRIGGERING A NASTY FREEBSD BUG IN JAVA/OPENJDK6) - Port:java/jgraph 5.13.0.4 Buildgroup: 8.4-QAT/amd64 Buildstatus: FAIL Buildgroup: 8.4-QAT/i386 Buildstatus: FAIL Buildgroup: 9.2-QAT/amd64 Buildstatus: FAIL Buildgroup: 9.2-QAT/i386 Buildstatus: FAIL - Port:java/jgraphx 1.10.3.0 Buildgroup: 8.4-QAT/amd64 Buildstatus: DEPEND (FORBIDDEN: TRIGGERING A NASTY FREEBSD BUG IN JAVA/OPENJDK6) Buildgroup: 8.4-QAT/i386 Buildstatus: DEPEND (FORBIDDEN: TRIGGERING A NASTY FREEBSD BUG IN JAVA/OPENJDK6) Buildgroup: 9.2-QAT/amd64 Buildstatus: DEPEND (FORBIDDEN: TRIGGERING A NASTY FREEBSD BUG IN JAVA/OPENJDK6) Buildgroup: 9.2-QAT/i386 Buildstatus: DEPEND (FORBIDDEN: TRIGGERING A NASTY FREEBSD BUG IN JAVA/OPENJDK6) - Port:mail/biabam 0.9.7_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~cr...@freebsd.org/20131229154800-12144-245416/biabam-0.9.7_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~cr...@freebsd.org/20131229154800-12144-245417/biabam-0.9.7_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~cr...@freebsd.org/20131229154800-12144-245418/biabam-0.9.7_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~cr...@freebsd.org/20131229154800-12144-245419/biabam-0.9.7_2.log - Port:mail/sympa 6.1.17_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: CHOWN Log: https://qat.redports.org//~cr...@freebsd.org/20131229154800-12144-245420/sympa-6.1.17_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: CHOWN Log: https://qat.redports.org//~cr...@freebsd.org/20131229154800-12144-245421/sympa-6.1.17_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: ??? Log: https://qat.redports.org//~cr...@freebsd.org/20131229154800-12144-245422/sympa-6.1.17_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: ??? Log: https://qat.redports.org//~cr...@freebsd.org/20131229154800-12144-245423/sympa-6.1.17_1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20131229154800-12144 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 10.0-RC3 AMD64 pdftk and gcc 4.6.4 dependency problem
Hello :-) When trying to install pdftk I get gcc dependency problem: # uname -a FreeBSD hexagon 10.0-RC3 FreeBSD 10.0-RC3 #0 r259778: Mon Dec 23 23:27:58 UTC 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 # pkg install pdftk Updating repository catalogue The following 2 packages will be installed: Installing gcc46: 4.6.4_1,1 Installing pdftk: 2.02 The installation will require 570 MB more space 0 B to be downloaded Proceed with installing packages [y/N]: y (..) pkg: WARNING: locally installed gcc-4.6.4 conflicts on /usr/local/man/man1/rebuild-gcj-db46.1.gz with: - gcc46-4.6.4_1,1 pkg: WARNING: locally installed gcc-4.6.4 conflicts on /usr/local/man/man3/ffi46.3.gz with: - gcc46-4.6.4_1,1 pkg: WARNING: locally installed gcc-4.6.4 conflicts on /usr/local/man/man3/ffi_call46.3.gz with: - gcc46-4.6.4_1,1 pkg: WARNING: locally installed gcc-4.6.4 conflicts on /usr/local/man/man3/ffi_prep_cif46.3.gz with: - gcc46-4.6.4_1,1 pkg: WARNING: locally installed gcc-4.6.4 conflicts on /usr/local/share/gcc-4.6.4/python/libjava/aotcompile.py with: - gcc46-4.6.4_1,1 pkg: WARNING: locally installed gcc-4.6.4 conflicts on /usr/local/share/gcc-4.6.4/python/libjava/classfile.py with: - gcc46-4.6.4_1,1 pkg: WARNING: locally installed gcc-4.6.4 conflicts on /usr/local/share/gcc-4.6.4/python/libstdcxx/__init__.py with: - gcc46-4.6.4_1,1 pkg: WARNING: locally installed gcc-4.6.4 conflicts on /usr/local/share/gcc-4.6.4/python/libstdcxx/v6/__init__.py with: - gcc46-4.6.4_1,1 pkg: WARNING: locally installed gcc-4.6.4 conflicts on /usr/local/share/gcc-4.6.4/python/libstdcxx/v6/printers.py with: - gcc46-4.6.4_1,1 pkg: WARNING: locally installed gcc-4.6.4 conflicts on /usr/local/share/java/libgcj-4.6.4.jar with: - gcc46-4.6.4_1,1 pkg: WARNING: locally installed gcc-4.6.4 conflicts on /usr/local/share/java/libgcj-tools-4.6.4.jar with: - gcc46-4.6.4_1,1 -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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
Still no traceback for ports conflicts during pkg upgrade
I am getting several ports conflicts when doing a pkg upgrade. The most obvious example is lang/gcc vs lang/gcc46: pkg: WARNING: locally installed gcc-4.6.4 conflicts on /usr/local/lib/gcc46/include/c++/x86_64-portbld-freebsd11.0/bits/error_constants.h with: - gcc46-4.6.4_1,1 As I had requested previously, There needs to be an -x (exclude) flag or better yet a traceback method for pkg upgrade so that one can trace the port causing the issue. lang/gcc46 is not the only port causing such problem. I admit that one of the possible causes could be that I marcusmerge the gnome3 ports. However, this does not make my request any less sensible, since there will probably be many other development branches in the future. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Still-no-traceback-for-ports-conflicts-during-pkg-upgrade-tp5872335.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ 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] r338048: 4x leftovers
Enable stage support - Build ID: 20131229215800-36824 Job owner: joh...@freebsd.org Buildtime: 52 minutes Enddate: Sun, 29 Dec 2013 22:50:17 GMT Revision: r338048 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=338048 - Port:math/sc 7.16_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~joh...@freebsd.org/20131229215800-36824-245620/sc-7.16_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~joh...@freebsd.org/20131229215800-36824-245621/sc-7.16_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~joh...@freebsd.org/20131229215800-36824-245622/sc-7.16_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~joh...@freebsd.org/20131229215800-36824-245623/sc-7.16_1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20131229215800-36824 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: [FIXED] ports/183791: audio/liba52 (liba52-0.7.4_2) is not jobs safe
On Dec 25, 2013, at 8:02 AM, Peter p...@citylink.dinoex.sub.org wrote: This seems to be a race condition with the timestamps of the Makefiles. make install thinks that the Makefiles are outdated, and recreates them before doing the install - but now with the target pointing directly to /usr/local and not to the staging area. In the log we can see this happening: Making install in liba52 gmake[1]: Entering directory `/usr/ports/audio/liba52/work/a52dec-0.7.4/liba52' cd .. \ CONFIG_FILES=liba52/Makefile CONFIG_HEADERS= /bin/sh ./config.status config.status: creating liba52/Makefile config.status: executing default-1 commands gmake[1]: Leaving directory `/usr/ports/audio/liba52/work/a52dec-0.7.4/liba52' gmake[1]: Entering directory `/usr/ports/audio/liba52/work/a52dec-0.7.4/liba52' gmake[2]: Entering directory `/usr/ports/audio/liba52/work/a52dec-0.7.4/liba52' /bin/sh ../autotools/mkinstalldirs /usr/local/lib while on successful runs these lines do not appear: Making install in liba52 gmake[1]: Entering directory `/usr/ports/audio/liba52/work/a52dec-0.7.4/liba52' gmake[2]: Entering directory `/usr/ports/audio/liba52/work/a52dec-0.7.4/liba52' /bin/sh ../autotools/mkinstalldirs /usr/ports/audio/liba52/work/stage/usr/local/lib I could not figure out why or how this happens - but for now a suitable workaround seems to be the following addition to the (main) makefile: pre-install: touch work/a52dec-*/*/Makefile I can confirm that addition to the Makefile worked perfectly for me on all of 200 runs on both test servers. Thanks Peter! Can someone close the PR after making a commit with the addition of the aforementioned pre-install target to /usr/ports/audio/liba52/Makefile please? (No revision bump necessary.) -Chad ___ 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
