[QAT] 363960: 4x depend (ignored: you must fetch the distribution manually. please access http://labs.adobe.com/technologies/flex/sdk/flex2sdk.html with a web browser. please place the downloaded flex
In some straightforward cases, protect documentation behind PORTDOCS, adding a DOCS option where needed, and a couple PORTEXAMPLES for good measure. - Build ID: 20140804034200-35179 Job owner: ad...@freebsd.org Buildtime: 5 hours Enddate: Mon, 04 Aug 2014 08:48:43 GMT Revision: 363960 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=363960 - Port:cad/geda-utils 1.4.3_4,1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391498/geda-utils-1.4.3_4,1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391499/geda-utils-1.4.3_4,1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391500/geda-utils-1.4.3_4,1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391501/geda-utils-1.4.3_4,1.log - Port:databases/libdbi-drivers 0.9.0_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391502/libdbi-drivers-0.9.0_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391503/libdbi-drivers-0.9.0_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391504/libdbi-drivers-0.9.0_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391505/libdbi-drivers-0.9.0_2.log - Port:databases/sqldeveloper 4.0.1.14.48 Buildgroup: 8.4-QAT/amd64 Buildstatus: IGNORED: DUE TO ORACLE LICENSE RESTRICTIONS, YOU MUST FETCH THE SOURCE DISTRIBUTION MANUALLY. PLEASE ACCESS HTTP://WWW.ORACLE.COM/TECHNOLOGY/SOFTWARE/PRODUCTS/SQL/INDEX.HTML WITH A WEB BROWSER AND FOLLOW THE LINK FOR THE SQLDEVELOPER-4.0.1.14.48-NO-JRE Buildgroup: 8.4-QAT/i386 Buildstatus: IGNORED: DUE TO ORACLE LICENSE RESTRICTIONS, YOU MUST FETCH THE SOURCE DISTRIBUTION MANUALLY. PLEASE ACCESS HTTP://WWW.ORACLE.COM/TECHNOLOGY/SOFTWARE/PRODUCTS/SQL/INDEX.HTML WITH A WEB BROWSER AND FOLLOW THE LINK FOR THE SQLDEVELOPER-4.0.1.14.48-NO-JRE Buildgroup: 9.2-QAT/amd64 Buildstatus: IGNORED: DUE TO ORACLE LICENSE RESTRICTIONS, YOU MUST FETCH THE SOURCE DISTRIBUTION MANUALLY. PLEASE ACCESS HTTP://WWW.ORACLE.COM/TECHNOLOGY/SOFTWARE/PRODUCTS/SQL/INDEX.HTML WITH A WEB BROWSER AND FOLLOW THE LINK FOR THE SQLDEVELOPER-4.0.1.14.48-NO-JRE Buildgroup: 9.2-QAT/i386 Buildstatus: IGNORED: DUE TO ORACLE LICENSE RESTRICTIONS, YOU MUST FETCH THE SOURCE DISTRIBUTION MANUALLY. PLEASE ACCESS HTTP://WWW.ORACLE.COM/TECHNOLOGY/SOFTWARE/PRODUCTS/SQL/INDEX.HTML WITH A WEB BROWSER AND FOLLOW THE LINK FOR THE SQLDEVELOPER-4.0.1.14.48-NO-JRE - Port:deskutils/cycle 0.3.1_8 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391510/cycle-0.3.1_8.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391511/cycle-0.3.1_8.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391512/cycle-0.3.1_8.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391513/cycle-0.3.1_8.log - Port:devel/buildtool 0.16 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391514/buildtool-0.16.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391515/buildtool-0.16.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140804034200-35179-391516/buildtool-0.16.log Buildgroup: 9.2-QAT/i386
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ net-mgmt/pandorafms_agent | 4.0.1 | 5.1-140804 +-+ net-mgmt/pandorafms_console | 4.0.1 | 5.1-140804 +-+ net-mgmt/pandorafms_server | 4.0.1 | 5.1-140804 +-+ 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
Re: Does pkg automatically download INDEX?
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 -- and with luck, the offending process might whine or squawk (thus providing you with identification). chflags noschg /usr/ports/INDEX* to undo it. Peace, david This was a really good suggestion. While I wasn't lucky in regards to having a process whine about being unable to write to INDEX-9, I did find that now there is an INDEX-9.bz2 sitting in /usr/ports, which I assume comes from a download of it. I'm going to try setting INDEX-9.bz2 to also have the schg flag on it, maybe that'll make a process complain. If not, at least I can modify my manual INDEX building to remove the schg flag before updated INDEX and then setting it again afterwards. 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
Re: How do maintainer updates work with bugzilla?
On 2014-08-03 22:18, Matthew Seaman wrote: By virtue of sending a PR into the system a le...@ee.lbl.gov account will have been created in Bugzilla. So, 'send-pr' still works? That's good news then, I was under impression that it was disabled after the bugzilla switch. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
www.freebsd.org
Hi, If you want your website to work harder, WE can help you measure your performances, identify areas of weakness, and clear a path to better conversion rates. There's no single reason why visitors to your website fail to become customers. The need is to attract visitor's attention that helps in better interaction. Optimisation does not mean changing the existing layout of your website but these are tools for better visitor engagements. Every non-converting visitor costs you in wasted market-ing efforts and missed sale. Would you be interested in receiving further information a quote for optimising your website with no-strings-attached? Best regards, Jessica Conversion Optimisation Specialist *D*OMOTICS Western Australia, Northern Territory, South Australia, Queensland, New South Wales, Victoria, Australian Capital Territory, Tasmania Disclaimer: We respect your privacy and want to make sure you are aware of a few things. By replying to this email, you authorise our affiliates that can help with your project to contact you at the number you provided, and you understand that they may use automated technology to reach you. At no time are you required to make a purchase. ___ 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 do maintainer updates work with bugzilla?
On 08/04/14 12:09, Vitaly Magerya wrote: On 2014-08-03 22:18, Matthew Seaman wrote: By virtue of sending a PR into the system a le...@ee.lbl.gov account will have been created in Bugzilla. So, 'send-pr' still works? That's good news then, I was under impression that it was disabled after the bugzilla switch. Err... no. I don't believe send-pr does anything useful at the moment. The PR I was talking about above was sent just before the switch to Bugzilla and then imported into Bugzilla as part of the migration. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: WANT_PHP_WEB is just a synonym for WANT_PHP_CGI in automated build environments
Matthew Pounsett ha scritto:
It looks to me like the rules that WANT_PHP_WEB uses to decide whether to
build the CGI or module version of PHP will always choose the CGI version
unless the module is already installed. If this is true, it means that in
automated build environments (e.g. tinderbox) – where *only* the direct
dependencies of a port are installed at build time – there isn’t any way to
tell WANT_PHP_WEB to install the module. This effectively makes WANT_PHP_WEB
a synonym for WANT_PHP_CGI in these environments.
Have I missed something, or is this a significant flaw in the design of the
WANT_PHP_{WEB,CGI,MOD} knobs?
You missed the fact that you can install the php module as a separate
port/package together with the core php package. Not only, mod_php port
requires core php port, that is the one containing the cgi version. So
there isn't any problem with tinderbox/poudriere.
--
Alex Dupre
___
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] 363973: 4x leftovers
- Stop trying to remove directories owned by dependencies - Optimize away USE_GL knob (implied by USE_QT4=opengl) Reported by:QAT - Build ID: 20140804082800-57320 Job owner: da...@freebsd.org Buildtime: 6 hours Enddate: Mon, 04 Aug 2014 14:14:25 GMT Revision: 363973 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=363973 - Port:astro/stellarium-qt4 0.12.4 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~da...@freebsd.org/20140804082800-57320-391686/stellarium-qt4-0.12.4.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~da...@freebsd.org/20140804082800-57320-391687/stellarium-qt4-0.12.4.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~da...@freebsd.org/20140804082800-57320-391688/stellarium-qt4-0.12.4.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~da...@freebsd.org/20140804082800-57320-391689/stellarium-qt4-0.12.4.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140804082800-57320 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: recommended linux port?
Am 04.08.2014 um 05:22 schrieb Steve Kargl: portmaster print/acroread9 ends with ===Verifying install for /compat/linux/lib/libexpat.so.1 in /usr/ports/textproc/linux-f10-expat === linux-f10-expat-2.0.1 is forbidden: http://www.freshports.org/vuxml.php?vid=5f030587-e39a-11de-881e-001aa0166822. *** Error code 1 Stop. make[2]: stopped in /usr/ports/textproc/linux-f10-expat *** Error code 1 Stop. make[1]: stopped in /usr/ports/graphics/linux-f10-cairo *** Error code 1 So, what is the recommended linux port? Johannes Meixner has done some work on moving Linux to a CentOS base, but that has not landed in the official ports tree yet. At any rate, that's beside the point in your particular case; we should forbid and expire acroread9 instead because it's no longer maintained. ___ 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] 363978: 30x leftovers, 2x depend (forbidden: http://www.freshports.org/vuxml.php?vid=77bb0541-c1aa-11e3-a5ac-001b21614864 in devel/linux-f10-dbus-glib), 1x threads, 1x depend (threads in www/fir
Update mozilla ports: - firefox 31.0 - firefox-esr 24.7.0 - libxul 24.7.0 - seamonkey 2.26.1 - thunderbird 31.0 Among changes: - add workaround for crash with openldap on thunderbird and seamonkey [1] - add crashfix for architectures with strict alignmentment - backport crashfix with system sqlite/nss on firefox-esr and thunderbird - restore hooking jemalloc in sqlite on freebsd 10+ - fix thunderbird build with -jN [2] - respect MAKE_JOBS_NUMBER regardless of kern.smp.cpus [2] - define CPE_URI for nspr/nss and firefox/thunderbird/seamonkey - require recent gstreamer1-libav i386 crashfix - add DTRACE option for use with DTraceToolkit (js_flowtime.d, js_who.d, etc) PR: 165263 [1] PR: 184630 [2] Submitted by: Jan Beich - Build ID: 20140804091200-39434 Job owner: b...@freebsd.org Buildtime: 8 hours Enddate: Mon, 04 Aug 2014 16:53:51 GMT Revision: 363978 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=363978 - Port:mail/linux-thunderbird 31.0 Buildgroup: 8.4-QAT/amd64 Buildstatus: DEPEND (FORBIDDEN: HTTP://WWW.FRESHPORTS.ORG/VUXML.PHP?VID=262B92FE-81C8-11E1-8899-001EC9578670 IN GRAPHICS/LINUX-F10-PNG) Buildgroup: 8.4-QAT/i386 Buildstatus: DEPEND (FORBIDDEN: HTTP://WWW.FRESHPORTS.ORG/VUXML.PHP?VID=262B92FE-81C8-11E1-8899-001EC9578670 IN GRAPHICS/LINUX-F10-PNG) Buildgroup: 9.2-QAT/amd64 Buildstatus: DEPEND (FORBIDDEN: HTTP://WWW.FRESHPORTS.ORG/VUXML.PHP?VID=262B92FE-81C8-11E1-8899-001EC9578670 IN GRAPHICS/LINUX-F10-PNG) Buildgroup: 9.2-QAT/i386 Buildstatus: DEPEND (FORBIDDEN: HTTP://WWW.FRESHPORTS.ORG/VUXML.PHP?VID=262B92FE-81C8-11E1-8899-001EC9578670 IN GRAPHICS/LINUX-F10-PNG) - Port:mail/thunderbird 31.0 Buildgroup: 8.4-QAT/amd64 Buildstatus: THREADS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391714/thunderbird-31.0.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391715/thunderbird-31.0.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391716/thunderbird-31.0.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391717/thunderbird-31.0.log - Port:mail/thunderbird-i18n 31.0 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391718/thunderbird-i18n-31.0.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391719/thunderbird-i18n-31.0.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391720/thunderbird-i18n-31.0.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391721/thunderbird-i18n-31.0.log - Port:www/firefox 31.0,1 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391722/firefox-31.0,1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391723/firefox-31.0,1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391724/firefox-31.0,1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391725/firefox-31.0,1.log - Port:www/firefox-esr 24.7.0,1 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391726/firefox-esr-24.7.0,1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140804091200-39434-391727/firefox-esr-24.7.0,1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log:
Re: How do maintainer updates work with bugzilla?
On Mon, 04 Aug 2014 12:44:12 +0100, Matthew Seaman stated: Err... no. I don't believe send-pr does anything useful at the moment. So, exactly what does a send-pr do now exactly? If it does nothing, there should have been some public notice of it AND have been removed from the system. -- Jerry signature.asc Description: PGP signature
pkg: cached package size mismatch, cannot continue
Hi, I install pkg-1.3.4 on my system. I did this: pkg clean -a (I verified that /var/cache/pkg was empty) # pkg install automake Updating repository catalogue FreeBSD repository is up-to-date All repositories are up-to-date The following 2 packages will be affected (of 135 checked): New packages to be INSTALLED: automake: 1.14 automake-wrapper: 20131203 The process will require 2 MB more space 434 KB to be downloaded Proceed with this action [y/N]: y Fetching automake-1.14.txz: 100% of 431 KB pkg: cached package automake-1.14: size mismatch, fetching from remote Fetching automake-1.14.txz: 100% of 431 KB pkg: cached package automake-1.14: size mismatch, cannot continue This seems to be happening for any package that I try to install. Any idea what the problem might be? -- Craig ___ 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: cached package size mismatch, cannot continue
On 04 Aug 2014, at 20:32, Craig Rodrigues rodr...@freebsd.org wrote: Hi, I install pkg-1.3.4 on my system. I did this: pkg clean -a (I verified that /var/cache/pkg was empty) # pkg install automake Updating repository catalogue FreeBSD repository is up-to-date All repositories are up-to-date The following 2 packages will be affected (of 135 checked): New packages to be INSTALLED: automake: 1.14 automake-wrapper: 20131203 The process will require 2 MB more space 434 KB to be downloaded Proceed with this action [y/N]: y Fetching automake-1.14.txz: 100% of 431 KB pkg: cached package automake-1.14: size mismatch, fetching from remote Fetching automake-1.14.txz: 100% of 431 KB pkg: cached package automake-1.14: size mismatch, cannot continue This seems to be happening for any package that I try to install. Any idea what the problem might be? Try pkg update -f -- Craig ___ 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: cached package size mismatch, cannot continue
On Mon, Aug 04, 2014 at 11:32:55AM -0700, Craig Rodrigues wrote: Hi, I install pkg-1.3.4 on my system. I did this: pkg clean -a (I verified that /var/cache/pkg was empty) # pkg install automake Updating repository catalogue FreeBSD repository is up-to-date All repositories are up-to-date The following 2 packages will be affected (of 135 checked): New packages to be INSTALLED: automake: 1.14 automake-wrapper: 20131203 The process will require 2 MB more space 434 KB to be downloaded Proceed with this action [y/N]: y Fetching automake-1.14.txz: 100% of 431 KB pkg: cached package automake-1.14: size mismatch, fetching from remote Fetching automake-1.14.txz: 100% of 431 KB pkg: cached package automake-1.14: size mismatch, cannot continue This seems to be happening for any package that I try to install. Any idea what the problem might be? -- Craig Rename /var/db/pkg/repo* (all of them) and try again. ___ 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: WANT_PHP_WEB is just a synonym for WANT_PHP_CGI in automated build environments
On Aug 4, 2014, at 09:05 , Alex Dupre a...@freebsd.org wrote:
Matthew Pounsett ha scritto:
It looks to me like the rules that WANT_PHP_WEB uses to decide whether to
build the CGI or module version of PHP will always choose the CGI version
unless the module is already installed. If this is true, it means that in
automated build environments (e.g. tinderbox) – where *only* the direct
dependencies of a port are installed at build time – there isn’t any way to
tell WANT_PHP_WEB to install the module. This effectively makes
WANT_PHP_WEB a synonym for WANT_PHP_CGI in these environments.
Have I missed something, or is this a significant flaw in the design of the
WANT_PHP_{WEB,CGI,MOD} knobs?
You missed the fact that you can install the php module as a separate
port/package together with the core php package. Not only, mod_php port
requires core php port, that is the one containing the cgi version. So
there isn't any problem with tinderbox/poudriere.
I can build it, sure .. but it’s the dependencies I’m trying to get fixed up.
If I can’t tell the ports tree that a WANT_PHP_WEB port should require
mod_php5, then when I go to install the package that gets built for that port
it’s not going to have the requirement in its meta data, and mod_php5 won’t be
installed as a result.
Yes, I can then also go manually install mod_php5, but that’s not really the
point of dependencies, is it?
___
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: WANT_PHP_WEB is just a synonym for WANT_PHP_CGI in automated build environments
On Aug 3, 2014, at 12:29 , Melvyn Sopacua mel...@magemana.nl wrote:
Hi Matthew,
On Sun, 3 Aug 2014, Matthew Pounsett wrote:
On Aug 3, 2014, at 02:07 , Melvyn Sopacua mel...@magemana.nl wrote:
For automated builds use the OPTIONS framework. Tinderbox can handle
that just fine.
Right, and I’m speaking from the perspective of the admin building the
port, not the maintainer. The maintainer can set that the port will
work with either .. but in an automated build environment it looks
like there is no knob for the administrator to tell the ports system
which to use.
Unless that changed in recent years, you can have Tinderbox mount your
options database in /var/db/ports into the build jail. So you can do one
configure run and set it.
Do one configure run to set what? The whole point of this thread is that there
is no configure option to tell a port that uses WANT_PHP_WEB to require
mod_php5.
Besides which, tinderbox has one options database per build. It doesn’t use
the options database in /var/db/ports.
A second possibility is to simply add www/mod_php5 to ports to be built,
since it's no longer part of lang/php5. This won't work for the
upstream-abandoned php 5.3.
A third is to set php53_SET=APACHE in /etc/make.conf.
Manually telling the system to build a package will get it built, but doesn’t
solve the dependency problem. The whole point of dependencies is that when you
install a port/package the things it requires will also get installed .. if a
port that uses WANT_PHP_WEB can’t be told to require mod_php5, then the
dependency doesn’t exist. Again, we’re back to WANT_PHP_WEB being a synonym
for WANT_PHP_CGI.
Your other suggestion seems to be that in order to get the php module to be a
dependency of some other port I need to use an old version of php.. I’m not
sure how seriously I should take that.
Again.. unless I’m missing some knob that exists to give guidance to
the ports system. I’m familiar with the options framework, but I
can’t find anything in bsd.php.mk that could be used to give guidance
to the ports system that mod_php5 is desired when WANT_PHP_WEB is
defined.
WANT_PHP_WEB actually pulls in the apache module if php is installed
only with the CLI or EMBED backend. See this bit:
if defined(WANT_PHP_MOD) || (defined(WANT_PHP_WEB) defined(PHP_VERSION)
${PHP_SAPI:Mcgi} == ${PHP_SAPI:Mfpm} == )
USE_APACHE_RUN= 22+
.include ${PORTSDIR}/Mk/bsd.apache.mk
RUN_DEPENDS+=
${PHPBASE}/${APACHEMODDIR}/libphp5.so:${PORTSDIR}/${MOD_PHP_PORT}
.endif
That’s not how I read that. I’ve read this piece of code and it’s how I
arrived at the conclusion that WANT_PHP_WEB is a synonym for WANT_PHP_CGI in
automated build environments. The above code seems to say that libphp5.so
should only be set if WANT_PHP_MOD is set, OR if WANT_PHP_WEB is set AND PHP is
installed AND the CGI and FPM options for the CGI module are unset.
As far as I can tell, the only way you get an installed version of PHP without
either the CGI or FPM options set is to install mod_php5. That makes
installing mod_php5 a prerequisite to making mod_php5 a dependency to any port
that uses WANT_PHP_WEB.
___
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 Sun, 03 Aug 2014 16:27:36 -0400 Naram Qashat cyberb...@cyberbotx.com wrote: On 08/03/14 15:53, Matthew Seaman wrote: On 03/08/2014 20:34, Naram Qashat wrote: Well, I've been using the command line arguments of -voL '=', and looking at the man page for pkg-version, as far as I can tell, it shouldn't be downloading INDEX, since I do have INDEX-9 on my system. pkg(8) doesn't download or attempt to build an INDEX at all. It can use one if one happens to be already available, but not otherwise. Cheers, Matthew I'm at a bit of a loss, then. While I can't say for sure if pkg is doing something unintended, there seems to be something on my system that is downloading INDEX without my knowledge. My usual way of updating my INDEX is using p5-FreeBSD-Portindex to generate the INDEX file, and using that INDEX to update the files that portupgrade uses. I run that manually, so I have nothing that would do that for me automatically, to my knowledge. How do you update the ports tree, with portsnap or with svn? Portnap also updates the index. Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0xC773696B3BAC17DC http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0xC773696B3BAC17DC ___ 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: cached package size mismatch, cannot continue
On Mon, Aug 4, 2014 at 11:39 AM, Michael Gmelin gre...@freebsd.org wrote: On 04 Aug 2014, at 20:32, Craig Rodrigues rodr...@freebsd.org wrote: Fetching automake-1.14.txz: 100% of 431 KB pkg: cached package automake-1.14: size mismatch, fetching from remote Fetching automake-1.14.txz: 100% of 431 KB pkg: cached package automake-1.14: size mismatch, cannot continue This seems to be happening for any package that I try to install. Any idea what the problem might be? Try pkg update -f Hi, That worked. Thanks! I'm not sure what would have caused this problem. This is a relatively new machine which I set up last week, and installed a bunch of packages via pkg install. The only thing I did different today was that I built and installed a few packages via ports under /usr/ports (updated with portsnap). -- Craig ___ 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: cached package size mismatch, cannot continue
On 04 Aug 2014, at 23:10, Craig Rodrigues rodr...@freebsd.org wrote: On Mon, Aug 4, 2014 at 11:39 AM, Michael Gmelin gre...@freebsd.org wrote: On 04 Aug 2014, at 20:32, Craig Rodrigues rodr...@freebsd.org wrote: Fetching automake-1.14.txz: 100% of 431 KB pkg: cached package automake-1.14: size mismatch, fetching from remote Fetching automake-1.14.txz: 100% of 431 KB pkg: cached package automake-1.14: size mismatch, cannot continue This seems to be happening for any package that I try to install. Any idea what the problem might be? Try pkg update -f Hi, That worked. Thanks! I'm not sure what would have caused this problem. This is a relatively new machine which I set up last week, and installed a bunch of packages via pkg install. The only thing I did different today was that I built and installed a few packages via ports under /usr/ports (updated with portsnap). Happened to me as well under 1.3.4 (my own repo). I didn't have time to look into it yet, but it happened after a package in the repo had been rebuilt (same version number, updated dependencies), so it might be a pkg bug. -- Craig ___ 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: cached package size mismatch, cannot continue
On Mon, Aug 04, 2014 at 02:10:54PM -0700, Craig Rodrigues wrote: On Mon, Aug 4, 2014 at 11:39 AM, Michael Gmelin gre...@freebsd.org wrote: On 04 Aug 2014, at 20:32, Craig Rodrigues rodr...@freebsd.org wrote: Fetching automake-1.14.txz: 100% of 431 KB pkg: cached package automake-1.14: size mismatch, fetching from remote Fetching automake-1.14.txz: 100% of 431 KB pkg: cached package automake-1.14: size mismatch, cannot continue This seems to be happening for any package that I try to install. Any idea what the problem might be? Try pkg update -f Hi, That worked. Thanks! I'm not sure what would have caused this problem. This is a relatively new machine which I set up last week, and installed a bunch of packages via pkg install. The only thing I did different today was that I built and installed a few packages via ports under /usr/ports (updated with portsnap). The problem is fixed in master it will be in 1.3.5, planned in around 20h regards, Bapt pgp_XqInDtNlM.pgp Description: PGP signature
curious issues with pkg-1.3.4's 'pkg upgrade -f' feature
I am trying to do a 'pkg upgrade -f' from a local mirror (built using tinderbox): FreeBSD eta.jnpr.net 10.0-RELEASE-p6 FreeBSD 10.0-RELEASE-p6 #4 r267837M: Tue Jun 24 13:53:48 PDT 2014 r...@eta.jnpr.net:/usr/obj/usr/src/sys/GENERIC amd64 $ sudo pkg upgrade -f Updating repository catalogue pkg: http://norse/tb/packages/freebsd:10:x86:64/meta.txz: Not Found pkg: repository cs01 has no meta file, using default settings cs01 repository is up-to-date All repositories are up-to-date Updating database digests format: 100% Checking for upgrades: 100% pkg: cannot resolve conflict between remote p5-Test-Unit(want install), local p5-Test-Unit(want keep), please resolve it manually pkg: SAT: conflicting request, cannot solve pkg: cannot solve job using SAT solver Any clue what may be going on? Set of currently installed packages is attached. GeoIP-1.6.0Find the country that any IP address or hostname originates from ORBit2-2.14.19_1 High-performance CORBA ORB with support for the C language OpenEXR-2.1.0_3High dynamic-range (HDR) image file format OpenSSH-askpass-1.2.4.1_2 Graphical password applet for entering SSH passphrase aalib-1.4.r5_10ASCII art library adns-1.4_1 Easy to use asynchronous-capable DNS client library and utilities alsa-lib-1.0.27.2_2ALSA compatibility library alsa-plugins-1.0.27_2 ALSA compatibility library plugins antiword-0.37_2An application for displaying Microsoft(R) Word documents apache-ant-1.9.4 Java- and XML-based build tool, conceptually similar to make apr-1.5.1.1.5.3_3 Apache Portability Library argp-standalone-1.3_2 Standalone version of arguments parsing functions from GLIBC asciidoc-8.6.9_3 Text document format for writing short documents and man pages aspell-0.60.6.1_5 Spelling checker with better suggestion logic than ispell at-spi2-atk-2.8.0 Assisted Technology Provider module for GTK+ at-spi2-core-2.8.0 Assistive Technology Service Provider Interface aterm-1.0.1_6 Color vt102 terminal emulator with transparency support atk-2.8.0 GNOME accessibility toolkit (ATK) attica-0.4.2,2 Open Collaboration Services API library autoconf-2.69 Automatically configure source code on many Un*x platforms autoconf-wrapper-20131203 Wrapper script for GNU autoconf autoconf213-2.13.000227_6 Automatically configure source code on many Un*x platforms (legacy 2.13) automake-1.14 GNU Standards-compliant Makefile generator automake-wrapper-20131203 Wrapper script for GNU automake automake14-1.4.6_6 GNU Standards-compliant Makefile generator (legacy 1.4) automoc4-0.9.88_3 Automatic moc for Qt 4 packages bash-4.3.22The GNU Project's Bourne Again SHell bcrypt-1.1 Cross-platform blowfish encryption utility bdftopcf-1.0.4 Convert X font from BDF to PCF bigreqsproto-1.1.2 BigReqs extension headers bind99-9.9.5P1_5 BIND DNS suite with updated DNSSEC and DNS64 binutils-2.24 GNU binary tools bison-2.7.1,1 Parser generator from FSF, (mostly) compatible with Yacc bitcoin-0.9.2 Virtual Peer-to-Peer Currency Client bitlbee-3.2.2_2IRC to other chat networks gateway bonnie++-1.97_3Performance Test of Filesystem I/O boost-jam-1.55.0 Build tool from the boost.org boost-libs-1.55.0_3Free portable C++ libraries (without Boost.Python) bootstrap-openjdk-r351880 Oracle's Java 6 virtual machine release under the GPL v2 ca_root_nss-3.16.3 The root certificate bundle from the Mozilla Project cabextract-1.4 Program to extract Microsoft cabinet (.CAB) files cairo-1.10.2_10,2 Vector graphics library with cross-device output support ccid-1.4.17Generic USB CCID (Chip/Smart Card Interface Devices) driver cdparanoia-3.9.8_9 CDDA extraction tool (also known as ripper) cdrtools-3.00_2CD/DVD/BluRay and ISO-9660 image creation and extraction tools celt-0.11.3_2 The CELT ultra-low delay audio codec clearlooks-themes-0.6.2_12 Clearlooks themes with the engine coming from gtk-engines2 clucene-2.3.3.4_4 CLucene is a C++ port of Lucene cmake-2.8.12.1_4 Cross-platform Makefile generator cmake-modules-2.8.12.1_1 Modules and Templates for CMake cmatrix-1.2a_1 Show a scrolling 'Matrix' like screen colord-1.0.1_2 Manage color profiles to accurately color input/output devices compat6x-amd64-6.4.604000.200810_3 Convenience package to install the compat6x libraries compat7x-amd64-7.4.704000.201310.1 Convenience package to
Re: How do maintainer updates work with bugzilla?
I just submitted an update using porttools, port submit. Does this mean it did not get sent? On 8/4/2014 1:22 PM, Jerry wrote: On Mon, 04 Aug 2014 12:44:12 +0100, Matthew Seaman stated: Err... no. I don't believe send-pr does anything useful at the moment. So, exactly what does a send-pr do now exactly? If it does nothing, there should have been some public notice of it AND have been removed from the system. smime.p7s Description: S/MIME Cryptographic Signature
[QAT] 364024: 4x leftovers, 1x depend (arch in graphics/sdl_gfx), 51x success
- Switch audio/musepack to USES=libtool, drop .la files - Bump dependent ports as .so version has changed - Fix audio/abcde by requiring python - Fix audio/moc plist with MUSEPACK enabled Approved by:portmgr blanket - Build ID: 20140804154800-42388 Job owner: amd...@freebsd.org Buildtime: 7 hours Enddate: Mon, 04 Aug 2014 22:53:46 GMT Revision: 364024 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=364024 - Port:audio/abcde 2.5.4_4 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391938/abcde-2.5.4_4.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391939/abcde-2.5.4_4.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391940/abcde-2.5.4_4.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391941/abcde-2.5.4_4.log - Port:audio/aqualung 0.9.b11_20 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391942/aqualung-0.9.b11_20.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391943/aqualung-0.9.b11_20.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391944/aqualung-0.9.b11_20.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391945/aqualung-0.9.b11_20.log - Port:audio/cmus 2.5.1_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391946/cmus-2.5.1_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391947/cmus-2.5.1_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391948/cmus-2.5.1_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391949/cmus-2.5.1_1.log - Port:audio/moc 2.4.4_15 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391950/moc-2.4.4_15.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391951/moc-2.4.4_15.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391952/moc-2.4.4_15.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391953/moc-2.4.4_15.log - Port:audio/musepack 2009.03.01_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391954/musepack-2009.03.01_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391955/musepack-2009.03.01_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391956/musepack-2009.03.01_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391957/musepack-2009.03.01_2.log - Port:audio/musicpd 0.18.11_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~amd...@freebsd.org/20140804154800-42388-391958/musicpd-0.18.11_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log:
Why USE_PYTHON=yes doesn't rebuild default python meta-port?
I am rebuilding the port hierarchy with the top port having USE_PYTHON=yes. This package runs python-config. But only python2 and python27 were actually built, and therefore only python2-config is available and my port breaks. Default meta-port python-2.7, that would have contained python-config, wasn't built. But USE_PYTHON=yes asks for the default python, doesn't it? So is this a bug in the make scripts, or else why default python version wasn't built? FreeBSD-10 with current ports tree. Yuri ___ 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/04/14 15:41, Alexander Leidinger wrote: On Sun, 03 Aug 2014 16:27:36 -0400 Naram Qashat cyberb...@cyberbotx.com wrote: On 08/03/14 15:53, Matthew Seaman wrote: On 03/08/2014 20:34, Naram Qashat wrote: Well, I've been using the command line arguments of -voL '=', and looking at the man page for pkg-version, as far as I can tell, it shouldn't be downloading INDEX, since I do have INDEX-9 on my system. pkg(8) doesn't download or attempt to build an INDEX at all. It can use one if one happens to be already available, but not otherwise. Cheers, Matthew I'm at a bit of a loss, then. While I can't say for sure if pkg is doing something unintended, there seems to be something on my system that is downloading INDEX without my knowledge. My usual way of updating my INDEX is using p5-FreeBSD-Portindex to generate the INDEX file, and using that INDEX to update the files that portupgrade uses. I run that manually, so I have nothing that would do that for me automatically, to my knowledge. How do you update the ports tree, with portsnap or with svn? Portnap also updates the index. Bye, Alexander. I update via svn, so that isn't getting the INDEX updates. 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
Re: WANT_PHP_WEB is just a synonym for WANT_PHP_CGI in automated build environments
Hi Matthew, On Mon, 4 Aug 2014, Matthew Pounsett wrote: As far as I can tell, the only way you get an installed version of PHP without either the CGI or FPM options set is to install mod_php5. That makes installing mod_php5 a prerequisite to making mod_php5 a dependency to any port that uses WANT_PHP_WEB. Now we're finally getting to the issue, let's cut the noise: - automated builds are not a factor. The bug is with the dependencies. - WANT_PHP_CGI is not a factor. The bug is that mod_php5 is not in the loop. So, let's see what happens: 1. databases/phpmyadmin has WANT_PHP_WEB set 2. On a clean environment I want to install that port and expect apache and mod_php5 built for me. 3. Because I don't want fpm or cgi, I unset the options for the lang/php5 options dialog. Expected result: phpMyAdmin depends on apache and mod_php5 among others. Result: # pkg query -F /var/packages/test/All/phpMyAdmin-4.2.7.txz %do lang/php5 archivers/php5-bz2 textproc/php5-ctype security/php5-filter devel/php5-json converters/php5-mbstring security/php5-mcrypt databases/php5-mysqli security/php5-openssl www/php5-session archivers/php5-zlib # pkg query -F /var/packages/test/All/php5-5.4.30.txz %do textproc/libxml2 devel/pcre # pkg info -lF /var/packages/test/All/php5-5.4.30.txz|grep bin/ /usr/local/bin/php /usr/local/bin/php-config /usr/local/bin/phpize So, there is no php-cgi or fpm, but www/mod_php5 is not in phpMyAdmin's dependencies, which means WANT_PHP_WEB is not satisfied, yet no errors are generated. Filed as: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192388 -- Melvyn ___ 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
How to tell pkg it's OK to overwrite files by another port
Hi, the issue: for www/magento there is a sample data package. I'd like to make a port for it, but the sample data overwrites a few files in the www/magento port's installed files to match the sample theme. This is OK and needed. But I don't know how to tell pkg this. I can make the sample data an option in the magento port and keep it in one port, but this would put a large burdon on maintaining the pkg-plist on upgrades as sample-data is only updated when backwards incompatible changes are made to the core that make the older sample data unusable. So I prefer to maintain it as a separate port. -- Melvyn ___ 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
