Sea Water Electrolyzer for Electro-Chlorination
[1]If you can't view this mail click here.. [2] 201721370email.jpg __ [3]Unsubscribeme! [4]Update Email Address! This email sent to freebsd-ports@freebsd.org by [5]n...@ecanode.com Powered by [6][elogo1.jpg] References 1. http://www.ewhizs.com/Preview.aspx?nno=MTAw-T%2f3%2fcheYTl4%3dmem=14 2. http://www.ecanode.com/ 3. http://www.ewhizs.com/unsubscribeme.aspx?ee=ZnJlZWJzZC1wb3J0c0BmcmVlYnNkLm9yZw%3d%3d-tMaMdwRz8NE%3dmem=14 4. http://www.ewhizs.com/updat.aspx?ee=ZnJlZWJzZC1wb3J0c0BmcmVlYnNkLm9yZw%3d%3d-tMaMdwRz8NE%3dmem=14 5. mailto:%2...@ecanode.com 6. http://www.tiaanosoft.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: ports/head@r314338 x11/nvidia-driver
As far as I can tell the reboots are related to a faulty strlen call when compiled with clang. Change compiler to gcc the problem goes away -Original Message- From: owner-freebsd-po...@freebsd.org [mailto:owner-freebsd-po...@freebsd.org] On Behalf Of Waitman Gobble Sent: 01 April 2013 20:06 To: Alexey Dokuchaev Cc: po...@freebsd.org; Sergey V. Dyatko Subject: Re: ports/head@r314338 x11/nvidia-driver Alexey Dokuchaev da...@freebsd.org wrote .. On Mon, Apr 01, 2013 at 03:39:37PM +0300, Sergey V. Dyatko wrote: On Mon, 1 Apr 2013 05:28:27 -0700 David Wolfskill da...@catwhisker.org wrote: On Mon, Apr 01, 2013 at 03:24:33PM +0300, Sergey V. Dyatko wrote: ... looks like r248084-patch-src-nvidia_subr.c is incomplete ... here complete patch I use on my desktop: http://svn.freebsd.by/files/patch-src__nvidia_subr.c.txt Please refer to http://www.freebsd.org/cgi/query-pr.cgi?pr=177459 (Not my PR, but I have tested that it works for my environment.) Ooops, My bad, I did not take advantage of the power of search, sorry. What are the chances of this change to get into the ports tree, before 8.4-R ?:) If I understand correctly It is one of cases, when committer may commit it without portmgr approval ? No, it still requires portmgr@ approval. I will handle it shortly. ./danfe ___ 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: http://www.freebsd.org/cgi/query-pr.cgi?pr=177459 After rebuilding FreeBSD 10.0-CURRENT from SVN the other night, the machine would reboot randomly, either instantly or within 5 minutes or so, it seemed to be related to the nvidia driver. The patch allowed me to update the driver.. which seemed to work. BUT the machine did reboot again maybe an hour later. I've disabled the driver again.. so far it's been running OK without reboot. uptime 12:02PM up 1 day, 1:45 uname -a FreeBSD dx.burplex.com 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248937: Sat Mar 30 21:53:14 PDT 2013 r...@dx.burplex.com:/usr/obj/usr/src/sys/FURAHA amd64 dmesg | grep NVID hdac1: NVIDIA (0x0be2) HDA Controller mem 0xfcffc000-0xfcff irq 17 at device 0.1 on pci4 hdacc1: NVIDIA GT220 HDA CODEC at cad 0 on hdac1 hdaa1: NVIDIA GT220 Audio Function Group at nid 1 on hdacc1 pcm3: NVIDIA GT220 (HDMI/DP 8ch) at nid 5 on hdaa1 hdacc2: NVIDIA GT220 HDA CODEC at cad 1 on hdac1 hdaa2: NVIDIA GT220 Audio Function Group at nid 1 on hdacc2 pcm4: NVIDIA GT220 (HDMI/DP 8ch) at nid 5 on hdaa2 hdacc3: NVIDIA GT220 HDA CODEC at cad 2 on hdac1 hdaa3: NVIDIA GT220 Audio Function Group at nid 1 on hdacc3 pcm5: NVIDIA GT220 (HDMI/DP 8ch) at nid 5 on hdaa3 hdacc4: NVIDIA GT220 HDA CODEC at cad 3 on hdac1 hdaa4: NVIDIA GT220 Audio Function Group at nid 1 on hdacc4 pcm6: NVIDIA GT220 (HDMI/DP 8ch) at nid 5 on hdaa4 *** I'm not 100% it's the nvidia driver to blame but it could be.. anyone else have a reboot issue? I actually have another card (non-nvidia) I'm thinking about putting into that machine so it might not be an issue for me anymore, anyway :) Thanks -- Waitman Gobble San Jose California USA ___ 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
net/freerdp: redefinition of typedef...
Upgrade freerdp-0.8.2_1 to freerdp-1.0.2 fails. The error is below. Thanks. Andriy Kornatskyy [ 12%] Building C object libfreerdp-utils/CMakeFiles/freerdp-utils.dir/registry.c.o In file included from /usr/local/include/freerdp/freerdp.h:27, from /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/include/freerdp/utils/registry.h:29, from /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/libfreerdp-utils/registry.c:22: /usr/local/include/freerdp/types_ui.h:30: error: redefinition of typedef 'uint8' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/include/freerdp/types.h:52: error: previous declaration of 'uint8' was here /usr/local/include/freerdp/types_ui.h:31: error: redefinition of typedef 'sint8' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/include/freerdp/types.h:53: error: previous declaration of 'sint8' was here /usr/local/include/freerdp/types_ui.h:32: error: redefinition of typedef 'uint16' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/include/freerdp/types.h:54: error: previous declaration of 'uint16' was here /usr/local/include/freerdp/types_ui.h:33: error: redefinition of typedef 'sint16' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/include/freerdp/types.h:55: error: previous declaration of 'sint16' was here /usr/local/include/freerdp/types_ui.h:34: error: redefinition of typedef 'uint32' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/include/freerdp/types.h:56: error: previous declaration of 'uint32' was here /usr/local/include/freerdp/types_ui.h:35: error: redefinition of typedef 'sint32' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/include/freerdp/types.h:57: error: previous declaration of 'sint32' was here /usr/local/include/freerdp/types_ui.h:40: error: redefinition of typedef 'uint64' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/include/freerdp/types.h:62: error: previous declaration of 'uint64' was here /usr/local/include/freerdp/types_ui.h:41: error: redefinition of typedef 'sint64' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/include/freerdp/types.h:63: error: previous declaration of 'sint64' was here In file included from /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/include/freerdp/utils/registry.h:29, from /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/libfreerdp-utils/registry.c:22: /usr/local/include/freerdp/freerdp.h:30:1: warning: FREERDP_INTERFACE_VERSION redefined In file included from /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/include/freerdp/utils/file.h:23, from /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/libfreerdp-utils/registry.c:20: /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-616aed4/include/freerdp/api.h:23:1: warning: this is the location of the previous definition *** [libfreerdp-utils/CMakeFiles/freerdp-utils.dir/registry.c.o] Error code 1 ___ 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: amarok-kde4 needs googlemock
On Sat, 30 Mar 2013 00:07:51 +0100, Alberto Villa avi...@freebsd.org wrote: On Friday 29 March 2013 01:30:56 Alberto Villa wrote: On Thursday 28 March 2013 14:35:10 Ronald Klop wrote: After upgrading kde to 4.10 I rebuild amarok and configure failed. This is being analyzed; for some reason, a global CMake setting changed with KDE SC 4.10. Fix committed. 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
ports/177576 math/maxima fails to start with SBCL and quicklisp
Hello, I've submitted PR ports/177576 http://www.freebsd.org/cgi/query-pr.cgi?pr=177576 which is necessary to us quicklisp users. Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
pkg_version: the package info for package '...' is corrupt
[[ I asked about this problem on the -questions list a couple of days ago, but didn't get any relevant replies, so I'm trying again here on the -ports list. Apologies if you see this twice. ]] A couple of days ago my system just simply decided to power itself off (twice) whilst I was in the middle of doing portupgrade -a. I have since learned that the unscheduled and unexpected power offs were due to a CPU cooling problem. I believe that I have that problem in hand now. Separately however, and probably as result of the sudden power offs, when I run pkg_version now I am getting many messages relating to various of my installed packages, all having the following general form: pkg_version: the package info for package 'PKG' is corrupt where `PKG' is the name of some package or another that I have installed. I have at least 6 such messages for different packages I have installed... and probably more. I googled around a bit and did not find any good explanation for the above error or, more importantly, what to do about it. I gather however that my package data base has become corrupted. OK, so how does one rebuild that from scratch? Please don't tell me that I have to reinstall every bleedin' port from scratch! Regards, rfg P.S. Oh! And by the way, I just happen to have made a full system backup quite recently. Do I just simply need to get the entire contents of /var/db/pkg/ from that backup, and then do rm -fr /var/db/pkg and then copy my backup copy of /var/db/pkg to the real /var/db/pkg ? Will that fix the problem? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
RE: net/freerdp: redefinition of typedef...
After deinstall of net/freerdp, it installed just fine. # pkg_info | grep freerdp freerdp-1.0.2 however now I have a problem with net/remmina-plugin-rdp. Error: shared library freerdp.0 does not exist *** [lib-depends] Error code 1 Thanks. Andriy Date: Tue, 2 Apr 2013 18:29:42 +0900 From: m...@vmeta.jp To: freebsd-ports@freebsd.org CC: andriy.kornats...@live.com Subject: Re: net/freerdp: redefinition of typedef... 2013-04-02 16:59 に Andriy Kornatskyy さんは書きました: Upgrade freerdp-0.8.2_1 to freerdp-1.0.2 fails. The error is below. Thanks. Andriy Kornatskyy The issue is already reported and waiting for commit. http://www.freebsd.org/cgi/query-pr.cgi?pr=177405 The workround is to deinstall old freerdp first and then install new version. Thanks, -- `whois vmeta.jp | nkf -w` meta m...@vmeta.jp ___ 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: net/freerdp: redefinition of typedef...
2013-04-02 16:59 に Andriy Kornatskyy さんは書きました: Upgrade freerdp-0.8.2_1 to freerdp-1.0.2 fails. The error is below. Thanks. Andriy Kornatskyy The issue is already reported and waiting for commit. http://www.freebsd.org/cgi/query-pr.cgi?pr=177405 The workround is to deinstall old freerdp first and then install new version. Thanks, -- `whois vmeta.jp | nkf -w` meta m...@vmeta.jp ___ 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_version: the package info for package '...' is corrupt
2013-04-02 11:08, Ronald F. Guilmette skrev: [[ I asked about this problem on the -questions list a couple of days ago, but didn't get any relevant replies, so I'm trying again here on the -ports list. Apologies if you see this twice. ]] A couple of days ago my system just simply decided to power itself off (twice) whilst I was in the middle of doing portupgrade -a. I have since learned that the unscheduled and unexpected power offs were due to a CPU cooling problem. I believe that I have that problem in hand now. Separately however, and probably as result of the sudden power offs, when I run pkg_version now I am getting many messages relating to various of my installed packages, all having the following general form: pkg_version: the package info for package 'PKG' is corrupt where `PKG' is the name of some package or another that I have installed. I have at least 6 such messages for different packages I have installed... and probably more. I googled around a bit and did not find any good explanation for the above error or, more importantly, what to do about it. I gather however that my package data base has become corrupted. OK, so how does one rebuild that from scratch? Please don't tell me that I have to reinstall every bleedin' port from scratch! Regards, rfg P.S. Oh! And by the way, I just happen to have made a full system backup quite recently. Do I just simply need to get the entire contents of /var/db/pkg/ from that backup, and then do rm -fr /var/db/pkg and then copy my backup copy of /var/db/pkg to the real /var/db/pkg ? Will that fix the problem? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Are you using pkg? If so the command should be pkg version without the underscore. /Leslie PS: Your private mail address bounces. I've tried two different SMTP Servers! r...@tristatelogic.com: host server1.tristatelogic.com[69.62.255.118] said: 550 5.7.1 mx1.bjare.net[212.31.160.3]: Client host rejected: bjare.net is BLACKLISTED - Use http://www.tristatelogic.com/contact.html (in reply to RCPT TO command) 550 5.7.1 c-4-202-233-83.cust.bredband2.com[83.233.202.4]: Client host rejected: cust.bredband2.com is BLACKLISTED - Use http://www.tristatelogic.com/contact.html 550 5.1.1 r...@tristatelogic.com... User unknown 554 5.5.1 Error: no valid recipients ___ 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: net/freerdp: redefinition of typedef...
remmina and remmina-plugins are also need to be updated to 1.0.0. I'm working on updating remmina (and its plugins) port. If you want to use remmina with rdp plugin, please stay on freerdp 0.8.2. Thanks, 2013-04-02 18:32 に Andriy Kornatskyy さんは書きました: After deinstall of net/freerdp, it installed just fine. # pkg_info | grep freerdp freerdp-1.0.2 however now I have a problem with net/remmina-plugin-rdp. Error: shared library freerdp.0 does not exist *** [lib-depends] Error code 1 Thanks. Andriy -- `whois vmeta.jp | nkf -w` meta m...@vmeta.jp ___ 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: net/freerdp: redefinition of typedef...
02.04.2013 12:32, Andriy Kornatskyy пишет: After deinstall of net/freerdp, it installed just fine. # pkg_info | grep freerdp freerdp-1.0.2 however now I have a problem with net/remmina-plugin-rdp. Error: shared library freerdp.0 does not exist *** [lib-depends] Error code 1 Remmina is not updated yet. To exempt this kind of errors you can use portmaster or portupgrade. Those two make a backup copies of deleted libraries so they wouldn't be lost during update. -- Sphinx of black quartz, judge my vow. ___ 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: ports/head@r314338 x11/nvidia-driver
On Tue, Apr 02, 2013 at 08:40:08AM +0100, Thomas Sparrevohn wrote: As far as I can tell the reboots are related to a faulty strlen call when compiled with clang. Change compiler to gcc the problem goes away -Original Message- ... FWIW: I have been using clang to build FreeBSD (and x11/nvidia-driver) in both head and stable/9 on my laptop since May 2012. I have not experienced the random reboots. I am also building/running FreeBSD/i386. If there is an issue with clang generating incorrect code for strlen(), getting that issue properly documented so it may be fixed would seem to be useful. Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpIySCT_8wOb.pgp Description: PGP signature
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 +-+ audio/qjackctl | 0.3.9 | 0.3.10 +-+ misc/freeswitch-scripts-devel | 1.2.3 | 1.2.8 +-+ net/freeswitch-curl-devel | 1.2.3 | 1.2.8 +-+ net/freeswitch-insideout-devel | 1.2.3 | 1.2.8 +-+ net/freeswitch-sbc-devel| 1.2.3 | 1.2.8 +-+ net/freeswitch-vanilla-devel| 1.2.3 | 1.2.8 +-+ x11/roxterm | 2.6.5 | 2.7.1 +-+ 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 If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org 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
[QAT] r315213: 3x leftovers, 1x finished
Fix package list if a non-standard PREFIX is used by adding %%LOCALBASE%% to
pkg-plist for icons being installed to ${LOCALBASE}/share/pixmaps/.
This was detected with poudriere testport.
-
Build ID: 20130325102800-16108
Job owner: eha...@freebsd.org
Buildtime: 8 days
Enddate: Tue, 02 Apr 2013 15:45:55 GMT
Revision: r315213
Repository:
https://svnweb.freebsd.org/ports?view=revisionrevision=315213
-
Port:audio/milkytracker 0.90.85_3
Buildgroup: 9.1-QAT/amd64
Buildstatus: LEFTOVERS
Log:
https://qat.redports.org//~eha...@freebsd.org/20130325102800-16108-123732/milkytracker-0.90.85_3.log
Buildgroup: 9.1-QAT/i386
Buildstatus: LEFTOVERS
Log:
https://qat.redports.org//~eha...@freebsd.org/20130325102800-16108-123733/milkytracker-0.90.85_3.log
Buildgroup: 8.3-QAT/amd64
Buildstatus: LEFTOVERS
Log:
https://qat.redports.org//~eha...@freebsd.org/20130325102800-16108-123734/milkytracker-0.90.85_3.log
Buildgroup: 8.3-QAT/i386
Buildstatus: FINISHED
Log:
https://qat.redports.org//~eha...@freebsd.org/20130325102800-16108-123735/milkytracker-0.90.85_3.log
--
Buildarchive URL: https://qat.redports.org/buildarchive/20130325102800-16108
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: [kde-freebsd] py27-pykde4-4.10.1
On Saturday 30 March 2013 13:46:46 Baptiste Daroussin wrote: FYI this was already happening with old options implementation which was already using uniquename which is not unique *sick* IIRC the problem is not UNIQUENAME, but PKGNAMEPREFIX being set after bsd.options.mk uses it to define OPTIONSFILE. bsd.options.mk should be called after bsd.port.pre.mk, to let *.mk files define their own PKGNAMEPREFIX. In fact, defining PKGNAMEPREFIX by hand makes it work. I found this problem when porting Qt 5 but had no time to report it; should I attach this information to the PR or is it known already? -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla The jig's up, Elman. Which jig? -- Jeff Elman signature.asc Description: This is a digitally signed message part.
Re: [kde-freebsd] py27-pykde4-4.10.1
On Tue, Apr 02, 2013 at 07:05:17PM +0200, Alberto Villa wrote: On Saturday 30 March 2013 13:46:46 Baptiste Daroussin wrote: FYI this was already happening with old options implementation which was already using uniquename which is not unique *sick* IIRC the problem is not UNIQUENAME, but PKGNAMEPREFIX being set after bsd.options.mk uses it to define OPTIONSFILE. bsd.options.mk should be called after bsd.port.pre.mk, to let *.mk files define their own PKGNAMEPREFIX. In fact, defining PKGNAMEPREFIX by hand makes it work. I found this problem when porting Qt 5 but had no time to report it; should I attach this information to the PR or is it known already? -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla The jig's up, Elman. Which jig? -- Jeff Elman No, OPTIONSFILE is built base on UNIQUENAME which is built which uses PKGNAMEPREFIX. that is the reason. regards, Bapt pgp4X4hg7RXmZ.pgp Description: PGP signature
Re: [kde-freebsd] py27-pykde4-4.10.1
On Tuesday 02 April 2013 19:08:14 Baptiste Daroussin wrote:
OPTIONSFILE is built base on UNIQUENAME which is built which uses
PKGNAMEPREFIX.
that is the reason.
bsd.options.mk, line 194: the .if exists(${OPTIONSFILE}) tries to evaluate
(make(1) functions evaluate immediately, as you know), among other,
PKGNAMEPREFIX, which is not yet set because bsd.python.mk is included at line
1424, while bsd.options.mk is included at line 1311 (speaking of bsd.port.mk).
Thus, OPTIONSFILE is not included.
This was the case with bsd.qt.mk, at least, so I suspect it's the same.
--
Alberto Villa, FreeBSD committer avi...@freebsd.org
http://people.FreeBSD.org/~avilla
Fanaticism consists of redoubling your effort when you have
forgotten your aim.
-- George Santayana
signature.asc
Description: This is a digitally signed message part.
Re: [kde-freebsd] py27-pykde4-4.10.1
On Tue, Apr 02, 2013 at 07:14:36PM +0200, Alberto Villa wrote:
On Tuesday 02 April 2013 19:08:14 Baptiste Daroussin wrote:
OPTIONSFILE is built base on UNIQUENAME which is built which uses
PKGNAMEPREFIX.
that is the reason.
bsd.options.mk, line 194: the .if exists(${OPTIONSFILE}) tries to evaluate
(make(1) functions evaluate immediately, as you know), among other,
PKGNAMEPREFIX, which is not yet set because bsd.python.mk is included at line
1424, while bsd.options.mk is included at line 1311 (speaking of
bsd.port.mk).
Thus, OPTIONSFILE is not included.
This was the case with bsd.qt.mk, at least, so I suspect it's the same.
Yes that true, and it is because OPTIONSFILE was (before optionsng) and still is
(with optionsng) built based on UNIQUENAME which is built base on PKGNAMEPREFIX.
cf bsd.port.mk L1286
So bsd.python.mk (it is not the only one) setting PKGNAMEPREFIX makes UNIQUENAME
not unique at all, first problem, it also make it changing meanng OPTIONSFILE
is expanded a first time to load options when PKGNAMEPREFIX is not yet set and
expanded a second time (when saving options) and PKGNAMEPREFIX is now set.
bsd.options.mk can't anyway be loaded after bsd.port.pre.mk given that one may
want to provide a PYTHON option and will make it set USE_PYTHON=yes for
example.
I don't know the right fix to be honnest. But UNIQUENAME not being UNIQUE is a
real problem imho and OPTIONSFILE changing depending on being after pre.mk or
before pre.mk is another problem.
I don't know what came first between the bsd.*.mk changing the PKGNAMEPREFIX and
UNIQUENAME creation, but for sure one choice here hasn't been smart.
regards,
Bapt
pgpt7EvBBSVEZ.pgp
Description: PGP signature
Poudriere-devel version 3.0.99.20130327 loads zfs kernel modules even with NO_ZFS set.
Hi, I couldn't find a more suitable list(s) for this so apologies. I really like the ability of building packages using poudriere-devel without having to use a ZFS pool by using NO_ZFS in the config file. However there seems to be a small glitch in the implementation, the zfs.ko and opensolaris.ko kernel modules get always loaded when the poudriere bulk build is started because it seems to try to figure out if a ZFS pool exists on the system by running zpool(8) regardless of NO_ZFS setting. If NO_ZFS is set in poudriere.conf the zpool(8) command should not be run at all. -Kimmo ___ 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: [kde-freebsd] py27-pykde4-4.10.1
On Tuesday 02 April 2013 19:24:40 Baptiste Daroussin wrote:
bsd.options.mk can't anyway be loaded after bsd.port.pre.mk given that one
may want to provide a PYTHON option and will make it set
USE_PYTHON=yes for
example.
Sure, you're right.
I don't know the right fix to be honnest. But UNIQUENAME not being UNIQUE
is
a real problem imho and OPTIONSFILE changing depending on being after
pre.mk or before pre.mk is another problem.
As far as I know LATEST_LINK should be unique (there was also a service
checking for duplicates)... What about UNIQUENAME=${LATEST_LINK}?
Anyway the problem is not with UNIQUENAME, it's with the usage of
PKGNAMESUFFIX. PKGNAMESUFFIX should be used by ports sharing the same
OPTIONS but with light differencies (e.g., variations of a single port); it
would be perfect. Unfortunately, time passed and it started being used the
wrong (so wrong) way. Either PKGNAMESUFFIX usage is fixed (among 20k
ports!), or UNIQUENAME is set to LATEST_LINK (or similar).
About the loading order, yes, it needs serious thought. At the same time, many
*.mk files need to be fixed as they don't distinguish between pre- and post-
makefile sections. Some day a vademecum has to be written about those two
sections, and I volunteer to help with that as I studied the matter quite well
in the past.
--
Alberto Villa, FreeBSD committer avi...@freebsd.org
http://people.FreeBSD.org/~avilla
There are two problems with a major hangover. You feel
like you are going to die and you're afraid that you won't.
signature.asc
Description: This is a digitally signed message part.
Re: [kde-freebsd] py27-pykde4-4.10.1
On 2013-04-02 19:24, Baptiste Daroussin wrote:
On Tue, Apr 02, 2013 at 07:14:36PM +0200, Alberto Villa wrote:
On Tuesday 02 April 2013 19:08:14 Baptiste Daroussin wrote:
OPTIONSFILE is built base on UNIQUENAME which is built which uses
PKGNAMEPREFIX.
that is the reason.
bsd.options.mk, line 194: the .if exists(${OPTIONSFILE}) tries to evaluate
(make(1) functions evaluate immediately, as you know), among other,
PKGNAMEPREFIX, which is not yet set because bsd.python.mk is included at
line
1424, while bsd.options.mk is included at line 1311 (speaking of
bsd.port.mk).
Thus, OPTIONSFILE is not included.
This was the case with bsd.qt.mk, at least, so I suspect it's the same.
Yes that true, and it is because OPTIONSFILE was (before optionsng) and still
is
(with optionsng) built based on UNIQUENAME which is built base on
PKGNAMEPREFIX.
cf bsd.port.mk L1286
So bsd.python.mk (it is not the only one) setting PKGNAMEPREFIX makes
UNIQUENAME
not unique at all, first problem, it also make it changing meanng OPTIONSFILE
is expanded a first time to load options when PKGNAMEPREFIX is not yet set and
expanded a second time (when saving options) and PKGNAMEPREFIX is now set.
bsd.options.mk can't anyway be loaded after bsd.port.pre.mk given that one may
want to provide a PYTHON option and will make it set USE_PYTHON=yes for
example.
I don't know the right fix to be honnest. But UNIQUENAME not being UNIQUE is a
real problem imho and OPTIONSFILE changing depending on being after pre.mk or
before pre.mk is another problem.
I don't know what came first between the bsd.*.mk changing the PKGNAMEPREFIX
and
UNIQUENAME creation, but for sure one choice here hasn't been smart.
Havent't done a test and looked for the right place but maybe it's an option to
chop prefixes like py2x, ap2x from OPTIONSFILE
sample OPTIONSFILE=${PKGNAMEPREFIX:S/py27-//:S/ap22-//:S/ap24-// ...
At last we should stop rewriting p5/py/ap ports to use only PORTDOCS / EXAMPLES
to the new options style until we have a proof solution.
--
Regards,
olli
___
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_version: the package info for package '...' is corrupt
On 4/2/2013 11:41 AM, Leslie Jensen wrote: 2013-04-02 11:08, Ronald F. Guilmette skrev: [[ I asked about this problem on the -questions list a couple of days ago, but didn't get any relevant replies, so I'm trying again here on the -ports list. Apologies if you see this twice. ]] A couple of days ago my system just simply decided to power itself off (twice) whilst I was in the middle of doing portupgrade -a. I have since learned that the unscheduled and unexpected power offs were due to a CPU cooling problem. I believe that I have that problem in hand now. Separately however, and probably as result of the sudden power offs, when I run pkg_version now I am getting many messages relating to various of my installed packages, all having the following general form: pkg_version: the package info for package 'PKG' is corrupt where `PKG' is the name of some package or another that I have installed. I have at least 6 such messages for different packages I have installed... and probably more. I googled around a bit and did not find any good explanation for the above error or, more importantly, what to do about it. I gather however that my package data base has become corrupted. OK, so how does one rebuild that from scratch? Please don't tell me that I have to reinstall every bleedin' port from scratch! Regards, rfg P.S. Oh! And by the way, I just happen to have made a full system backup quite recently. Do I just simply need to get the entire contents of /var/db/pkg/ from that backup, and then do rm -fr /var/db/pkg and then copy my backup copy of /var/db/pkg to the real /var/db/pkg ? Will that fix the problem? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Are you using pkg? If so the command should be pkg version without the underscore. No, this is the old pkg_version which produces this output. With pkgng, the database is atomic thanks to sqlite, thus this problem would not have occured. /Leslie PS: Your private mail address bounces. I've tried two different SMTP Servers! r...@tristatelogic.com: host server1.tristatelogic.com[69.62.255.118] said: 550 5.7.1 mx1.bjare.net[212.31.160.3]: Client host rejected: bjare.net is BLACKLISTED - Use http://www.tristatelogic.com/contact.html (in reply to RCPT TO command) 550 5.7.1 c-4-202-233-83.cust.bredband2.com[83.233.202.4]: Client host rejected: cust.bredband2.com is BLACKLISTED - Use http://www.tristatelogic.com/contact.html 550 5.1.1 r...@tristatelogic.com... User unknown 554 5.5.1 Error: no valid recipients ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Poudriere-devel version 3.0.99.20130327 loads zfs kernel modules even with NO_ZFS set.
Le Tue, 2 Apr 2013 20:31:55 +0300, Kimmo Paasiala kpaas...@gmail.com a écrit : Hello, I couldn't find a more suitable list(s) for this so apologies. You can report and check poudriere bugs here: https://fossil.etoilebsd.net/poudriere/reportlist I really like the ability of building packages using poudriere-devel without having to use a ZFS pool by using NO_ZFS in the config file. Looks a nice feature. Regards. ___ 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
WCO Knowledge Academy for Customs and Trade 2013
-- To unsubscribe from this mailing list, please click here https://www.eiseverywhere.com/emarketing/profile.php?id=0Hcj%2BTAkFp1Y6cExxXIJvGgSr%2BBvRwXu ___ 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_version: the package info for package '...' is corrupt
Ok, first, my apologies to Leslie Jensen about the e-mail bounce. It is nothing personal, believe me. I just have a personal policy of locally blacklisting any and all domains that send me spam. (Apparently, at one time or another, I received some spam from bjare.net.) I believe that if _everybody_... or even just 10% of everybody... did as I do, then ISPs would finally take seriously their spam outflow problems. (Most of them don't at present, and that explains why there is so much spam.) Now, as regards to pkg_version versus pkg version I have never even seen the latter, so I don't know a damn thing about that. Furthermore, although there does appear to be an executable named /usr/sbin/pkg present on my system, whatever the heck it is, it does not seem to have any associated man page. :-( So anyway, I have never used it, I don't know what it even does, and I would still not know how to use it, even if you held a gun to my head. Regarding Julien Laffaye comment(s) relating to pkgng, I have also never even heard of that before now. What is it and where do I get it? And if it is so wonderful... and if what I am using is considered old... then why isn't this new pkgng thing the default in/on 9.1-RELEASE? (I also apparently have no man page for anything called pkgng on my system.) Anyway, athough I do thank both Leslie Jensen and Julien Laffaye for their comments and attempts to help, I still am in DIRE need of an answer to my original question. I have, apparently, over 50 of my installed ports that pkg_version is now telling me are in some *unspecified way* corrupt and I still need (and am desperately begging for) someone to tell me how to resolve that problem, exactly. As I have said, I _do_ have a recent full system backup, but that doesn't help me unless and until someone tells me which file or files from that, exactly, I should be restoring in order to eliminate this problem. Could someone kindly do that, please? Regards, rfg P.S. I do most seriously wonder if whoever engineered the FreeBSD ports system ever realized how dramatically UNhelpful a message like the following actually is: pkg_version: the package info for package 'evince-2.32.0_9' is corrupt I do not intend to offend anyone, but to be frank, this is the kind of a message I would expect out of a Windows system, i.e. a message that some- thing is broken, but providing -zero- details regarding what exactly is broken, where it is located, or, most importantly, how to begin to fix the problem. When I am using Windows, I _expect_ to be treated like a luser... i.e. one who cannot be trusted with too much information. When I am using any kind of *NIX system however, I tend to expect the exact opposite, and am rather unhappy when critical information is hidden from me. ___ 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_version: the package info for package '...' is corrupt
On 4/2/2013 10:30 PM, Ronald F. Guilmette wrote: Ok, first, my apologies to Leslie Jensen about the e-mail bounce. It is nothing personal, believe me. I just have a personal policy of locally blacklisting any and all domains that send me spam. (Apparently, at one time or another, I received some spam from bjare.net.) I believe that if _everybody_... or even just 10% of everybody... did as I do, then ISPs would finally take seriously their spam outflow problems. (Most of them don't at present, and that explains why there is so much spam.) Now, as regards to pkg_version versus pkg version I have never even seen the latter, so I don't know a damn thing about that. Furthermore, although there does appear to be an executable named /usr/sbin/pkg present on my system, whatever the heck it is, it does not seem to have any associated man page. :-( So anyway, I have never used it, I don't know what it even does, and I would still not know how to use it, even if you held a gun to my head. Regarding Julien Laffaye comment(s) relating to pkgng, I have also never even heard of that before now. What is it and where do I get it? And if it is so wonderful... and if what I am using is considered old... then why isn't this new pkgng thing the default in/on 9.1-RELEASE? (I also apparently have no man page for anything called pkgng on my system.) https://wiki.freebsd.org/pkgng /usr/bin/pkg is the binary that will bootrap pkgng, installing the real binary and manpages. Anyway, athough I do thank both Leslie Jensen and Julien Laffaye for their comments and attempts to help, I still am in DIRE need of an answer to my original question. I have, apparently, over 50 of my installed ports that pkg_version is now telling me are in some *unspecified way* corrupt and I still need (and am desperately begging for) someone to tell me how to resolve that problem, exactly. As I have said, I _do_ have a recent full system backup, but that doesn't help me unless and until someone tells me which file or files from that, exactly, I should be restoring in order to eliminate this problem. Could someone kindly do that, please? You can try ports-mgmt/portmaster, which has some options to try to repair the /var/db/pkg database. If the backup is fresh and you did not install new packages since, you can just copy the /var/db/pkg from the backup to the system (backup-ing the broken one, we never know, you might need it...) Regards, rfg P.S. I do most seriously wonder if whoever engineered the FreeBSD ports system ever realized how dramatically UNhelpful a message like the following actually is: pkg_version: the package info for package 'evince-2.32.0_9' is corrupt I do not intend to offend anyone, but to be frank, this is the kind of a message I would expect out of a Windows system, i.e. a message that some- thing is broken, but providing -zero- details regarding what exactly is broken, where it is located, or, most importantly, how to begin to fix the problem. When I am using Windows, I _expect_ to be treated like a luser... i.e. one who cannot be trusted with too much information. When I am using any kind of *NIX system however, I tend to expect the exact opposite, and am rather unhappy when critical information is hidden from me. ___ 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
[QAT] r315222: 1x depend (depend_package in x11/libxp), 7x finished, 1x depend (depend_package in databases/qt4-sqlite3-plugin), 17x success, 2x leftovers
- Add global options (DOCS, NLS, etc) to the OPTIONS_DEFINE if it's already defined - Remove OPTIONS_DEFINE, if it contains only global options - Build ID: 2013032514-32589 Job owner: m...@freebsd.org Buildtime: 8 days Enddate: Tue, 02 Apr 2013 22:12:34 GMT Revision: r315222 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=315222 - Port:devel/qdevelop 0.28_2 Buildgroup: 9.1-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123764/qdevelop-0.28_2.log Buildgroup: 9.1-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123765/qdevelop-0.28_2.log Buildgroup: 8.3-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123766/qdevelop-0.28_2.log Buildgroup: 8.3-QAT/i386 Buildstatus: FINISHED Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123767/libxcb-1.7.log - Port:games/warmux 11.04.1_2 Buildgroup: 9.1-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123768/warmux-11.04.1_2.log Buildgroup: 9.1-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123769/warmux-11.04.1_2.log Buildgroup: 8.3-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123770/warmux-11.04.1_2.log Buildgroup: 8.3-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123771/warmux-11.04.1_2.log - Port:graphics/xaos 3.5_4 Buildgroup: 9.1-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123772/xaos-3.5_4.log Buildgroup: 9.1-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123773/xaos-3.5_4.log Buildgroup: 8.3-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123774/xaos-3.5_4.log Buildgroup: 8.3-QAT/i386 Buildstatus: FINISHED Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123775/libxcb-1.7.log - Port:math/qtiplot 0.9.8.9_4 Buildgroup: 9.1-QAT/amd64 Buildstatus: DEPEND (DEPEND_PACKAGE IN DATABASES/QT4-SQLITE3-PLUGIN) Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123776/qt4-sqlite-plugin-4.8.4.log Buildgroup: 9.1-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123777/qtiplot-0.9.8.9_4.log Buildgroup: 8.3-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123778/qtiplot-0.9.8.9_4.log Buildgroup: 8.3-QAT/i386 Buildstatus: DEPEND (DEPEND_PACKAGE IN X11/LIBXP) Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123779/libXp-1.0.1,1.log - Port:multimedia/minitube 2.0 Buildgroup: 9.1-QAT/amd64 Buildstatus: FINISHED Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123780/minitube-2.0.log Buildgroup: 9.1-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123781/minitube-2.0.log Buildgroup: 8.3-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123782/minitube-2.0.log Buildgroup: 8.3-QAT/i386 Buildstatus: FINISHED Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123783/libxcb-1.7.log - Port:print/hplip 3.13.2 Buildgroup: 9.1-QAT/amd64 Buildstatus: FINISHED Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123784/hplip-3.13.2.log Buildgroup: 9.1-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/2013032514-32589-123785/hplip-3.13.2.log Buildgroup: 8.3-QAT/amd64
graphics/shotwell needs a new home
Hello, A year or two ago, I fixed up shotwell and took maintainership from gnome@. Unfortunately, the build broke a month ago or so, and it needs some love from someone much more familiar with gnomeisms to make it functional. gnome@ has indicated they don't want it back, for which I can't necessarily blame them. Is there some brave soul that might be willing to adopt it? Thanks, David ___ 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
php5-ice Needs Updating
=== php5-Ice-3.4.2 cannot be installed: doesn't work with lang/php5 port (doesn't support PHP 5.4). *** [install] Error code 1 Stop in /usr/ports/devel/php5-ice. Could you guys update this? I really need this extension. Regards, Jaret ___ 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] r315340: 3x leftovers, 1x finished
Update 4.2.7p357 -- 4.2.7p364 - Build ID: 20130327002000-26832 Job owner: c...@freebsd.org Buildtime: 7 days Enddate: Wed, 03 Apr 2013 05:57:19 GMT Revision: r315340 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=315340 - Port:net/ntp-devel 4.2.7p364 Buildgroup: 9.1-QAT/amd64 Buildstatus: FINISHED Log: https://qat.redports.org//~c...@freebsd.org/20130327002000-26832-124452/ntp-4.2.7p364.log Buildgroup: 9.1-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~c...@freebsd.org/20130327002000-26832-124453/ntp-4.2.7p364.log Buildgroup: 8.3-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~c...@freebsd.org/20130327002000-26832-124454/ntp-4.2.7p364.log Buildgroup: 8.3-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~c...@freebsd.org/20130327002000-26832-124455/ntp-4.2.7p364.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20130327002000-26832 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
