Re: splitting subversion port?
Hello, olli. You wrote 8 июня 2014 г., 1:25:40: oh This should be possible if the old pkg tools are no longer supported oh (this year Sept.) and code for sub packages is in the tree. oh Splitting the package now into several ports is not a preferred way. oh Building a full blown subversion triggers without sub packages x times a full oh build for every single shaped port (see for example bacula server/client) It is not exactly so in subversion case. Yes, configure step will be performed for each ports, and it is not very fast step, but after that each port will build only what it need to build: look at subversion bindings now. Bindings ports doesn't build libraries Ko, only binding. It could be done same way for mod_dav_svn Ko, etc. -- // Black Lion AKA Lev Serebryakov l...@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
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 +-+ deskutils/recoll| 1.19.13 | 1.19.14 +-+ 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
/usr/ports/lang/huc updates
https://github.com/uli/huc is a more current version, with fixes to work on 64bit architectures (HuC builds cleanly from ports on a FreeBSD11-current system I am running on an amd64 arch, but when I attempt to compile a helloworld.c program following http://hucdoc.nodtveidt.net/course01.html it throws a segfault and dumps core). My *guess* though I have not yet tried it is that using this updated version from github instead of the zeograd distile will yield more usable results; as well as have other bug fixes and feature improvements, the 3.21 codebase has apparently not been touched since 2006; while the github repo is under active development (with some very loose support to be found on #utopiasoft on EFNet's IRC servers). Thanks in advance! グ レ ェ -grey (as an aside, I am guessing that since the port maintainer is listed as po...@freebsd.org this port has no active maintainer, and has perhaps slipped under the radar because it seems to build cleanly as is presumably done in an automated fashion with poudriere or something similar; if it needs a maintainer, I can conceivably take a stab at it if necessary) ___ 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: Who was the mental genius
None of the above represents what I think FreeBSD ought to be about. +1 @JM: Being a port maintainer does not give you the right to talk down to others, much less ridicule anyone. Worse, you feel entitled to address others in such fashion quite regularly. You are in need of some serious style overhaul my friend. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Who-was-the-mental-genius-tp5918254p5918986.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
Re: Splitting devel/subversion into SEVERAL ports -- how fine-grained do we want to see it?
On Sun, 8 Jun 2014 00:16:18 +0400 Lev Serebryakov wrote: Hello, Ports. I've learned proper way to split subversion into several ports. Question is: how fine-grained should I do this? I want to split it at least into: (1) devel/subversion-libs-- base libs, used by all other ports. Options about SERF, BDB and SASL goes here. (2) devel/subversion-client -- all base tools, like svn, svnversion and so on, but not svnserve. (3) devel/subversion-server -- svnserve binary. (4) devel/subversion-tools -- additional tools (option now). (5) devel/subversion-apache -- all mod_dav_svn-related stuff. (6) devel/subversion-gnome -- GNOME KEyRing integration (option now). (7) devel/subversion-kde -- KDE KWallet integration (option now). (8) devel/subversion -- meta-port with options (and real stuff, like patches and all infrastructure). But it is possible to extract more options to separate ports: BDB repository format, remote access with svn: scheme and SERF support (http: scheme remote access) could be separate ports (and packages), not options! But maybe, it is too much already? I don't want to stop you from doing this, but if I were you I'd just wait for subpackages support. You may want to merge all those ports back into one port then. ___ 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: Splitting devel/subversion into SEVERAL ports -- how fine-grained do we want to see it?
On Sun, 8 Jun 2014 00:16:18 +0400 Lev Serebryakov l...@freebsd.org wrote: Hello, Ports. I've learned proper way to split subversion into several ports. Question is: how fine-grained should I do this? I want to split it at least into: (1) devel/subversion-libs-- base libs, used by all other ports. Options about SERF, BDB and SASL goes here. (2) devel/subversion-client -- all base tools, like svn, svnversion and so on, but not svnserve. (3) devel/subversion-server -- svnserve binary. (4) devel/subversion-tools -- additional tools (option now). (5) devel/subversion-apache -- all mod_dav_svn-related stuff. (6) devel/subversion-gnome -- GNOME KEyRing integration (option now). (7) devel/subversion-kde -- KDE KWallet integration (option now). (8) devel/subversion -- meta-port with options (and real stuff, like patches and all infrastructure). But it is possible to extract more options to separate ports: BDB repository format, remote access with svn: scheme and SERF support (http: scheme remote access) could be separate ports (and packages), not options! But maybe, it is too much already? -- // Black Lion AKA Lev Serebryakov l...@freebsd.org Holy... Is this Debian now? How about 14 packages to have granularity over what sub-library needed, and 23 others for each svn* command? And don't forget headers. An aspect of ports I liked was it followed/respected the upstream packaging mindset, instead of going for artificial repackaging like linux distros. This minigame of cutting other people works in tiny atomics bits so I have to figure what is missing at runtime is tiresome. If this is a binary/options issue, I'd rather see an effort in providing a system able to allow using globally packages with local build when desired options differs, and the reverse (build everything except a list of stuff where binary is prefered). Be more like macports, less like apt. My 2 cents. -- Matthieu Volat ma...@alkumuna.eu signature.asc Description: PGP signature
Re: Splitting devel/subversion into SEVERAL ports -- how fine-grained do we want to see it?
Hello, Tijl. You wrote 8 июня 2014 г., 14:16:14: TC I don't want to stop you from doing this, but if I were you I'd just TC wait for subpackages support. You may want to merge all those ports TC back into one port then. It is second way. But I didn't seen any estimations about subpackages support, and separate mod_dav_svn is request which I got twice a month. -- // Black Lion AKA Lev Serebryakov l...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Splitting devel/subversion into SEVERAL ports -- how fine-grained do we want to see it?
Hello, Matthieu. You wrote 8 июня 2014 г., 15:41:42: MV Holy... MV Is this Debian now? How about 14 packages to have granularity over what MV sub-library needed, and 23 others for each svn* command? And don't forget headers. MV An aspect of ports I liked was it followed/respected the upstream MV packaging mindset, instead of going for artificial repackaging like MV linux distros. This minigame of cutting other people works in tiny MV atomics bits so I have to figure what is missing at runtime is tiresome. MV If this is a binary/options issue, I'd rather see an effort in MV providing a system able to allow using globally packages with local MV build when desired options differs, and the reverse (build everything MV except a list of stuff where binary is prefered). With pkgng in play, I get more and more requests from people, who want to use only binary packages. And when such vital (for many) features as mod_dav_svn and (not so vital, but desirable) DE integration is non-default options of single port, it could not be done. BTW, nobody objects against separated language bindings, especially Java ones :) Really, I get requests to have mod_dav_svn package at least twice a month for all time subversion port exists. But, yes, maybe separation to libraries and binaries is too much, and I need only extract apache-related stuff and DE-related stuff. -- // Black Lion AKA Lev Serebryakov l...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Splitting devel/subversion into SEVERAL ports -- how fine-grained do we want to see it?
On Sun, 8 Jun 2014 16:27:15 +0400 Lev Serebryakov wrote: Hello, Tijl. You wrote 8 июня 2014 г., 14:16:14: TC I don't want to stop you from doing this, but if I were you I'd just TC wait for subpackages support. You may want to merge all those ports TC back into one port then. It is second way. But I didn't seen any estimations about subpackages support, and separate mod_dav_svn is request which I got twice a month. Yes, I have some questions about subpackages myself. For instance, will a port be able to depend on the subpackage of another port? Will the infrastructure be smart enough to build just that subpackage then or will it build the full package (and all of its dependencies) and then split up the stage directory? If a port has to smart then you may want to split subversion up now because you'll need all that logic for subpackages too. ___ 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: Splitting devel/subversion into SEVERAL ports -- how fine-grained do we want to see it?
On Sun, Jun 08, 2014 at 02:41:21PM +0200, Tijl Coosemans wrote: On Sun, 8 Jun 2014 16:27:15 +0400 Lev Serebryakov wrote: Hello, Tijl. You wrote 8 июня 2014 г., 14:16:14: TC I don't want to stop you from doing this, but if I were you I'd just TC wait for subpackages support. You may want to merge all those ports TC back into one port then. It is second way. But I didn't seen any estimations about subpackages support, and separate mod_dav_svn is request which I got twice a month. Yes, I have some questions about subpackages myself. For instance, will a port be able to depend on the subpackage of another port? Will the infrastructure be smart enough to build just that subpackage then or will it build the full package (and all of its dependencies) and then split up the stage directory? If a port has to smart then you may want to split subversion up now because you'll need all that logic for subpackages too. yes to all questions :) that is how subpackage will be, concerning the ETA, now pkg 1.3 has enough support for it, so after EOL of pkg_install I'll push the support for subpackages. regards, Bapt pgpO17iH9UqN5.pgp Description: PGP signature
Re: Splitting devel/subversion into SEVERAL ports -- how fine-grained do we want to see it?
On Sun, 8 Jun 2014, Lev Serebryakov wrote: Hello, Matthieu. You wrote 8 2014 ?., 15:41:42: MV Holy... MV Is this Debian now? How about 14 packages to have granularity over what MV sub-library needed, and 23 others for each svn* command? And don't forget headers. MV An aspect of ports I liked was it followed/respected the upstream MV packaging mindset, instead of going for artificial repackaging like MV linux distros. This minigame of cutting other people works in tiny MV atomics bits so I have to figure what is missing at runtime is tiresome. MV If this is a binary/options issue, I'd rather see an effort in MV providing a system able to allow using globally packages with local MV build when desired options differs, and the reverse (build everything MV except a list of stuff where binary is prefered). With pkgng in play, I get more and more requests from people, who want to use only binary packages. And when such vital (for many) features as mod_dav_svn and (not so vital, but desirable) DE integration is non-default options of single port, it could not be done. BTW, nobody objects against separated language bindings, especially Java ones :) Really, I get requests to have mod_dav_svn package at least twice a month for all time subversion port exists. But, yes, maybe separation to libraries and binaries is too much, and I need only extract apache-related stuff and DE-related stuff. This is less work and complication, and sounds like it will be enough to satisfy people. Later, if a split into more slave ports is needed, it can be done then. ___ 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
r356789 breaks rkhunter
I just upgraded rkhunter and the installer splatted the sample file over my .conf file. Running 'rkhunter --propupd' now quits with the error message The SCRIPTDIR configuration option has not been set by the installer. This option is now commented out in the .conf and .conf.sample file. # # This option specifies the script directory to use. # # The installer program will set the default directory. If this default is # subsequently commented out or removed, then the program will not run. # #SCRIPTDIR=/usr/local/lib/rkhunter/scripts This the correct directory where the scripts are installed. Uncommenting this and re-running the command now quits with this error message: Invalid INSTALLDIR configuration option - no installation directory specified. I have searched around and have not found a file containing this option. Help, please. Frank ___ 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: How are ports built now
--On June 7, 2014 at 11:16:04 PM +0200 olli hauer oha...@gmx.de wrote: On 2014-06-07 22:40, Paul Schmehl wrote: --On June 7, 2014 at 10:22:41 PM +0200 A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. Thanks. That's good to know. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? I'm pretty sure I did, but I ran it again. I noticed several errors which I will have to investigate. Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. I've been working on this for two days now, so the parameters have changed a bit. But here's an example of what prompted my question: This is the result of portmaster -ad === All (18) === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Install textproc/docproj Install print/ghostscript9 Upgrade pkgconf-0.9.5 to pkgconf-0.9.6 Upgrade lcms2-2.6_1 to lcms2-2.6_2 Install textproc/docbook-xml Install textproc/docbook-sgml Install www/mod_authnz_external22 === Proceed? y/n [y] n This is the result of pkg upgrade -n # pkg upgrade -n Updating repository catalogue Upgrades have been requested for the following 150 packages: Installing xf86vidmodeproto: 2.3.1 Installing damageproto: 1.2.1 Installing dri2proto: 2.8 Installing pciids: 20140526 Installing randrproto: 1.4.0 Installing perl5: 5.16.3_10 Installing db48: 4.8.30.0 Reinstalling autoconf-2.69 (direct dependency changed) Reinstalling automake-1.14 (direct dependency changed) Reinstalling bootstrap-openjdk-r351880 (needed shared library changed) Reinstalling curl-7.37.0 (options changed) Reinstalling dejavu-2.34_3 (options changed) Upgrading en-freebsd-doc: 43251,1 - 44807,1 Reinstalling gettext-0.18.3.1_1 (options changed) Reinstalling igor-1.431 (direct dependency changed) Reinstalling ja-font-ipa-00303_1 (direct dependency changed) Reinstalling libgcrypt-1.5.3_2 (direct dependency changed) Reinstalling libwmf-nox11-0.2.8.4_11 (direct dependency changed) Reinstalling libxcb-1.10_2 (direct dependency changed) Reinstalling libxslt-1.1.28_3 (direct dependency changed) Reinstalling mcrypt-2.6.8_1 (direct dependency changed) Reinstalling mkfontdir-1.0.7 (direct dependency changed) Reinstalling mysqltuner-1.3.0 (direct dependency changed) Reinstalling neon29-0.29.6_6 (direct dependency changed) Reinstalling p5-Carp-Clan-6.04 (direct dependency changed) Reinstalling p5-Locale-gettext-1.05_3 (direct dependency changed) Reinstalling p5-XML-Parser-2.41_1 (direct dependency changed) Reinstalling p5-type1inst-0.6.1_5 (options changed) Reinstalling perl5.14-5.14.4_7 (options changed) Reinstalling php5-5.4.29 (options changed) Reinstalling php5-bz2-5.4.29 (direct dependency changed) Reinstalling php5-ctype-5.4.29 (direct dependency changed) Reinstalling php5-curl-5.4.29 (direct dependency changed) Reinstalling php5-dom-5.4.29 (direct dependency changed) Reinstalling php5-filter-5.4.29 (direct dependency changed) Reinstalling php5-hash-5.4.29 (direct dependency changed) Reinstalling php5-iconv-5.4.29 (direct dependency changed) Reinstalling php5-json-5.4.29 (direct dependency changed) Reinstalling php5-mbstring-5.4.29 (direct dependency changed) Reinstalling php5-mssql-5.4.29 (direct dependency changed) Reinstalling php5-mysql-5.4.29 (direct dependency changed) Reinstalling php5-openssl-5.4.29 (direct dependency changed) Reinstalling php5-pdo-5.4.29 (direct dependency changed) Reinstalling php5-phar-5.4.29 (direct dependency changed) Reinstalling php5-posix-5.4.29 (direct dependency changed) Reinstalling php5-session-5.4.29 (direct dependency changed) Reinstalling php5-simplexml-5.4.29 (direct dependency changed) Reinstalling php5-tokenizer-5.4.29 (direct dependency changed) Reinstalling php5-xml-5.4.29 (direct dependency changed) Reinstalling
Re: How are ports built now
Hi Paul, On 08/06/2014 16:20, Paul Schmehl wrote: I have this in my /etc/make.conf file: DISABLE_VULNERABILITIES=yes FORCE_PKG_REGISTER=yes WITH_PKG=yes This should read: WITH_PKGNG=yes to encourage the use of the new pkg tools. Thanks, Daniel. ___ 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: How are ports built now
On 6/8/14, 11:20 AM, Paul Schmehl wrote: --On June 7, 2014 at 11:16:04 PM +0200 olli hauer oha...@gmx.de wrote: Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. I've been working on this for two days now, so the parameters have changed a bit. But here's an example of what prompted my question: This is the result of portmaster -ad === All (18) [[stuff]] === Proceed? y/n [y] n This is the result of pkg upgrade -n # pkg upgrade -n Updating repository catalogue Upgrades have been requested for the following 150 packages: [[different stuff]] The upgrade will require 426 MB more space 373 MB to be downloaded Clearly portmaster and pkg upgrade disagree on what work needs to be done. Do you have non-default port options configured? I believe the packages are all created with the default options, so that if you've installed everything from ports, and some of those ports with non-default options, your dependencies when upgrading with portmaster could end up looking different than when upgrading with pkg. ___ 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: How are ports built now
--On June 8, 2014 at 11:38:37 AM -0400 Kevin Phair phair.ke...@gmail.com wrote: On 6/8/14, 11:20 AM, Paul Schmehl wrote: --On June 7, 2014 at 11:16:04 PM +0200 olli hauer oha...@gmx.de wrote: Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. I've been working on this for two days now, so the parameters have changed a bit. But here's an example of what prompted my question: This is the result of portmaster -ad === All (18) [[stuff]] === Proceed? y/n [y] n This is the result of pkg upgrade -n # pkg upgrade -n Updating repository catalogue Upgrades have been requested for the following 150 packages: [[different stuff]] The upgrade will require 426 MB more space 373 MB to be downloaded Clearly portmaster and pkg upgrade disagree on what work needs to be done. Do you have non-default port options configured? I believe the packages are all created with the default options, so that if you've installed everything from ports, and some of those ports with non-default options, your dependencies when upgrading with portmaster could end up looking different than when upgrading with pkg. Yes, I do have a few ports with none-default options. The problem is, they're critical ports (like apache22). Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How are ports built now
On 2014-06-08 17:20, Paul Schmehl wrote: --On June 7, 2014 at 11:16:04 PM +0200 olli hauer oha...@gmx.de wrote: On 2014-06-07 22:40, Paul Schmehl wrote: --On June 7, 2014 at 10:22:41 PM +0200 A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. Thanks. That's good to know. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? I'm pretty sure I did, but I ran it again. I noticed several errors which I will have to investigate. Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. I've been working on this for two days now, so the parameters have changed a bit. But here's an example of what prompted my question: This is the result of portmaster -ad === All (18) === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Install textproc/docproj Install print/ghostscript9 Upgrade pkgconf-0.9.5 to pkgconf-0.9.6 Upgrade lcms2-2.6_1 to lcms2-2.6_2 Install textproc/docbook-xml Install textproc/docbook-sgml Install www/mod_authnz_external22 === Proceed? y/n [y] n This is the result of pkg upgrade -n # pkg upgrade -n Updating repository catalogue Upgrades have been requested for the following 150 packages: Installing xf86vidmodeproto: 2.3.1 Installing damageproto: 1.2.1 Installing dri2proto: 2.8 Installing pciids: 20140526 Installing randrproto: 1.4.0 Installing perl5: 5.16.3_10 Installing db48: 4.8.30.0 Reinstalling autoconf-2.69 (direct dependency changed) Reinstalling automake-1.14 (direct dependency changed) Reinstalling bootstrap-openjdk-r351880 (needed shared library changed) Reinstalling curl-7.37.0 (options changed) Reinstalling dejavu-2.34_3 (options changed) Upgrading en-freebsd-doc: 43251,1 - 44807,1 Reinstalling gettext-0.18.3.1_1 (options changed) Reinstalling igor-1.431 (direct dependency changed) Reinstalling ja-font-ipa-00303_1 (direct dependency changed) Reinstalling libgcrypt-1.5.3_2 (direct dependency changed) Reinstalling libwmf-nox11-0.2.8.4_11 (direct dependency changed) Reinstalling libxcb-1.10_2 (direct dependency changed) Reinstalling libxslt-1.1.28_3 (direct dependency changed) Reinstalling mcrypt-2.6.8_1 (direct dependency changed) Reinstalling mkfontdir-1.0.7 (direct dependency changed) Reinstalling mysqltuner-1.3.0 (direct dependency changed) Reinstalling neon29-0.29.6_6 (direct dependency changed) Reinstalling p5-Carp-Clan-6.04 (direct dependency changed) Reinstalling p5-Locale-gettext-1.05_3 (direct dependency changed) Reinstalling p5-XML-Parser-2.41_1 (direct dependency changed) Reinstalling p5-type1inst-0.6.1_5 (options changed) Reinstalling perl5.14-5.14.4_7 (options changed) Reinstalling php5-5.4.29 (options changed) Reinstalling php5-bz2-5.4.29 (direct dependency changed) Reinstalling php5-ctype-5.4.29 (direct dependency changed) Reinstalling php5-curl-5.4.29 (direct dependency changed) Reinstalling php5-dom-5.4.29 (direct dependency changed) Reinstalling php5-filter-5.4.29 (direct dependency changed) Reinstalling php5-hash-5.4.29 (direct dependency changed) Reinstalling php5-iconv-5.4.29 (direct dependency changed) Reinstalling php5-json-5.4.29 (direct dependency changed) Reinstalling php5-mbstring-5.4.29 (direct dependency changed) Reinstalling php5-mssql-5.4.29 (direct dependency changed) Reinstalling php5-mysql-5.4.29 (direct dependency changed) Reinstalling php5-openssl-5.4.29 (direct dependency changed) Reinstalling php5-pdo-5.4.29 (direct dependency changed) Reinstalling php5-phar-5.4.29 (direct dependency changed) Reinstalling php5-posix-5.4.29 (direct dependency changed) Reinstalling php5-session-5.4.29 (direct dependency changed) Reinstalling php5-simplexml-5.4.29 (direct dependency changed) Reinstalling php5-tokenizer-5.4.29 (direct dependency changed) Reinstalling php5-xml-5.4.29 (direct dependency changed) Reinstalling php5-xmlreader-5.4.29 (direct dependency changed) Reinstalling php5-xmlrpc-5.4.29 (direct dependency
Re: How are ports built now
On Sun, 8 Jun 2014, Paul Schmehl wrote: Yes, I do have a few ports with none-default options. The problem is, they're critical ports (like apache22). At present, these have to be built from ports. Long-term, there is a plan to have multiple packages for ports with options. ___ 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: How are ports built now
--On June 8, 2014 at 10:32:33 AM -0600 Warren Block wbl...@wonkity.com wrote: On Sun, 8 Jun 2014, Paul Schmehl wrote: Yes, I do have a few ports with none-default options. The problem is, they're critical ports (like apache22). At present, these have to be built from ports. Long-term, there is a plan to have multiple packages for ports with options. It seems like a completely unworkable solution to me. For example, say you have a port with 10 options. Imagine how many different binaries you would have to have to cover every possible combination of selected options. It would take a huge amount of storage Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How are ports built now
--On June 8, 2014 at 6:05:35 PM +0200 olli hauer oha...@gmx.de wrote: On 2014-06-08 17:20, Paul Schmehl wrote: --On June 7, 2014 at 11:16:04 PM +0200 olli hauer oha...@gmx.de wrote: On 2014-06-07 22:40, Paul Schmehl wrote: --On June 7, 2014 at 10:22:41 PM +0200 A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. Thanks. That's good to know. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? I'm pretty sure I did, but I ran it again. I noticed several errors which I will have to investigate. Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. I've been working on this for two days now, so the parameters have changed a bit. But here's an example of what prompted my question: This is the result of portmaster -ad === All (18) === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Install textproc/docproj Install print/ghostscript9 Upgrade pkgconf-0.9.5 to pkgconf-0.9.6 Upgrade lcms2-2.6_1 to lcms2-2.6_2 Install textproc/docbook-xml Install textproc/docbook-sgml Install www/mod_authnz_external22 === Proceed? y/n [y] n This is the result of pkg upgrade -n # pkg upgrade -n Updating repository catalogue Upgrades have been requested for the following 150 packages: Installing xf86vidmodeproto: 2.3.1 Installing damageproto: 1.2.1 Installing dri2proto: 2.8 Installing pciids: 20140526 Installing randrproto: 1.4.0 Installing perl5: 5.16.3_10 Installing db48: 4.8.30.0 On possible issue between `pkg upgrade' and portmaster with an current ports tree is that some of the ports where updated between last wednesday and now. E.g pkgconf and the freebsd docs where updated after the last package build. [removed a bunch of lines] Is it possible that portmaster builds with NO_PORTDOCS or DOCS=off or similar? No. The port mail/pflogsumm has as only OPTIONS_DEFINE=DOCS, but `pkg upgrade' complains about changed options Reinstalling pflogsumm-1.1.5,1 (options changed) DOCS on/off could be a possible explanation for all the '(options changed)' updates. In general I accept the default options, which is to install docs and examples. There are very few cases where I do not do that. Here's what portmaster wants to build now: === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Install textproc/docbook-sgml Install textproc/docbook-xml Install www/mod_authnz_external22 Re-install docproj-2.0_2 Install print/ghostscript9 All of these ports fail to install individually. Unfortunately, I have to have ghostscript because I use ImageMagick for our forum. Otherwise I remove it. It's always been problematic during installs and upgrades. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How are ports built now
On Sat, Jun 7, 2014 at 10:19 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote: Thanks, but no, you misunderstand. I just upgraded to servers to 8.4 and decided to adopt the new pkgng system at the same time. Any time I upgrade the OS, I always rebuild all ports. I've been using portmaster -ad to do that for a while now. Ah, ok. Sorry for the confusion. I'm still using portupgrade, and haven't used portmaster, so I have nothing to add about that. One one of the servers I seem to be in some sort of loop. Every time I run portmaster -ad the same ports come up for install/upgrade. Yet when portmaster completes it says the ports were successfully installed. Run portmaster -ad again, the same list pops up. All I can say is follow this mailing list closely. There seems to be a lot of problems with the ports tree lately, it has made me lose some confidence in the ports tree. Now I only update when I absolutely have to. Good luck! -- Regards, Torfinn Ingolfsen ___ 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: How are ports built now
--On June 8, 2014 at 7:17:01 PM +0200 Torfinn Ingolfsen tin...@gmail.com wrote: On Sat, Jun 7, 2014 at 10:19 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote: Thanks, but no, you misunderstand. I just upgraded to servers to 8.4 and decided to adopt the new pkgng system at the same time. Any time I upgrade the OS, I always rebuild all ports. I've been using portmaster -ad to do that for a while now. Ah, ok. Sorry for the confusion. I'm still using portupgrade, and haven't used portmaster, so I have nothing to add about that. One one of the servers I seem to be in some sort of loop. Every time I run portmaster -ad the same ports come up for install/upgrade. Yet when portmaster completes it says the ports were successfully installed. Run portmaster -ad again, the same list pops up. All I can say is follow this mailing list closely. There seems to be a lot of problems with the ports tree lately, it has made me lose some confidence in the ports tree. Now I only update when I absolutely have to. Me too. Between staging and the change to pkgng, everything is upside down. It seems FreeBSD is headed toward the dependency hell of Linux instead of the smooth running ports system we once had. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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 2 ng conversion
On 2014-05-28 11:30 AM, Jim Ohlstein wrote: Hello, On 5/28/14, 2:13 PM, Jim Pazarena wrote: On a new/fresh install, V10, should a person immediately place WITH_PKGNG=yes in the make.conf ? And then is it not required to run pkg2ng ? Or is it implied? It seems not, but I cannot find documentation in this respect. In my experience it is unnecessary to add WITH_PKGNG=yes in a fresh FreeBSD 10 box, and it is certainly not necessary to run pkg2ng since there are no installed packages. The pkg_* tools are not included in FreeBSD 10 and the pkg(ng) system is the default. this process is a little confusing. do I still need to run portsnap fetch ? Or does this need to be replaced with some other ng style update? ___ 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 2 ng conversion
On Sun, 8 Jun 2014, Jim Pazarena wrote: On 2014-05-28 11:30 AM, Jim Ohlstein wrote: Hello, On 5/28/14, 2:13 PM, Jim Pazarena wrote: On a new/fresh install, V10, should a person immediately place WITH_PKGNG=yes in the make.conf ? And then is it not required to run pkg2ng ? Or is it implied? It seems not, but I cannot find documentation in this respect. In my experience it is unnecessary to add WITH_PKGNG=yes in a fresh FreeBSD 10 box, and it is certainly not necessary to run pkg2ng since there are no installed packages. The pkg_* tools are not included in FreeBSD 10 and the pkg(ng) system is the default. this process is a little confusing. do I still need to run portsnap fetch ? If you build from ports and wish to continue using them, then yes, continue to use portsnap or svn to update the ports tree. Or does this need to be replaced with some other ng style update? No. pkg is just a package manager. It does not replace ports, it just handles packages. Like the old package manager, binary packages can be downloaded and installed rather than ports, but the choice is yours. ___ 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: How are ports built now
On Sun, 8 Jun 2014, Paul Schmehl wrote: --On June 8, 2014 at 10:32:33 AM -0600 Warren Block wbl...@wonkity.com wrote: On Sun, 8 Jun 2014, Paul Schmehl wrote: Yes, I do have a few ports with none-default options. The problem is, they're critical ports (like apache22). At present, these have to be built from ports. Long-term, there is a plan to have multiple packages for ports with options. It seems like a completely unworkable solution to me. For example, say you have a port with 10 options. Imagine how many different binaries you would have to have to cover every possible combination of selected options. It would take a huge amount of storage I can't say how it will work, just pointing out that until variant packages are available, ports with default options that aren't as desired still have to be built locally. ___ 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
Struggling mightily with port updates
I upgraded two systems to 8.4 and ran portmaster -ad to update all ports. Most of it worked fine, but I'm in docbook hell now. I also don't understand this: === All (6) === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Re-install ruby-1.9.3.484_2,1 Install textproc/docbook-xml Install www/mod_authnz_external22 Re-install docproj-2.0_2 Install print/ghostscript9 === Proceed? y/n [y] I just upgraded ruby: === The following actions were performed: Re-installation of ruby-1.9.3.484_2,1 Re-installation of ruby19-bdb-0.6.6_3 Re-installation of ruby19-date2-4.0.19 So why does portmaster want to reinstall it? Is there a way to dump all the docbook stuff? It's a royal PITA. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How are ports built now
Paul Schmehl pschmehl_li...@tx.rr.com writes: Thanks, but no, you misunderstand. I just upgraded to servers to 8.4 and decided to adopt the new pkgng system at the same time. Any time I upgrade the OS, I always rebuild all ports. I've been using portmaster -ad to do that for a while now. Presumably it's a typo that you left out the -f option? Without that, you wouldn't have been rebuilding everything, and surely you would have noticed by now. ___ 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: How are ports built now
--On June 8, 2014 at 2:50:53 PM -0400 Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org wrote: Paul Schmehl pschmehl_li...@tx.rr.com writes: Thanks, but no, you misunderstand. I just upgraded to servers to 8.4 and decided to adopt the new pkgng system at the same time. Any time I upgrade the OS, I always rebuild all ports. I've been using portmaster -ad to do that for a while now. Presumably it's a typo that you left out the -f option? Without that, you wouldn't have been rebuilding everything, and surely you would have noticed by now. Yes, it's a typo. I've been typing -ad for so long now trying to fix the remaining problems that I left that off. I'm about to give up on the whole thing and switch to another OS. This is beyond frustrating. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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 2 ng conversion
On 2014-06-08 10:55 AM, Warren Block wrote: On Sun, 8 Jun 2014, Jim Pazarena wrote: No. pkg is just a package manager. It does not replace ports, it just handles packages. Like the old package manager, binary packages can be downloaded and installed rather than ports, but the choice is yours. Ahh.. therein lies the confusion. I have been compiling ports for many years. However the compilations began nagging about converting pkg2ng. So I investigated, and set the appropriate WITH_PKGNG=yes and ran pkg2ng. But I never use packages. I always compile from ports. So the warning appearing in each and every compile was is very misleading. Unless I am *still* confused !! ___ 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 2 ng conversion
On 08 Jun 2014, at 21:25, Jim Pazarena fpo...@paz.bz wrote: On 2014-06-08 10:55 AM, Warren Block wrote: On Sun, 8 Jun 2014, Jim Pazarena wrote: No. pkg is just a package manager. It does not replace ports, it just handles packages. Like the old package manager, binary packages can be downloaded and installed rather than ports, but the choice is yours. Ahh.. therein lies the confusion. I have been compiling ports for many years. However the compilations began nagging about converting pkg2ng. So I investigated, and set the appropriate WITH_PKGNG=yes and ran pkg2ng. But I never use packages. I always compile from ports. So the warning appearing in each and every compile was is very misleading. Unless I am *still* confused !! Not really. If you build from ports that results in a binary package that is installed using the package manager. Old pkg_* tools won't be supported after September 1st, so this directly affects you, even if you build all ports yourself. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkg 2 ng conversion
On 06/08/2014 02:25 PM, Jim Pazarena wrote: On 2014-06-08 10:55 AM, Warren Block wrote: On Sun, 8 Jun 2014, Jim Pazarena wrote: No. pkg is just a package manager. It does not replace ports, it just handles packages. Like the old package manager, binary packages can be downloaded and installed rather than ports, but the choice is yours. Ahh.. therein lies the confusion. I have been compiling ports for many years. However the compilations began nagging about converting pkg2ng. So I investigated, and set the appropriate WITH_PKGNG=yes and ran pkg2ng. But I never use packages. I always compile from ports. So the warning appearing in each and every compile was is very misleading. Unless I am *still* confused !! I still think you are confused. pkg manages the database that stores which ports/packages are installed on your system. Whether that particular piece of software came from building it using a port, or from downloading a binary package is immaterial. I think part of the confusion comes from the double use of the words package and/or port. When you have, say, xorg-7.7 installed on your system, do you say you have the port xorg installed, or the package xorg installed? Once it is installed it doesn't matter where it came from - port or package. For whatever reason, people tend to call it a package once it is installed, even if it came from a port. For example, when you write pkg info in the new system, or pkg_info in the old system, it reads the database to tell you the list of packages/ports installed. Now pkg_info and pkg assume a very different structure for the database. That is why, if you have installed any ports or packages using the old system, you have to run pkg2ng. It converts the database from one form to the other. And that is why if you are using FreeBSD-9 or an older system, you have to add WITH_PKGNG=yes to make.conf, so that when more ports/packages are installed, it will update the new database and not the old. Why did the change the database structure? The old way had a separate directory for each port/package built. The new way is to use a modern relational database. So one advantage is the the new pkg database is much faster. Maybe there are other advantages too. ___ 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: How are ports built now
On 08/06/2014 17:54, Paul Schmehl wrote: It seems like a completely unworkable solution to me. For example, say you have a port with 10 options. Imagine how many different binaries you would have to have to cover every possible combination of selected options. It would take a huge amount of storage Yes. You're absolutely right -- there is a combinatorial problem with port options. However there are three things that will help: * Sub packages. Many option settings just add some extra files to a or data package. With the plan to create sub packages -- ie. dividing up the files from a single software compilation into more than one binary package -- a significant proportion of that goes away. * The realization that we really don't need to build packages for all different possible combinations of options. Some option sets simply don't work. Others are for features that only a tiny minority of people would ever want. * The ports isn't going away. If you need a special set of options for a particular port, then you will still have the choice of building from source via the ports. Unlike many other packaging systems, the results of doing this will still be completely integrated with the packaging system, and you will be able to mix and match ports you compile yourself with binary packages from the repositories. Hopefully the necessity of adopting the third option can be minimized, although nothing is going to stop you doing that should you simply prefer to do so. Staging is one of the big pieces necessary to make this all work. It also has the interesting side effect that since everything is built as a package it makes it quite natural to build your own package sets and set up a package repository. If you've got more than one FreeBSD system to manage[*], then I can heartily recommend setting up a package building system and package repository. It's like night and day: you build off-line at your leisure in a clean environment with no fuss and no worries if things don't work entirely right first time -- you haven't affected anything of consequence, so you can just fix the problem and try again without downtime on important services. You can install exactly the software you'll be using on a test system and run it though all the QA you could want before deploying it live. The when it comes to doing the actually installation of packages on your live systems it takes only seconds of disruption, and you're done. poudriere(8) + pkg(8) really is the winning combination. Cheers, Matthew [*] Or even if you only have just the one. -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: How are ports built now
[snip snipperdy snip] Olli, was it really necessary to quote all 236 (!) of those lines? AvW -- I'm not completely useless, I can be used as a bad example. pgpQMWtVlnLfC.pgp Description: PGP signature
Re: pkg 2 ng conversion
Jim Pazarena wrote: this process is a little confusing. do I still need to run portsnap fetch ? PKGNG is a packaging system, not a building system. If you need a ports tree (usually for BUILDING ports/packages from source, although there are other reasons occasionally), then yes, you need to do a # portsnap fetch extract or alternatively obtain a ports tree through Git or Subversion. If you don't need a ports tree (for example because you'll only be installing binary packages from a repository and don't need a ports tree for other reasons), there's no need to use Portsnap either. AvW -- I'm not completely useless, I can be used as a bad example. pgpTX5WduDnWU.pgp Description: PGP signature
Re: pkg 2 ng conversion
On Sun, Jun 8, 2014 at 12:59 PM, Montgomery-Smith, Stephen step...@missouri.edu wrote: On 06/08/2014 02:25 PM, Jim Pazarena wrote: On 2014-06-08 10:55 AM, Warren Block wrote: On Sun, 8 Jun 2014, Jim Pazarena wrote: No. pkg is just a package manager. It does not replace ports, it just handles packages. Like the old package manager, binary packages can be downloaded and installed rather than ports, but the choice is yours. Ahh.. therein lies the confusion. I have been compiling ports for many years. However the compilations began nagging about converting pkg2ng. So I investigated, and set the appropriate WITH_PKGNG=yes and ran pkg2ng. But I never use packages. I always compile from ports. So the warning appearing in each and every compile was is very misleading. Unless I am *still* confused !! I still think you are confused. pkg manages the database that stores which ports/packages are installed on your system. Whether that particular piece of software came from building it using a port, or from downloading a binary package is immaterial. I think part of the confusion comes from the double use of the words package and/or port. When you have, say, xorg-7.7 installed on your system, do you say you have the port xorg installed, or the package xorg installed? Once it is installed it doesn't matter where it came from - port or package. For whatever reason, people tend to call it a package once it is installed, even if it came from a port. For example, when you write pkg info in the new system, or pkg_info in the old system, it reads the database to tell you the list of packages/ports installed. Now pkg_info and pkg assume a very different structure for the database. That is why, if you have installed any ports or packages using the old system, you have to run pkg2ng. It converts the database from one form to the other. And that is why if you are using FreeBSD-9 or an older system, you have to add WITH_PKGNG=yes to make.conf, so that when more ports/packages are installed, it will update the new database and not the old. Why did the change the database structure? The old way had a separate directory for each port/package built. The new way is to use a modern relational database. So one advantage is the the new pkg database is much faster. Maybe there are other advantages too. There are many advantages and speed is a minor one. The one that I see as most significant is that the database schema will not allow any port or package to be installed if there is a file that has the same path as an installed one. This was actually a fairly common problem. It was often noticed, perhaps fairly quickly, but often not, and a CONFLICTS was added to the port, but until them, the second port simply overwrote the older file. This seemed to happen most frequently with documentation files. The new database has blocks the installation of the new port until the conflict is resolved. It does not prevent a port from being committed with a conflict, but the conflict will be noted the first time someone tries to install the ports and will them be fixed in one of several ways. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.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
Re: pkg 2 ng conversion
On 08/06/2014 20:59, Montgomery-Smith, Stephen wrote: Why did the change the database structure? The old way had a separate directory for each port/package built. The new way is to use a modern relational database. So one advantage is the the new pkg database is much faster. Maybe there are other advantages too. Yes, absolutely. Speed is one very big reason for switching to sqlite. There are others - reliability. It was depressingly easy to break the old style /var/db/pkg setup. Especially in tracking reverse dependencies: ie. asking what depends on this package? - consistency. The database schema simply makes it impossible to have duplicate versions of the same package in the pkgdb, something that was formerly a frequent problem. - It's a RDBMS with the power of SQL to pull out pretty much whatever information you could want about the packages you have installed. SQL queries are much easier to write than grepping through /var/db/pkg and passing the results through some complicated post-processing pipeline to filter out the useful stuff. Although one word of caution: we do tend to change the database schema quite frequently, and occasionally in quite radical ways. So, by all means feel free to fire up 'pkg shell' and SQL away; just don't make that an essential or even an important part of anything critical to your livelihood. Instead, use the tools like 'pkg query' or 'pkg info' where we aim to provide a consistent API. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
[QAT] 357068: 2x ignored: does not run on i386, while you are running i386, 2x depend (ignored: does not run on i386, while you are running i386 in math/p5-math-int128), 1x depend (??? in graphics/net
Mass-update maintainer from fbsd-po...@opsec.eu - p...@freebsd.org - Build ID: 20140608190600-21045 Job owner: p...@freebsd.org Buildtime: 3 hours Enddate: Sun, 08 Jun 2014 21:58:38 GMT Revision: 357068 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=357068 - Port:databases/p5-DBD-cego 1.2.8 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349790/p5-DBD-cego-1.2.8.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349791/p5-DBD-cego-1.2.8.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349792/p5-DBD-cego-1.2.8.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349793/p5-DBD-cego-1.2.8.log - Port:devel/dragon 1.3.10 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349794/dragon-1.3.10.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349795/dragon-1.3.10.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349796/dragon-1.3.10.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349797/dragon-1.3.10.log - Port:devel/p5-CBOR-XS 1.25 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349798/p5-CBOR-XS-1.25.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349799/p5-CBOR-XS-1.25.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349800/p5-CBOR-XS-1.25.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349801/p5-CBOR-XS-1.25.log - Port:devel/p5-String-Dump 0.09 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349802/p5-String-Dump-0.09.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349803/p5-String-Dump-0.09.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349804/p5-String-Dump-0.09.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349805/p5-String-Dump-0.09.log - Port:devel/soapui 5.0.0 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349806/soapui-5.0.0.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349807/soapui-5.0.0.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349808/soapui-5.0.0.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349809/soapui-5.0.0.log - Port:dns/p5-URBL-Prepare 0.09 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349810/p5-URBL-Prepare-0.09.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~p...@freebsd.org/20140608190600-21045-349811/p5-URBL-Prepare-0.09.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log:
Re: gobject-introspection broken again or something else wrong...?
The confusing thing for me is this:
[01] Saved devel/gobject-introspection wrkdir to:
/build/poudriere_data/wrkdirs/84amd64-default/default/gobject-introspection-1.36.0_2.txz
[01] Finished build of devel/gobject-introspection: Failed: configure
[01] Skipping build of accessibility/atk: Dependent port
devel/gobject-introspection failed
[01] Skipping build of graphics/gdk-pixbuf2: Dependent port
devel/gobject-introspection failed
[01] Skipping build of devel/libgsf: Dependent port
devel/gobject-introspection failed
[01] Skipping build of x11-toolkits/pango: Dependent port
devel/gobject-introspection failed
(nothing else skipped because of devel/gobject-introspection)
now none of the packages (including devel/gobject-introspection itself)
are in my 'to build' list... So why is it even being built? one
assumes some of the skipped are needed to build or run something else...
but that's not skipped, and it builds...
Pointers would be nice...
Michelle
Michelle Sullivan wrote:
Seems every week or two my build servers all fail and it's mostly one of
2 packages
devel/gobject-introspection
dns/bind99
Today its gobject-introspection:
checking for backtrace_symbols... no
checking whether /usr/local/bin/python2.7 version is = 2.5... yes
checking for /usr/local/bin/python2.7 version... 2.7
checking for /usr/local/bin/python2.7 platform... freebsd9
checking for /usr/local/bin/python2.7 script directory...
${prefix}/lib/python2.7/site-packages
checking for /usr/local/bin/python2.7 extension module directory...
${exec_prefix}/lib/python2.7/site-packages
checking for headers required to compile python extensions... not found
configure: error: Python headers not found
=== Script configure failed unexpectedly.
Please run the gnomelogalyzer, available from
http://www.freebsd.org/gnome/gnomelogalyzer.sh;, which will diagnose the
problem and suggest a solution. If - and only if - the gnomelogalyzer cannot
solve the problem, report the build failure to the FreeBSD GNOME team at
gn...@freebsd.org, and attach (a)
/wrkdirs/usr/ports/devel/gobject-introspection/work/gobject-introspection-1.36.0/config.log,
(b) the output of the failed make command, and (c) the gnomelogalyzer
output.
Also, it might be a good idea to provide an overview of all packages
installed
on your system (i.e. an `ls /var/db/pkg`). Put your attachment up on any
website, copy-and-paste into http://freebsd-gnome.pastebin.com, or use
send-pr(1) with the attachment. Try to avoid sending any attachments to the
mailing list (gn...@freebsd.org), because attachments sent to FreeBSD
mailing
lists are usually discarded by the mailing list software.
*** [do-configure] Error code 1
Stop in /usr/ports/devel/gobject-introspection.
=== Cleaning for gobject-introspection-1.36.0_2
build of /usr/ports/devel/gobject-introspection ended at Sat Jun 7
15:53:19 CEST 2014
build time: 00:00:00
Clues?
Thanks,
--
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
octave update
-B/usr/local/bin -pthread -Wl,-soname -Wl,__voronoi__.so -o dldfcn/.libs/__voronoi__.so c++: warning: argument unused during compilation: '-pthread' c++: warning: argument unused during compilation: '-pthread' sed: /usr/local/lib/liblcms2.la: No such file or directory libtool: link: `/usr/local/lib/liblcms2.la' is not a valid libtool archive gmake[5]: *** [dldfcn/__magick_read__.la] Error 1 gmake[5]: *** Waiting for unfinished jobs libtool: link: c++ -fPIC -DPIC -shared -nostdlib /usr/lib/crti.o /usr/lib/crtbeginS.o dldfcn/.libs/dldfcn_amd_la-amd.o -Wl,-rpath - Wl,/usr/ports/math/octave/work/octave-3.8.1/libinterp/.libs -Wl,-rpath - Wl,/usr/ports/math/octave/work/octave-3.8.1/liboctave/.libs -Wl,-rpath - Wl,/usr/local/lib/octave/3.8.1 -L/usr/local/lib -L/usr/local/lib/gcc47 ./.libs/liboctinterp.so ../liboctave/.libs/liboctave.so -lumfpack - lsuitesparseconfig -lcholmod -lalapack -lptcblas -lamd -lcamd -lcolamd - lccolamd -lcxsparse -lutil -L/usr/lib -lc++ -lm -lpthread -lc -lgcc -lgcc_s /usr/lib/crtendS.o /usr/lib/crtn.o -O2 -pthread -Wl,- rpath=/usr/local/lib/gcc47 -B/usr/local/bin -Wl,-rpath=/usr/local/lib/gcc47 - B/usr/local/bin -pthread -Wl,-soname -Wl,amd.so -o dldfcn/.libs/amd.so c++: warning: argument unused during compilation: '-pthread' c++: warning: argument unused during compilation: '-pthread' libtool: link: c++ -fPIC -DPIC -shared -nostdlib /usr/lib/crti.o /usr/lib/crtbeginS.o dldfcn/.libs/dldfcn_ccolamd_la-ccolamd.o -Wl,-rpath - Wl,/usr/ports/math/octave/work/octave-3.8.1/libinterp/.libs -Wl,-rpath - Wl,/usr/ports/math/octave/work/octave-3.8.1/liboctave/.libs -Wl,-rpath - Wl,/usr/local/lib/octave/3.8.1 -L/usr/local/lib -L/usr/local/lib/gcc47 ./.libs/liboctinterp.so ../liboctave/.libs/liboctave.so -lumfpack - lsuitesparseconfig -lcholmod -lalapack -lptcblas -lamd -lcamd -lcolamd - lccolamd -lcxsparse -lutil -L/usr/lib -lc++ -lm -lpthread -lc -lgcc -lgcc_s /usr/lib/crtendS.o /usr/lib/crtn.o -O2 -pthread -Wl,- rpath=/usr/local/lib/gcc47 -B/usr/local/bin -Wl,-rpath=/usr/local/lib/gcc47 - B/usr/local/bin -pthread -Wl,-soname -Wl,ccolamd.so -o dldfcn/.libs/ccolamd.so c++: warning: argument unused during compilation: '-pthread' c++: warning: argument unused during compilation: '-pthread' libtool: link: c++ -fPIC -DPIC -shared -nostdlib /usr/lib/crti.o /usr/lib/crtbeginS.o dldfcn/.libs/dldfcn_chol_la-chol.o -Wl,-rpath - Wl,/usr/ports/math/octave/work/octave-3.8.1/libinterp/.libs -Wl,-rpath - Wl,/usr/ports/math/octave/work/octave-3.8.1/liboctave/.libs -Wl,-rpath - Wl,/usr/local/lib/octave/3.8.1 -L/usr/local/lib -L/usr/local/lib/gcc47 ./.libs/liboctinterp.so ../liboctave/.libs/liboctave.so -lumfpack - lsuitesparseconfig -lcholmod -lalapack -lptcblas -lamd -lcamd -lcolamd - lccolamd -lcxsparse -lutil -L/usr/lib -lc++ -lm -lpthread -lc -lgcc -lgcc_s /usr/lib/crtendS.o /usr/lib/crtn.o -O2 -pthread -Wl,- rpath=/usr/local/lib/gcc47 -B/usr/local/bin -Wl,-rpath=/usr/local/lib/gcc47 - B/usr/local/bin -pthread -Wl,-soname -Wl,chol.so -o dldfcn/.libs/chol.so c++: warning: argument unused during compilation: '-pthread' c++: warning: argument unused during compilation: '-pthread' Hi! My system: FreeBSD 10.0-RELEASE-p5 #0: Tue Jun 3 13:14:57 UTC 2014 root@amd64- builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 After last update of Octave it doesn't build anymore: libtool: link: ( cd dldfcn/.libs rm -f __fltk_uigetfile__.la ln -s ../__fltk_uigetfile__.la __fltk_uigetfile__.la ) libtool: link: c++ -fPIC -DPIC -shared -nostdlib /usr/lib/crti.o /usr/lib/crtbeginS.o dldfcn/.libs/dldfcn_colamd_la-colamd.o -Wl,-rpath - Wl,/usr/ports/math/octave/work/octave-3.8.1/libinterp/.libs -Wl,-rpath - Wl,/usr/ports/math/octave/work/octave-3.8.1/liboctave/.libs -Wl,-rpath - Wl,/usr/local/lib/octave/3.8.1 -L/usr/local/lib -L/usr/local/lib/gcc47 ./.libs/liboctinterp.so ../liboctave/.libs/liboctave.so -lumfpack - lsuitesparseconfig -lcholmod -lalapack -lptcblas -lamd -lcamd -lcolamd - lccolamd -lcxsparse -lutil -L/usr/lib -lc++ -lm -lpthread -lc -lgcc -lgcc_s /usr/lib/crtendS.o /usr/lib/crtn.o -O2 -pthread -Wl,- rpath=/usr/local/lib/gcc47 -B/usr/local/bin -Wl,-rpath=/usr/local/lib/gcc47 - B/usr/local/bin -pthread -Wl,-soname -Wl,colamd.so -o dldfcn/.libs/colamd.so c++: warning: argument unused during compilation: '-pthread' c++: warning: argument unused during compilation: '-pthread' libtool: link: ( cd dldfcn/.libs rm -f __init_fltk__.la ln -s ../__init_fltk__.la __init_fltk__.la ) libtool: link: ( cd dldfcn/.libs rm -f ccolamd.la ln -s ../ccolamd.la ccolamd.la ) libtool: link: ( cd dldfcn/.libs rm -f chol.la ln -s ../chol.la chol.la ) libtool: link: ( cd dldfcn/.libs rm -f colamd.la ln -s ../colamd.la colamd.la ) libtool: link: ( cd dldfcn/.libs rm -f __voronoi__.la ln -s ../__voronoi__.la __voronoi__.la ) libtool: link: ( cd dldfcn/.libs rm -f amd.la ln -s ../amd.la amd.la ) gmake[5]: Leaving directory
Re: Struggling mightily with port updates
On Sun, 8 Jun 2014, Paul Schmehl wrote: I upgraded two systems to 8.4 and ran portmaster -ad to update all ports. Most of it worked fine, but I'm in docbook hell now. I also don't understand this: === All (6) === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Re-install ruby-1.9.3.484_2,1 Install textproc/docbook-xml Install www/mod_authnz_external22 Re-install docproj-2.0_2 Install print/ghostscript9 === Proceed? y/n [y] I just upgraded ruby: === The following actions were performed: Re-installation of ruby-1.9.3.484_2,1 Re-installation of ruby19-bdb-0.6.6_3 Re-installation of ruby19-date2-4.0.19 So why does portmaster want to reinstall it? /usr/ports/UPDATING shows manual steps that must be taken. The 20140219 entry talks about the DocBook ports. ___ 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: Struggling mightily with port updates
--On June 8, 2014 at 6:38:48 PM -0600 Warren Block wbl...@wonkity.com wrote: On Sun, 8 Jun 2014, Paul Schmehl wrote: I upgraded two systems to 8.4 and ran portmaster -ad to update all ports. Most of it worked fine, but I'm in docbook hell now. I also don't understand this: === All (6) === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Re-install ruby-1.9.3.484_2,1 Install textproc/docbook-xml Install www/mod_authnz_external22 Re-install docproj-2.0_2 Install print/ghostscript9 === Proceed? y/n [y] I just upgraded ruby: === The following actions were performed: Re-installation of ruby-1.9.3.484_2,1 Re-installation of ruby19-bdb-0.6.6_3 Re-installation of ruby19-date2-4.0.19 So why does portmaster want to reinstall it? /usr/ports/UPDATING shows manual steps that must be taken. The 20140219 entry talks about the DocBook ports. I read that, but the uninstalls failed. I ended up having to run down the dependency rabbit hole, uninstalling ports one at a time until the one depending upon them were all gone. It's working now. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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 2 ng conversion
On Sun, 8 Jun 2014, Jim Pazarena wrote: On 2014-06-08 10:55 AM, Warren Block wrote: On Sun, 8 Jun 2014, Jim Pazarena wrote: No. pkg is just a package manager. It does not replace ports, it just handles packages. Like the old package manager, binary packages can be downloaded and installed rather than ports, but the choice is yours. Ahh.. therein lies the confusion. I have been compiling ports for many years. However the compilations began nagging about converting pkg2ng. So I investigated, and set the appropriate WITH_PKGNG=yes and ran pkg2ng. But I never use packages. I always compile from ports. So the warning appearing in each and every compile was is very misleading. Unless I am *still* confused !! The package database tracks what is installed, whether it was built from a port or downloaded as a binary package. The old package database is going away, and it's time to switch. That's what pkg2ng does, reads the old installed packages database and writes the new format. ___ 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
RELEASE_x_y_EOL ports tags [Was: Re: Who was the mental genius]
On 6/5/2014 6:05 PM, Erich Dollansky wrote:
Hi,
On Thu, 05 Jun 2014 15:09:53 -0500
Paul Schmehl pschmehl_li...@tx.rr.com wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system
instead of outright breaking ports? The idiots are apparently
running the asylum. {{sigh}}
this is the reason why I am asking for versions on the ports tree since
a decade. Ok, we have the revision now. Just go back in the revision
until it works. It is a good practice to make a note of the revision of
the running ports tree you have before updating it.
We do have that. We have RELEASE_X_EOL tags that identify the last
known-good ports tree for a given major branch. Unfortunately, this
time the break happened in the middle of the 8.x lifespan, so there is
no handy EOL tag.
Perhaps a RELEASE_x_y_EOL tag would be a useful thing to add whenever
there is a break like this? It certainly would be an easier mnemonic to
say check out the RELEASE_8_3_EOL tag instead of check out R112358.
Hell, the prior's even self-documenting if someone happened to stumble
across http://svnweb.freebsd.org/ports/tags/.
We already have tags going back through 20 years of releases (just in
case you want a ports tree that works with release 2.0.5) and an
established policy of tagging for last known good at the major level.
I don't think a few more tags are going to hurt if it saves someone
the hassle of dancing up to the line of an API/ABI break.
___
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
