Re: redports and build status
On Tue, Aug 12, 2014 at 8:54 PM, Tijl Coosemans t...@freebsd.org wrote: On Tue, 12 Aug 2014 19:38:27 +0200 Fernando Apesteguía wrote: Hi there, I built a port in redports and I received a mail notifying that the builds were finished, but it seems redports couldn't figure out if the builds finished successfully. https://redports.org/buildarchive/20140812170901-30860 Any ideas of why this happened? Thanks in advance. I'm seeing a lot of these as well. CCing decke@ Yeah, the finished state is some rescue state in case something went terribly wrong. Usually this happens when something inside redports fails or some backend behaves very weird or if the port creates some very strange situation like a recursive dependency (which fills up a temporary partition and then fails). If only one of many jobs fails then chances are good that it is some redports weirdness. If many jobs fail (like in this case) and it is reproducible then the chances are good that your port is doing something very very bad. -- Bernhard Froehlich http://www.bluelife.at/ ___ 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, pkg's confusion on upgrades...
Hi, We have a number of 10.x systems now - where we install packages (aka pkg install) some components, but other components we build from ports (as we need to add / remove options that the package gives you no choice over). Initially 'pkg upgrade' wanted to replace the port versions with pkg versions (which include options we don't want, and would have pulled in a lot of other dependencies). I seem to have fixed this by 'locking' them (i.e. pkg lock) - pkg upgrade doesn't want to touch them now, which is good. But, 'pkg upgrade' still wants to pull in more packages than are installed - i.e. 'pkg upgrade' shows entries under to be INSTALLED as well as to be UPGRADED. 'pkg info -a -d' displays the dependencies of all installed packages (none of which depend on the package it wants to install) - but I can't seem to find any way to get 'pkg upgrade' to tell me why it wants to install a new package (i.e. which *upgrade* is it doing that now requires the to be INSTALLED packages?) -Karl ___ 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
[BUG] GDB port bug report due to login problems with Bugzilla
Hello. As I am not able to login to Bugzilla to report a bug (502 Bad Gateway from nginx?) I would like to inform you here about a bug in devel/gdb. Since before updating to 7.8.1 I had no problems. Now with latest patch to fbsd-threads.c (R 364713) gdb crashes with the first run command. % gdb78 `which gdb78`gdb78.core GNU gdb (GDB) 7.8 [GDB v7.8 for FreeBSD] Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i386-portbld-freebsd9.1. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from /usr/local/bin/gdb78...done. [New process 100614] Core was generated by `gdb78'. Program terminated with signal SIGABRT, Aborted. #0 0x293c73f7 in kill () from /lib/libc.so.7 (gdb) bt #0 0x293c73f7 in kill () from /lib/libc.so.7 #1 0x293c7316 in raise () from /lib/libc.so.7 #2 0x293c5d9a in abort () from /lib/libc.so.7 #3 0x0841ba8a in can_dump_core (reason=0x89f49b0 DB does when %s is detected.) at utils.c:630 #4 0x0841bdb1 in internal_verror ( file=0x299dca80 target.c:2626: internal-error: Can't determine the current address space of thread LWP 1\n\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable., line=144656744, fmt=0x89f49cf , ap=0x299e8c00 (y or n) ) at utils.c:802 #5 0x089f49b0 in ?? () #6 0x0841be1e in ?? () at utils.c:813 #7 0x0841be5c in internal_warning ( file=0x89d1947 col of the target machine.\nRemaining arguments are interpreted by the target protocol. For more\ninformation on the arguments for a particular protocol, type\n`help target ' followed by the protocol na..., line=2626, string=0x89d25a4 LL) at utils.c:832 #8 0x08354773 in target_thread_address_space (ptid=...) at target.c:2642 #9 0x0834dd24 in tdefault_trace_init (self=0x92982c0 dummy_target) at target-delegates.c:964 #10 0x0834dd24 in tdefault_trace_init (self=0x92c5d40 exec_ops) at target-delegates.c:964 #11 0x0834dd24 in tdefault_trace_init (self=0x298ba500) at target-delegates.c:964 #12 0x0834dd24 in tdefault_trace_init (self=0x9290400 fbsd_thread_ops) at target-delegates.c:964 #13 0x083547ab in target_thread_address_space (ptid=...) at target.c:2645 #14 0x082b2227 in ?? () at regcache.c:491 #15 0x082b231a in regcache_observer_target_changed (target=0x8999254) at regcache.c:520 #16 0x0830b960 in thread_still_needs_step_over (tp=0x29a02900) at infrun.c:2110 #17 0x08311beb in keep_going (ecs=0xbfbfe138) at infrun.c:5809 #18 0x0830f842 in process_event_stop_test (ecs=0xbfbfe138) at infrun.c:4590 #19 0x0830f292 in process_event_stop_test (ecs=0xbfbfe138) at infrun.c:4349 #20 0x0830e525 in handle_inferior_event (ecs=0xbfbfe138) at infrun.c:3830 #21 0x0830ca66 in fetch_inferior_event (client_data=0x298ba500) at infrun.c:2865 #22 0x0830bfa8 in start_remote (from_tty=674835856) at infrun.c:2423 #23 0x08304d1c in ?? () at infcmd.c:641 #24 0x08304d50 in start_command (args=0x0, from_tty=1) at infcmd.c:660 #25 0x0823b41b in do_sfunc (c=0x299d1350, args=0x0, from_tty=1) at ./cli/cli-decode.c:123 #26 0x0823e241 in multi_line_command_p (type=698159952) at ./cli/cli-script.c:97 #27 0x08419253 in execute_command (p=0x2983b081 , from_tty=1) at top.c:482 #28 0x0832c821 in command_line_handler (rl=0x2983b080 ) at event-top.c:460 #29 0x0832cd73 in gdb_readline2 (client_data=0x2983d134) at event-top.c:653 #30 0x2912a117 in rl_callback_read_char () from /usr/local/lib/libreadline.so.6 #31 0x0832c3ab in change_line_handler () at event-top.c:200 #32 0x0832c712 in async_disable_stdin () at event-top.c:399 #33 0xbfbfe6ac in ?? () (gdb) q % uname -a FreeBSD entw-pr2.demig.intra 9.1-RELEASE FreeBSD 9.1-RELEASE #2: Wed Feb 6 17:03:36 CET 2013 root@entw-pr2.demig.intra:/usr/obj/usr/src/sys/ENTW-PR2 i386 Best regards, Norbert Koch ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Redports, broken regression tests and missing check-orphans
Bernhard, while we're at it, there are currently two problems with
redports which diminish it's usefulness significantly:
1. Redports used to run make regression-test on every build; right
now, each log has this instead:
phase 5: make test
[: -eq: unexpected operator
=== Regression tests skipped. ===
So, no regression tests are executed. I don't know what the problem is here.
2. Most ports now have stage support; this means that checking for
leftover files under ${PREFIX} is close to useless: only files in
pkg-plist are copied there. Instead, leftovers should be searched for in
${STAGEDIR} -- running make stage-qa and make check-orphans with
every build would do that.
(I've already botched two patches when I assumed that successful
redports run means that pkg-plist is complete).
So, can the first problem be fixed and the second suggestion
implemented? Should I be bothering tinderbox author(s) instead?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: redports and build status
On Wed, 13 Aug 2014 09:49:31 +0200 Bernhard Fröhlich wrote: On Tue, Aug 12, 2014 at 8:54 PM, Tijl Coosemans t...@freebsd.org wrote: On Tue, 12 Aug 2014 19:38:27 +0200 Fernando Apesteguía wrote: I built a port in redports and I received a mail notifying that the builds were finished, but it seems redports couldn't figure out if the builds finished successfully. https://redports.org/buildarchive/20140812170901-30860 Any ideas of why this happened? Thanks in advance. I'm seeing a lot of these as well. CCing decke@ Yeah, the finished state is some rescue state in case something went terribly wrong. Usually this happens when something inside redports fails or some backend behaves very weird or if the port creates some very strange situation like a recursive dependency (which fills up a temporary partition and then fails). If only one of many jobs fails then chances are good that it is some redports weirdness. If many jobs fail (like in this case) and it is reproducible then the chances are good that your port is doing something very very bad. I'm seeing these on multiple unrelated ports and with trivial changes. I've now cleared my redports tree, leaving only one unmodified port and it still results in all 'finished'. Maybe redport's internal ports tree got corrupt or one of its cached packages? ___ 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: [BUG] GDB port bug report due to login problems with Bugzilla
On Wed, 13 Aug 2014 11:42:35 +0200 Norbert Koch wrote: Hello. As I am not able to login to Bugzilla to report a bug (502 Bad Gateway from nginx?) I would like to inform you here about a bug in devel/gdb. Since before updating to 7.8.1 I had no problems. Now with latest patch to fbsd-threads.c (R 364713) gdb crashes with the first run command. % gdb78 `which gdb78`gdb78.core GNU gdb (GDB) 7.8 [GDB v7.8 for FreeBSD] Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i386-portbld-freebsd9.1. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from /usr/local/bin/gdb78...done. [New process 100614] Core was generated by `gdb78'. Program terminated with signal SIGABRT, Aborted. #0 0x293c73f7 in kill () from /lib/libc.so.7 (gdb) bt #0 0x293c73f7 in kill () from /lib/libc.so.7 #1 0x293c7316 in raise () from /lib/libc.so.7 #2 0x293c5d9a in abort () from /lib/libc.so.7 #3 0x0841ba8a in can_dump_core (reason=0x89f49b0 DB does when %s is detected.) at utils.c:630 #4 0x0841bdb1 in internal_verror ( file=0x299dca80 target.c:2626: internal-error: Can't determine the current address space of thread LWP 1\n\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable., line=144656744, fmt=0x89f49cf , ap=0x299e8c00 (y or n) ) at utils.c:802 #5 0x089f49b0 in ?? () #6 0x0841be1e in ?? () at utils.c:813 #7 0x0841be5c in internal_warning ( file=0x89d1947 col of the target machine.\nRemaining arguments are interpreted by the target protocol. For more\ninformation on the arguments for a particular protocol, type\n`help target ' followed by the protocol na..., line=2626, string=0x89d25a4 LL) at utils.c:832 #8 0x08354773 in target_thread_address_space (ptid=...) at target.c:2642 #9 0x0834dd24 in tdefault_trace_init (self=0x92982c0 dummy_target) at target-delegates.c:964 #10 0x0834dd24 in tdefault_trace_init (self=0x92c5d40 exec_ops) at target-delegates.c:964 #11 0x0834dd24 in tdefault_trace_init (self=0x298ba500) at target-delegates.c:964 #12 0x0834dd24 in tdefault_trace_init (self=0x9290400 fbsd_thread_ops) at target-delegates.c:964 #13 0x083547ab in target_thread_address_space (ptid=...) at target.c:2645 #14 0x082b2227 in ?? () at regcache.c:491 #15 0x082b231a in regcache_observer_target_changed (target=0x8999254) at regcache.c:520 #16 0x0830b960 in thread_still_needs_step_over (tp=0x29a02900) at infrun.c:2110 #17 0x08311beb in keep_going (ecs=0xbfbfe138) at infrun.c:5809 #18 0x0830f842 in process_event_stop_test (ecs=0xbfbfe138) at infrun.c:4590 #19 0x0830f292 in process_event_stop_test (ecs=0xbfbfe138) at infrun.c:4349 #20 0x0830e525 in handle_inferior_event (ecs=0xbfbfe138) at infrun.c:3830 #21 0x0830ca66 in fetch_inferior_event (client_data=0x298ba500) at infrun.c:2865 #22 0x0830bfa8 in start_remote (from_tty=674835856) at infrun.c:2423 #23 0x08304d1c in ?? () at infcmd.c:641 #24 0x08304d50 in start_command (args=0x0, from_tty=1) at infcmd.c:660 #25 0x0823b41b in do_sfunc (c=0x299d1350, args=0x0, from_tty=1) at ./cli/cli-decode.c:123 #26 0x0823e241 in multi_line_command_p (type=698159952) at ./cli/cli-script.c:97 #27 0x08419253 in execute_command (p=0x2983b081 , from_tty=1) at top.c:482 #28 0x0832c821 in command_line_handler (rl=0x2983b080 ) at event-top.c:460 #29 0x0832cd73 in gdb_readline2 (client_data=0x2983d134) at event-top.c:653 #30 0x2912a117 in rl_callback_read_char () from /usr/local/lib/libreadline.so.6 #31 0x0832c3ab in change_line_handler () at event-top.c:200 #32 0x0832c712 in async_disable_stdin () at event-top.c:399 #33 0xbfbfe6ac in ?? () (gdb) q % uname -a FreeBSD entw-pr2.demig.intra 9.1-RELEASE FreeBSD 9.1-RELEASE #2: Wed Feb 6 17:03:36 CET 2013 root@entw-pr2.demig.intra:/usr/obj/usr/src/sys/ENTW-PR2 i386 CCing maintainer ___ 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: [BUG] GDB port bug report due to login problems with Bugzilla
Hi Norbert, it could be a problem related to i386, because on amd64 it works perfectly. I'll try to get a i386 system and test it more deeply. thanks for the help best regards, pizzamig On Wed, Aug 13, 2014 at 11:42 AM, Norbert Koch nk...@demig.de wrote: Hello. As I am not able to login to Bugzilla to report a bug (502 Bad Gateway from nginx?) I would like to inform you here about a bug in devel/gdb. Since before updating to 7.8.1 I had no problems. Now with latest patch to fbsd-threads.c (R 364713) gdb crashes with the first run command. % gdb78 `which gdb78`gdb78.core GNU gdb (GDB) 7.8 [GDB v7.8 for FreeBSD] Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i386-portbld-freebsd9.1. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from /usr/local/bin/gdb78...done. [New process 100614] Core was generated by `gdb78'. Program terminated with signal SIGABRT, Aborted. #0 0x293c73f7 in kill () from /lib/libc.so.7 (gdb) bt #0 0x293c73f7 in kill () from /lib/libc.so.7 #1 0x293c7316 in raise () from /lib/libc.so.7 #2 0x293c5d9a in abort () from /lib/libc.so.7 #3 0x0841ba8a in can_dump_core (reason=0x89f49b0 DB does when %s is detected.) at utils.c:630 #4 0x0841bdb1 in internal_verror ( file=0x299dca80 target.c:2626: internal-error: Can't determine the current address space of thread LWP 1\n\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable., line=144656744, fmt=0x89f49cf , ap=0x299e8c00 (y or n) ) at utils.c:802 #5 0x089f49b0 in ?? () #6 0x0841be1e in ?? () at utils.c:813 #7 0x0841be5c in internal_warning ( file=0x89d1947 col of the target machine.\nRemaining arguments are interpreted by the target protocol. For more\ninformation on the arguments for a particular protocol, type\n`help target ' followed by the protocol na..., line=2626, string=0x89d25a4 LL) at utils.c:832 #8 0x08354773 in target_thread_address_space (ptid=...) at target.c:2642 #9 0x0834dd24 in tdefault_trace_init (self=0x92982c0 dummy_target) at target-delegates.c:964 #10 0x0834dd24 in tdefault_trace_init (self=0x92c5d40 exec_ops) at target-delegates.c:964 #11 0x0834dd24 in tdefault_trace_init (self=0x298ba500) at target-delegates.c:964 #12 0x0834dd24 in tdefault_trace_init (self=0x9290400 fbsd_thread_ops) at target-delegates.c:964 #13 0x083547ab in target_thread_address_space (ptid=...) at target.c:2645 #14 0x082b2227 in ?? () at regcache.c:491 #15 0x082b231a in regcache_observer_target_changed (target=0x8999254) at regcache.c:520 #16 0x0830b960 in thread_still_needs_step_over (tp=0x29a02900) at infrun.c:2110 #17 0x08311beb in keep_going (ecs=0xbfbfe138) at infrun.c:5809 #18 0x0830f842 in process_event_stop_test (ecs=0xbfbfe138) at infrun.c:4590 #19 0x0830f292 in process_event_stop_test (ecs=0xbfbfe138) at infrun.c:4349 #20 0x0830e525 in handle_inferior_event (ecs=0xbfbfe138) at infrun.c:3830 #21 0x0830ca66 in fetch_inferior_event (client_data=0x298ba500) at infrun.c:2865 #22 0x0830bfa8 in start_remote (from_tty=674835856) at infrun.c:2423 #23 0x08304d1c in ?? () at infcmd.c:641 #24 0x08304d50 in start_command (args=0x0, from_tty=1) at infcmd.c:660 #25 0x0823b41b in do_sfunc (c=0x299d1350, args=0x0, from_tty=1) at ./cli/cli-decode.c:123 #26 0x0823e241 in multi_line_command_p (type=698159952) at ./cli/cli-script.c:97 #27 0x08419253 in execute_command (p=0x2983b081 , from_tty=1) at top.c:482 #28 0x0832c821 in command_line_handler (rl=0x2983b080 ) at event-top.c:460 #29 0x0832cd73 in gdb_readline2 (client_data=0x2983d134) at event-top.c:653 #30 0x2912a117 in rl_callback_read_char () from /usr/local/lib/libreadline.so.6 #31 0x0832c3ab in change_line_handler () at event-top.c:200 #32 0x0832c712 in async_disable_stdin () at event-top.c:399 #33 0xbfbfe6ac in ?? () (gdb) q % uname -a FreeBSD entw-pr2.demig.intra 9.1-RELEASE FreeBSD 9.1-RELEASE #2: Wed Feb 6 17:03:36 CET 2013 root@entw-pr2.demig.intra:/usr/obj/usr/src/sys/ENTW-PR2 i386 Best regards, Norbert Koch ___ 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
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-140813 +-+ net-mgmt/pandorafms_console | 4.0.1 | 5.1-140813 +-+ net-mgmt/pandorafms_server | 4.0.1 | 5.1-140813 +-+ www/groupoffice | 3.7.24 | 6.0.12 +-+ 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
Ports marked IGNORE
Wed, 13 Aug 2014 07:03:19 -0400 While running portupgrade -a, I found the following ports were marked as IGNORE: - print/acroread9 (marked as IGNORE) - ftp/linux-f10-curl (marked as IGNORE) - textproc/linux-f10-expat (marked as IGNORE) - security/linux-f10-gnutls (marked as IGNORE) - security/linux-f10-libgcrypt (marked as IGNORE) - textproc/linux-f10-libxml2 (marked as IGNORE) - security/linux-f10-nss (marked as IGNORE) - net/linux-f10-openldap (marked as IGNORE) - security/linux-f10-openssl (marked as IGNORE) - graphics/linux-f10-png (marked as IGNORE) - graphics/linux-f10-tiff (marked as IGNORE) Are there any plains to update/correct these programs? Also, what is suppose to replace print/acroread9? I need that program or something that works similar to it. I know, or at least have never found any program that works like Adobe Acrobat does on FreeBSD, but at least I need the functionality of regular Adobe for working with PDF files. -- Jerry signature.asc Description: PGP signature
Choosing a port category for a new port
Hi, I've create a port for authbind, and am unsure which category or categories to pick for it. [pkg-desc] Authbind allows a program which does not or should not run as root to bind to low-numbered ports in a controlled way. In most cases, you will probably want to use mac_portacl(4) instead of authbind. WWW: http://www.chiark.greenend.org.uk/ucgi/~ian/git/authbind.git/ [pkg-desc] My current choice of categories would be: CATEGORY= net security What's the lists opinion on the main category and eventual secondary categories for this new port ? MfG CoCo ___ 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 marked IGNORE
Hi! While running portupgrade -a, I found the following ports were marked as IGNORE: - print/acroread9 (marked as IGNORE) - ftp/linux-f10-curl (marked as IGNORE) - textproc/linux-f10-expat (marked as IGNORE) - security/linux-f10-gnutls (marked as IGNORE) - security/linux-f10-libgcrypt (marked as IGNORE) - textproc/linux-f10-libxml2 (marked as IGNORE) - security/linux-f10-nss (marked as IGNORE) - net/linux-f10-openldap (marked as IGNORE) - security/linux-f10-openssl (marked as IGNORE) - graphics/linux-f10-png (marked as IGNORE) - graphics/linux-f10-tiff (marked as IGNORE) Are there any plains to update/correct these programs? Not those, they are part of really ancient linux packages which provide part of a linux emulation environment. f10 == Fedora 10. Here is more info on the state of the linux emu, there is work being done to update it to fedora 19 or 20, centos 6 or 7 and some more recent linux-kernel emulation (even for 64bit linux). https://wiki.freebsd.org/201407DevSummit/LinuxEmulation Also, what is suppose to replace print/acroread9? I need that program or something that works similar to it. Acrobat itself no longer supports acroread9, and 10+11 are not provided for linux anymore. So: It's a real issue, and I know no solution. I use xpdf for most PDF stuff. There are other PDF display programs but as far as I understand, most use the same core (poppler). There is graphics/mupdf, which probably uses a different core, maybe it does what you need ? -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ImageMagic + Webp
I'm seeing the same problem on my 9.3-RELEASE box. Interestingly enough however, it builds on my 9.2-RELEASE box. I've attached the builds for both. -scott On 08/12/14 01:44, Robert Backhaus wrote: I have the same issue here. Sunpoet, do you have this? I have attached a script of my failure. FreeBSD boffin 9.3-STABLE FreeBSD 9.3-STABLE #1 r268979: Tue Jul 22 22:42:39 EST 2014 root@boffin:/usr/obj/home/src/sys/GENERIC amd64 On 11 August 2014 18:45, Jos Chrispijn po...@webrz.net wrote: After I installed ImageMagic port, I got stuck at the installation of Webp: === Building for webp-0.4.1 Making all in src Making all in dec Making all in enc Making all in dsp CC libwebpdspdecode_sse2_la-lossless_sse2.lo lossless_sse2.c: In function 'ConvertBGRAToBGR': lossless_sse2.c:403: note: use -flax-vector-conversions to permit conversions between vectors with differing element types or numbers of subparts lossless_sse2.c:403: error: incompatible type for argument 1 of '__builtin_ia32_psrlqi128' lossless_sse2.c:404: error: incompatible type for argument 1 of '__builtin_ia32_psrlqi128' *** [libwebpdspdecode_sse2_la-lossless_sse2.lo] Error code 1 1 error *** [all-recursive] Error code 1 1 error *** [all-recursive] Error code 1 1 error === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** [do-build] Error code 1 Stop in /usr/ports/graphics/webp. *** [install] Error code 1 Stop in /usr/ports/graphics/webp. *** [reinstall] Error code 1 Stop in /usr/ports/graphics/webp. --- end of text -- Can you tell me how to solve? Thanks, Jos Chrispijn ___ 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 ]0;portmaster: webp-0.4.1 === Currently installed version: webp-0.4.1 === Port directory: /usr/ports/graphics/webp === Gathering distinfo list for installed ports === Launching 'make checksum' for graphics/webp in background === Gathering dependency list for graphics/webp from ports === Initial dependency check complete for graphics/webp ]0;portmaster: webp-0.4.1 === Starting build for graphics/webp === === All dependencies are up to date === Cleaning for webp-0.4.1 === Waiting on fetch checksum for graphics/webp === === License BSD3CLAUSE accepted by the user === Found saved configuration for webp-0.3.1_4 === webp-0.4.1 depends on file: /usr/local/sbin/pkg - found === Fetching all distfiles required by webp-0.4.1 for building === Extracting for webp-0.4.1 = SHA256 Checksum OK for libwebp-0.4.1.tar.gz. === Patching for webp-0.4.1 === webp-0.4.1 depends on shared library: libgif.so - found (/usr/local/lib/libgif.so.5) === webp-0.4.1 depends on shared library: libjpeg.so - found (/usr/local/lib/libjpeg.so.11) === webp-0.4.1 depends on shared library: libpng15.so - found (/usr/local/lib/libpng15.so.15) === webp-0.4.1 depends on shared library: libtiff.so - found (/usr/local/lib/libtiff.so.4) === Configuring for webp-0.4.1 configure: loading site script /usr/ports/Templates/config.site checking build system type... amd64-portbld-freebsd9.2 checking host system type... amd64-portbld-freebsd9.2 checking target system type... amd64-portbld-freebsd9.2 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p checking for gawk... (cached) /usr/bin/awk checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking for gcc... cc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking dependency style of cc... gcc3 checking for ar... ar checking the archiver (ar) interface... ar checking how to print strings... printf checking for a sed that does not truncate output... (cached) /usr/bin/sed checking for grep that handles long lines and -e... (cached) /usr/bin/grep checking for egrep... (cached) /usr/bin/egrep checking for fgrep... (cached) /usr/bin/fgrep checking for ld used by cc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)...
Adventures in ports, chapter 364135
mail/thunderbird does not compile on 8.4-STABLE because base gcc is too
old. Adding USE_GCC= 4.7+ fixes the issue, but then of course it
won't compile on a system without gcc at all. Is there an idiom to say
Use clang, but if you use gcc, use at least 4.7?
portmaster and databases/firebird25-client don't work well together; I
encountered the config dialog multiple times in the course of one build.
Presumably some step of the build is deleting the cached option file.
It would be nice for devel/qt5 to have a more granular database option
than the all-in-one; something like:
OPTIONS_DEFINE= SQL_IBASE SQL_MYSQL SQL_ODBC SQL_POSTGRES SQL_SQLITE2 \
SQL_SQLITE3 TOOLS
SQL_PLUGINS_USE=
.if ${PORT_OPTIONS:MIBASE}
SQL_PLUGINS_USE=sql-ibase
.endif
.if ${PORT_OPTIONS:MMYSQL}
SQL_PLUGINS_USE=sql-mysql
.endif
.if ${PORT_OPTIONS:MODBC}
SQL_PLUGINS_USE=sql-odbc
.endif
.if ${PORT_OPTIONS:MPOSTGRES}
SQL_PLUGINS_USE=sql-pgsql
.endif
.if ${PORT_OPTIONS:MSQLITE2}
SQL_PLUGINS_USE=sql-sqlite2
.endif
.if ${PORT_OPTIONS:MSQLITE3}
SQL_PLUGINS_USE=sql-sqlite3
.endif
It was a bit of a shock to get mysql, odbc, and sqlite2 built when all I
am really interested in are postgres and sqlite3! -- George
___
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: Adventures in ports, chapter 364135
It would be nice for devel/qt5 to have a more granular database option
than the all-in-one; something like:
OPTIONS_DEFINE= SQL_IBASE SQL_MYSQL SQL_ODBC SQL_POSTGRES SQL_SQLITE2 \
SQL_SQLITE3 TOOLS
SQL_PLUGINS_USE=
.if ${PORT_OPTIONS:MIBASE}
SQL_PLUGINS_USE=sql-ibase
Of course, this should have said SQL_PLUGINS_USE+=sql-ibase (etc.).
.endif
[...]
___
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
[Bug 192069] pkgng has removed package install dates for everything that was installed before today
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192069 Gavin Atkinson ga...@freebsd.org changed: What|Removed |Added Status|Needs Triage|Issue Resolved Resolution|--- |FIXED Assignee|freebsd-b...@freebsd.org|freebsd-ports@FreeBSD.org --- Comment #4 from Gavin Atkinson ga...@freebsd.org --- Thanks for the report, this was indeed a bug in 1.3.0 and was fixed in 1.3.1. Unfortunately for anybody who used 1.3.0, there is no way to get the installed timestamps back without resorting to making use of a backup of the package database. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: redports and build status
On Wed, Aug 13, 2014 at 12:39 PM, Tijl Coosemans t...@freebsd.org wrote: On Wed, 13 Aug 2014 09:49:31 +0200 Bernhard Fröhlich wrote: On Tue, Aug 12, 2014 at 8:54 PM, Tijl Coosemans t...@freebsd.org wrote: On Tue, 12 Aug 2014 19:38:27 +0200 Fernando Apesteguía wrote: I built a port in redports and I received a mail notifying that the builds were finished, but it seems redports couldn't figure out if the builds finished successfully. https://redports.org/buildarchive/20140812170901-30860 Any ideas of why this happened? Thanks in advance. I'm seeing a lot of these as well. CCing decke@ Yeah, the finished state is some rescue state in case something went terribly wrong. Usually this happens when something inside redports fails or some backend behaves very weird or if the port creates some very strange situation like a recursive dependency (which fills up a temporary partition and then fails). If only one of many jobs fails then chances are good that it is some redports weirdness. If many jobs fail (like in this case) and it is reproducible then the chances are good that your port is doing something very very bad. I'm seeing these on multiple unrelated ports and with trivial changes. I've now cleared my redports tree, leaving only one unmodified port and it still results in all 'finished'. Maybe redport's internal ports tree got corrupt or one of its cached packages? Mine is modified but nothing to do with dependencies or such. However this problem is reproducible. This is the port: https://redports.org/browser/fernape/lang/basic256?rev=30358 I don't see very bad things there or at least not compared with the previous revision which finished with success Can you think of anything I can try? I'm willing to help. I got used to run successfully tests in redports to attach them to my PR's and I don't want to update this port until it builds properly. 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
net-im/skype-[devel] won't connect
Hello. This afternoon when I try to sign onto Skype, I get: Periodic UIC Update Failed I haven't updated ports recently. Does anyone have an idea? I heard Skype was closing down old versions. ___ 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-im/skype-[devel] won't connect
On Wed, Aug 13, 2014 at 10:38 AM, Kenta S. ken...@hush.com wrote: Hello. This afternoon when I try to sign onto Skype, I get: Periodic UIC Update Failed I haven't updated ports recently. Does anyone have an idea? I heard Skype was closing down old versions. I had received the following e-mail from Skype a few days ago: On Fri, Aug 8, 2014 at 7:53 PM, Skype norep...@emails.skype.com wrote: Your Skype for Linux version is being retired. Update today. » Can't see this email properly? Forgotten your password? Your Skype for Linux version is being retired. Update today. Dear swhetzel, We are now retiring older versions of Skype and it appears that at some point you signed into Skype with one of these. To continue signing into Skype on Linux you'll need to download the latest version. The new version comes with improved performance, the latest features and security updates, so you'll get the best possible Skype experience. If you're on the latest version of Skype, the above will not apply. Update now at http://www.skype.com/download. Someone will need to update the Skype port to the latest Linux version and see if it works on our current version of Linux emulation. -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. ___ 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: [BUG] GDB port bug report due to login problems with Bugzilla
Hi Norbert, I installed a i386 10.0 system and I can debug with gdb78. I've built gdb-7.8_1 and used it to debug a hello world. It worked. I ran gdb78 to debug gdb78 debugging a hello world. It worked. In other words, here is everything fine. The error you show is quite strange: the whole trace is quite a messy: the function tdefault_trace_init, showed 4 times, is not even called, as the first resolved function async_disable_stdin. I guess that the crash has corrupted the core dump in some way... At the moment, I cannot install a FreeBSD 9.1 system, but I will try next days. Could you give me also the port's configuration? Some special configuration in make.conf? Compiler used to build gdb? Thanks in advance best regards, pizzamig On Wed, Aug 13, 2014 at 12:55 PM, Luca Pizzamiglio luca.pizzamig...@gmail.com wrote: Hi Norbert, it could be a problem related to i386, because on amd64 it works perfectly. I'll try to get a i386 system and test it more deeply. thanks for the help best regards, pizzamig On Wed, Aug 13, 2014 at 11:42 AM, Norbert Koch nk...@demig.de wrote: Hello. As I am not able to login to Bugzilla to report a bug (502 Bad Gateway from nginx?) I would like to inform you here about a bug in devel/gdb. Since before updating to 7.8.1 I had no problems. Now with latest patch to fbsd-threads.c (R 364713) gdb crashes with the first run command. % gdb78 `which gdb78`gdb78.core GNU gdb (GDB) 7.8 [GDB v7.8 for FreeBSD] Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i386-portbld-freebsd9.1. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from /usr/local/bin/gdb78...done. [New process 100614] Core was generated by `gdb78'. Program terminated with signal SIGABRT, Aborted. #0 0x293c73f7 in kill () from /lib/libc.so.7 (gdb) bt #0 0x293c73f7 in kill () from /lib/libc.so.7 #1 0x293c7316 in raise () from /lib/libc.so.7 #2 0x293c5d9a in abort () from /lib/libc.so.7 #3 0x0841ba8a in can_dump_core (reason=0x89f49b0 DB does when %s is detected.) at utils.c:630 #4 0x0841bdb1 in internal_verror ( file=0x299dca80 target.c:2626: internal-error: Can't determine the current address space of thread LWP 1\n\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable., line=144656744, fmt=0x89f49cf , ap=0x299e8c00 (y or n) ) at utils.c:802 #5 0x089f49b0 in ?? () #6 0x0841be1e in ?? () at utils.c:813 #7 0x0841be5c in internal_warning ( file=0x89d1947 col of the target machine.\nRemaining arguments are interpreted by the target protocol. For more\ninformation on the arguments for a particular protocol, type\n`help target ' followed by the protocol na..., line=2626, string=0x89d25a4 LL) at utils.c:832 #8 0x08354773 in target_thread_address_space (ptid=...) at target.c:2642 #9 0x0834dd24 in tdefault_trace_init (self=0x92982c0 dummy_target) at target-delegates.c:964 #10 0x0834dd24 in tdefault_trace_init (self=0x92c5d40 exec_ops) at target-delegates.c:964 #11 0x0834dd24 in tdefault_trace_init (self=0x298ba500) at target-delegates.c:964 #12 0x0834dd24 in tdefault_trace_init (self=0x9290400 fbsd_thread_ops) at target-delegates.c:964 #13 0x083547ab in target_thread_address_space (ptid=...) at target.c:2645 #14 0x082b2227 in ?? () at regcache.c:491 #15 0x082b231a in regcache_observer_target_changed (target=0x8999254) at regcache.c:520 #16 0x0830b960 in thread_still_needs_step_over (tp=0x29a02900) at infrun.c:2110 #17 0x08311beb in keep_going (ecs=0xbfbfe138) at infrun.c:5809 #18 0x0830f842 in process_event_stop_test (ecs=0xbfbfe138) at infrun.c:4590 #19 0x0830f292 in process_event_stop_test (ecs=0xbfbfe138) at infrun.c:4349 #20 0x0830e525 in handle_inferior_event (ecs=0xbfbfe138) at infrun.c:3830 #21 0x0830ca66 in fetch_inferior_event (client_data=0x298ba500) at infrun.c:2865 #22 0x0830bfa8 in start_remote (from_tty=674835856) at infrun.c:2423 #23 0x08304d1c in ?? () at infcmd.c:641 #24 0x08304d50 in start_command (args=0x0, from_tty=1) at infcmd.c:660 #25 0x0823b41b in do_sfunc (c=0x299d1350, args=0x0, from_tty=1) at ./cli/cli-decode.c:123 #26 0x0823e241 in multi_line_command_p (type=698159952) at ./cli/cli-script.c:97 #27 0x08419253 in execute_command (p=0x2983b081 , from_tty=1) at top.c:482 #28 0x0832c821 in command_line_handler (rl=0x2983b080 ) at event-top.c:460 #29 0x0832cd73 in gdb_readline2 (client_data=0x2983d134) at
Re: redports and build status
On Wednesday 13 August 2014 17:11:28 Fernando Apesteguía wrote: On Wed, Aug 13, 2014 at 12:39 PM, Tijl Coosemans t...@freebsd.org wrote: On Wed, 13 Aug 2014 09:49:31 +0200 Bernhard Fröhlich wrote: On Tue, Aug 12, 2014 at 8:54 PM, Tijl Coosemans t...@freebsd.org wrote: On Tue, 12 Aug 2014 19:38:27 +0200 Fernando Apesteguía wrote: I built a port in redports and I received a mail notifying that the builds were finished, but it seems redports couldn't figure out if the builds finished successfully. https://redports.org/buildarchive/20140812170901-30860 Any ideas of why this happened? Thanks in advance. I'm seeing a lot of these as well. CCing decke@ Yeah, the finished state is some rescue state in case something went terribly wrong. Usually this happens when something inside redports fails or some backend behaves very weird or if the port creates some very strange situation like a recursive dependency (which fills up a temporary partition and then fails). If only one of many jobs fails then chances are good that it is some redports weirdness. If many jobs fail (like in this case) and it is reproducible then the chances are good that your port is doing something very very bad. I'm seeing these on multiple unrelated ports and with trivial changes. I've now cleared my redports tree, leaving only one unmodified port and it still results in all 'finished'. Maybe redport's internal ports tree got corrupt or one of its cached packages? Mine is modified but nothing to do with dependencies or such. However this problem is reproducible. This is the port: https://redports.org/browser/fernape/lang/basic256?rev=30358 I don't see very bad things there or at least not compared with the previous revision which finished with success Can you think of anything I can try? I'm willing to help. I got used to run successfully tests in redports to attach them to my PR's and I don't want to update this port until it builds properly. Regards http://forums.freebsd.org/viewtopic.php?f=22t=44800start=75 -- ajtiM http://www.redbubble.com/people/lumiwa ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: redports and build status
On Wed, Aug 13, 2014 at 5:50 PM, Ajtim lum...@gmail.com wrote: On Wednesday 13 August 2014 17:11:28 Fernando Apesteguía wrote: On Wed, Aug 13, 2014 at 12:39 PM, Tijl Coosemans t...@freebsd.org wrote: On Wed, 13 Aug 2014 09:49:31 +0200 Bernhard Fröhlich wrote: On Tue, Aug 12, 2014 at 8:54 PM, Tijl Coosemans t...@freebsd.org wrote: On Tue, 12 Aug 2014 19:38:27 +0200 Fernando Apesteguía wrote: I built a port in redports and I received a mail notifying that the builds were finished, but it seems redports couldn't figure out if the builds finished successfully. https://redports.org/buildarchive/20140812170901-30860 Any ideas of why this happened? Thanks in advance. I'm seeing a lot of these as well. CCing decke@ Yeah, the finished state is some rescue state in case something went terribly wrong. Usually this happens when something inside redports fails or some backend behaves very weird or if the port creates some very strange situation like a recursive dependency (which fills up a temporary partition and then fails). If only one of many jobs fails then chances are good that it is some redports weirdness. If many jobs fail (like in this case) and it is reproducible then the chances are good that your port is doing something very very bad. I'm seeing these on multiple unrelated ports and with trivial changes. I've now cleared my redports tree, leaving only one unmodified port and it still results in all 'finished'. Maybe redport's internal ports tree got corrupt or one of its cached packages? Mine is modified but nothing to do with dependencies or such. However this problem is reproducible. This is the port: https://redports.org/browser/fernape/lang/basic256?rev=30358 I don't see very bad things there or at least not compared with the previous revision which finished with success Can you think of anything I can try? I'm willing to help. I got used to run successfully tests in redports to attach them to my PR's and I don't want to update this port until it builds properly. Regards http://forums.freebsd.org/viewtopic.php?f=22t=44800start=75 Sorry, but I don't see how that thread is related to this one... -- ajtiM http://www.redbubble.com/people/lumiwa ___ 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
SUHOSIN option on lang/php53
Just wondering: since security/php-suhosin won't build on PHP 5.3, why is there still an option for Suhosin in the lang/php53 port? http://svnweb.freebsd.org/ports/head/security/php-suhosin/Makefile?r1=349250r2=349251; ___ 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: SUHOSIN option on lang/php53
Hi! Just wondering: since security/php-suhosin won't build on PHP 5.3, why is there still an option for Suhosin in the lang/php53 port? http://svnweb.freebsd.org/ports/head/security/php-suhosin/Makefile?r1=349250r2=349251; Because no-one noticed and send a patch/PR 8-} ? -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote: On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of Dennis Glatting, and lo! it spake thus: do_install in the Makefile does the chown. Generally you'd want to do something more like using @owner/@group in plist, rather than chown'ing in the stage. Doing that would break building as non-root, too. What's the order? plist cannot change owner/group unless it is defined. Or, does plist execution happen /after/ the make process creates the owner/group entries? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
Hi! On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote: On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of Dennis Glatting, and lo! it spake thus: do_install in the Makefile does the chown. Generally you'd want to do something more like using @owner/@group in plist, rather than chown'ing in the stage. Doing that would break building as non-root, too. What's the order? plist cannot change owner/group unless it is defined. Or, does plist execution happen /after/ the make process creates the owner/group entries? If you some file bin/myfile1 in the pkg-plist which need to be owned by some user etc, then: [...] bin/myfile0 @owner www @group www bin/myfile1 @owner root @group wheel bin/myfile2 [...] should probably work. Can you try it ? -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ImageMagic + Webp
On 12 Aug 2014, at 07:44, Robert Backhaus rob...@robbak.com wrote: On 11 August 2014 18:45, Jos Chrispijn po...@webrz.net wrote: After I installed ImageMagic port, I got stuck at the installation of Webp: === Building for webp-0.4.1 Making all in src Making all in dec Making all in enc Making all in dsp CC libwebpdspdecode_sse2_la-lossless_sse2.lo lossless_sse2.c: In function 'ConvertBGRAToBGR': lossless_sse2.c:403: note: use -flax-vector-conversions to permit conversions between vectors with differing element types or numbers of subparts lossless_sse2.c:403: error: incompatible type for argument 1 of '__builtin_ia32_psrlqi128' lossless_sse2.c:404: error: incompatible type for argument 1 of '__builtin_ia32_psrlqi128' *** [libwebpdspdecode_sse2_la-lossless_sse2.lo] Error code 1 [...] I have the same issue here. Sunpoet, do you have this? I have attached a script of my failure. FreeBSD boffin 9.3-STABLE FreeBSD 9.3-STABLE #1 r268979: Tue Jul 22 22:42:39 EST 2014 root@boffin:/usr/obj/home/src/sys/GENERIC amd64 This is a bug in gcc's emmintrin.h header. I have committed a fix to head in r269948, and I will merge it to stable/10 and stable/9 in three days. Meanwhile, please apply the attached diff to emmintrin.h in /usr/include/gcc/4.2 manually. -Dimitry fix-mm_srli_epi64-cast-1.diff Description: Binary data signature.asc Description: Message signed with OpenPGP using GPGMail
Re: redports and build status
On Wed, Aug 13, 2014 at 6:16 PM, Fernando Apesteguía fernando.apesteg...@gmail.com wrote: On Wed, Aug 13, 2014 at 5:50 PM, Ajtim lum...@gmail.com wrote: On Wednesday 13 August 2014 17:11:28 Fernando Apesteguía wrote: On Wed, Aug 13, 2014 at 12:39 PM, Tijl Coosemans t...@freebsd.org wrote: On Wed, 13 Aug 2014 09:49:31 +0200 Bernhard Fröhlich wrote: On Tue, Aug 12, 2014 at 8:54 PM, Tijl Coosemans t...@freebsd.org wrote: On Tue, 12 Aug 2014 19:38:27 +0200 Fernando Apesteguía wrote: I built a port in redports and I received a mail notifying that the builds were finished, but it seems redports couldn't figure out if the builds finished successfully. https://redports.org/buildarchive/20140812170901-30860 Any ideas of why this happened? Thanks in advance. I'm seeing a lot of these as well. CCing decke@ Yeah, the finished state is some rescue state in case something went terribly wrong. Usually this happens when something inside redports fails or some backend behaves very weird or if the port creates some very strange situation like a recursive dependency (which fills up a temporary partition and then fails). If only one of many jobs fails then chances are good that it is some redports weirdness. If many jobs fail (like in this case) and it is reproducible then the chances are good that your port is doing something very very bad. I'm seeing these on multiple unrelated ports and with trivial changes. I've now cleared my redports tree, leaving only one unmodified port and it still results in all 'finished'. Maybe redport's internal ports tree got corrupt or one of its cached packages? Mine is modified but nothing to do with dependencies or such. However this problem is reproducible. This is the port: https://redports.org/browser/fernape/lang/basic256?rev=30358 I don't see very bad things there or at least not compared with the previous revision which finished with success Can you think of anything I can try? I'm willing to help. I got used to run successfully tests in redports to attach them to my PR's and I don't want to update this port until it builds properly. Just tried another port and it finished without being able to figure out the outcome of the building process. The differences between the revision that worked and the one that didn't, are trivial: https://redports.org/changeset/30460/fernape Cheers. Regards http://forums.freebsd.org/viewtopic.php?f=22t=44800start=75 Sorry, but I don't see how that thread is related to this one... -- ajtiM http://www.redbubble.com/people/lumiwa ___ 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-im/skype-[devel] won't connect
On Wed, 13 Aug 2014 11:38:23 -0400 Kenta S. wrote: Hello. This afternoon when I try to sign onto Skype, I get: Periodic UIC Update Failed I haven't updated ports recently. Does anyone have an idea? I heard Skype was closing down old versions. I don't use it but https://github.com/xmj/linux-ports has Skype 4.2.0.13. -- Herbert ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
On 2014-08-13 18:37, Dennis Glatting wrote: On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote: On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of Dennis Glatting, and lo! it spake thus: do_install in the Makefile does the chown. Generally you'd want to do something more like using @owner/@group in plist, rather than chown'ing in the stage. Doing that would break building as non-root, too. What's the order? plist cannot change owner/group unless it is defined. Or, does plist execution happen /after/ the make process creates the owner/group entries? In case the port defines USERS and GROUPS from ports/(U|G)IDs, then this GROUPS/USERS are created in a early step during port / packet installation and they are available before pkg-plist is processed. USERS= $user (list) from UIDs GROUPS= $group (list) from GIDs In case the port requires user / group not in UIDs/GIDs then request an entry for them. -- 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: redports and build status
On Wed, 13 Aug 2014 17:11:28 +0200 Fernando Apestegu=C3=ADa wrote: Mine is modified but nothing to do with dependencies or such. However this problem is reproducible. This is the port: https://redports.org/browser/fernape/lang/basic256?rev=3D30358 I don't see very bad things there or at least not compared with the previous revision which finished with success Can you think of anything I can try? I'm willing to help. I got used to run successfully tests in redports to attach them to my PR's and I don't want to update this port until it builds properly. Regards Hi Fernando, It's just a shot in the dark, but try to delete the content of your SVN repository then re-add all your ports again. Cheers, -- Carlos Jacobo Puga Medina c...@fbsd.es ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
On Wed, 2014-08-13 at 18:43 +0200, Kurt Jaeger wrote: Hi! On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote: On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of Dennis Glatting, and lo! it spake thus: do_install in the Makefile does the chown. Generally you'd want to do something more like using @owner/@group in plist, rather than chown'ing in the stage. Doing that would break building as non-root, too. What's the order? plist cannot change owner/group unless it is defined. Or, does plist execution happen /after/ the make process creates the owner/group entries? If you some file bin/myfile1 in the pkg-plist which need to be owned by some user etc, then: [...] bin/myfile0 @owner www @group www bin/myfile1 @owner root @group wheel bin/myfile2 [...] should probably work. Can you try it ? I am setting permissions on directories and the man page for pkg-create isn't clear. It says: @owner user Set default ownership for all subsequent files to user. Use without an arg to set back to default (root) ownership. Perhaps it means files in the generic? Another issue I is the directories are made in the Makefile (do_install) because pkg-create doesn't mention a mkdir function. The Porter's Handbook mentions @exec mkdir however the StageDir WIKI states it is ignored and directory creation should remain in post-install, specifically: Directory creation should remain in the post-install: target (in particular because pkgng doesn't work like pkg_install in that area and pkgng ignores the @exec mkdir, and directly packs the directory even if empty). Consequently, I have no idea how to set the owner/group on those directories in stagedir. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Redports, broken regression tests and missing check-orphans
Am 13.08.2014 12:10 schrieb Vitaly Magerya vmage...@gmail.com:
Bernhard, while we're at it, there are currently two problems with
redports which diminish it's usefulness significantly:
1. Redports used to run make regression-test on every build; right now,
each log has this instead:
phase 5: make test
[: -eq: unexpected operator
=== Regression tests skipped. ===
So, no regression tests are executed. I don't know what the problem is
here.
2. Most ports now have stage support; this means that checking for
leftover files under ${PREFIX} is close to useless: only files in pkg-plist
are copied there. Instead, leftovers should be searched for in ${STAGEDIR}
-- running make stage-qa and make check-orphans with every build would
do that.
(I've already botched two patches when I assumed that successful redports
run means that pkg-plist is complete).
So, can the first problem be fixed and the second suggestion implemented?
Should I be bothering tinderbox author(s) instead?
I am not sure where the first issue is coming from but the second is
definitely a tinderbox task. We are asking for tinderbox staging and modern
leftover checks for some time already. I am working on a poudriere
migration but it's quite a moving target and it requires quite a bit of
work.
___
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: SUHOSIN option on lang/php53
On 13/08/14 18:32, Kurt Jaeger wrote: Hi! Just wondering: since security/php-suhosin won't build on PHP 5.3, why is there still an option for Suhosin in the lang/php53 port? http://svnweb.freebsd.org/ports/head/security/php-suhosin/Makefile?r1=349250r2=349251; Because no-one noticed and send a patch/PR 8-} ? No, they are 2 different things. One is the Suhosin patch, one the extension. http://suhosin.org/stories/index.html Florian signature.asc Description: OpenPGP digital signature
Re: ImageMagic + Webp
On Thu, Aug 14, 2014 at 12:53 AM, Dimitry Andric d...@freebsd.org wrote: On 12 Aug 2014, at 07:44, Robert Backhaus rob...@robbak.com wrote: On 11 August 2014 18:45, Jos Chrispijn po...@webrz.net wrote: After I installed ImageMagic port, I got stuck at the installation of Webp: === Building for webp-0.4.1 Making all in src Making all in dec Making all in enc Making all in dsp CC libwebpdspdecode_sse2_la-lossless_sse2.lo lossless_sse2.c: In function 'ConvertBGRAToBGR': lossless_sse2.c:403: note: use -flax-vector-conversions to permit conversions between vectors with differing element types or numbers of subparts lossless_sse2.c:403: error: incompatible type for argument 1 of '__builtin_ia32_psrlqi128' lossless_sse2.c:404: error: incompatible type for argument 1 of '__builtin_ia32_psrlqi128' *** [libwebpdspdecode_sse2_la-lossless_sse2.lo] Error code 1 [...] I have the same issue here. Sunpoet, do you have this? I have attached a script of my failure. FreeBSD boffin 9.3-STABLE FreeBSD 9.3-STABLE #1 r268979: Tue Jul 22 22:42:39 EST 2014 root@boffin:/usr/obj/home/src/sys/GENERIC amd64 This is a bug in gcc's emmintrin.h header. I have committed a fix to head in r269948, and I will merge it to stable/10 and stable/9 in three days. Meanwhile, please apply the attached diff to emmintrin.h in /usr/include/gcc/4.2 manually. -Dimitry Hi dim, Thanks for your explanation. I've posted the information to ports/192600 and ports/192637. Regards, sunpoet ___ 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
emulators/linux_base-f10 poudriere (3.1pre)
Hello,
I' building my ports with poudriere 3.1pre on head. The port
emulators/linux_base-f10 can not be build due to a problem with one file
listed in the Makefile which seems to not exist anymore (or at least not
with the correct SHA256 signature and filesize). What makes me wonder is
that the file gamin-0.1.9-6.fc10.src.rpm itself is not used to build the
port, poudriere only stops because it can not fetch this file;
If one builds the port normal (with make install) the missing file is
not an issue and the port just installs fine.
The file in question is in the Makefile in the list of SRC_DISTFILES
which is part of DISTFILES:
DISTFILES= ${BIN_DISTFILES} ${SRC_DISTFILES}
and only the files in BIN_DISTFILES are used to build the port.
If I comment out the single file, poudriere is happy.
Why the normal 'make install' can build the port and poudriere can not?
Thanks
matthias
diff -c
/usr/local/poudriere/ports/ports-head/emulators/linux_base-f10/Makefile*
***
/usr/local/poudriere/ports/ports-head/emulators/linux_base-f10/Makefile
2014-08-13 19:10:04.0 +0200
---
/usr/local/poudriere/ports/ports-head/emulators/linux_base-f10/Makefile.orig
2014-08-09 12:45:52.0 +0200
***
*** 75,80
--- 75,81
fedora-release-10-1.src.rpm \
filesystem-2.4.19-1.fc10.src.rpm \
freetype-2.3.7-1.fc10.src.rpm \
+ gamin-0.1.9-6.fc10.src.rpm \
gcc-4.3.2-7.src.rpm \
gdbm-1.8.0-29.fc10.src.rpm \
glib-1.2.10-32.fc10.src.rpm \
--
Matthias Apitz | /\ ASCII Ribbon Campaign:
E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ | X- No proprietary attachments
phone: +49-170-4527211 | / \ - Respect for open standards
| en.wikipedia.org/wiki/ASCII_Ribbon_Campaign
___
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-im/skype-[devel] won't connect
On Wednesday 13 August 2014 18:28:08 Herbert J. Skuhra wrote: On Wed, 13 Aug 2014 11:38:23 -0400 Kenta S. wrote: Hello. This afternoon when I try to sign onto Skype, I get: Periodic UIC Update Failed I haven't updated ports recently. Does anyone have an idea? I heard Skype was closing down old versions. I don't use it but https://github.com/xmj/linux-ports has Skype 4.2.0.13. -- Herbert ___ 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 http://forums.freebsd.org/viewtopic.php?f=22t=44800start=75 -- ajtiM http://www.redbubble.com/people/lumiwa ___ 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: ImageMagic + Webp
Am 13.08.2014 um 20:20 schrieb Sunpoet Po-Chuan Hsieh: On Thu, Aug 14, 2014 at 12:53 AM, Dimitry Andric d...@freebsd.org wrote: On 12 Aug 2014, at 07:44, Robert Backhaus rob...@robbak.com wrote: On 11 August 2014 18:45, Jos Chrispijn po...@webrz.net wrote: After I installed ImageMagic port, I got stuck at the installation of Webp: === Building for webp-0.4.1 Making all in src Making all in dec Making all in enc Making all in dsp CC libwebpdspdecode_sse2_la-lossless_sse2.lo lossless_sse2.c: In function 'ConvertBGRAToBGR': lossless_sse2.c:403: note: use -flax-vector-conversions to permit conversions between vectors with differing element types or numbers of subparts lossless_sse2.c:403: error: incompatible type for argument 1 of '__builtin_ia32_psrlqi128' lossless_sse2.c:404: error: incompatible type for argument 1 of '__builtin_ia32_psrlqi128' *** [libwebpdspdecode_sse2_la-lossless_sse2.lo] Error code 1 [...] I have the same issue here. Sunpoet, do you have this? I have attached a script of my failure. FreeBSD boffin 9.3-STABLE FreeBSD 9.3-STABLE #1 r268979: Tue Jul 22 22:42:39 EST 2014 root@boffin:/usr/obj/home/src/sys/GENERIC amd64 This is a bug in gcc's emmintrin.h header. I have committed a fix to head in r269948, and I will merge it to stable/10 and stable/9 in three days. Meanwhile, please apply the attached diff to emmintrin.h in /usr/include/gcc/4.2 manually. -Dimitry Hi dim, Thanks for your explanation. I've posted the information to ports/192600 and ports/192637. I have proposed in the latter that you switch the port to using a newer GCC version or clang on the affected systems, to sidestep the issue. I am unsure if we will have an erratum, so for the benefit of users who use the releases rather than STABLE/, it would be beneficial to have the port compilable on systems that installed a broken/unpatched gcc 4.2. Dimitry, any plans for an erratum? Thank you. ___ 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-im/skype-[devel] won't connect
Hi, On Wed, Aug 13, 2014 at 10:47:25AM -0500, Scot Hetzel wrote: On Wed, Aug 13, 2014 at 10:38 AM, Kenta S. ken...@hush.com wrote: Hello. This afternoon when I try to sign onto Skype, I get: Periodic UIC Update Failed I haven't updated ports recently. Does anyone have an idea? I heard Skype was closing down old versions. I had received the following e-mail from Skype a few days ago: On Fri, Aug 8, 2014 at 7:53 PM, Skype norep...@emails.skype.com wrote: Your Skype for Linux version is being retired. Update today. » Can't see this email properly? Forgotten your password? Your Skype for Linux version is being retired. Update today. Dear swhetzel, We are now retiring older versions of Skype and it appears that at some point you signed into Skype with one of these. To continue signing into Skype on Linux you'll need to download the latest version. The new version comes with improved performance, the latest features and security updates, so you'll get the best possible Skype experience. If you're on the latest version of Skype, the above will not apply. Update now at http://www.skype.com/download. Someone will need to update the Skype port to the latest Linux version and see if it works on our current version of Linux emulation. I've read in various places (and tested myself with a couple of version on Linux) that any version before skype 4.3.0.37 will not connect. The skype port at: https://github.com/vassilisl/freebsd-ports/tree/master/net-im/skype4 will connect (if you use the f20 ports https://github.com/vassilisl/freebsd-linux_base-f20 ;) ) but it doesn't have sound working. Both xmj and I are working on getting that version of Skype on c6 and f20 linux emulation bases respectivelly, which basically means get it to talk to pulseaudio. If anyone has experience with that, please shout! :) Regards, Vassilis -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. ___ freebsd-emulat...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org -- “Prediction is very difficult, especially if it's about the future.” ― Niels Bohr F5E2 30B5 72BB DB1E EB24 B06F 6986 DE46 E128 CC4A signature.asc Description: Digital signature
Re: ImageMagic + Webp
On 13 Aug 2014, at 23:06, Matthias Andree mand...@freebsd.org wrote: Am 13.08.2014 um 20:20 schrieb Sunpoet Po-Chuan Hsieh: On Thu, Aug 14, 2014 at 12:53 AM, Dimitry Andric d...@freebsd.org wrote: On 12 Aug 2014, at 07:44, Robert Backhaus rob...@robbak.com wrote: On 11 August 2014 18:45, Jos Chrispijn po...@webrz.net wrote: After I installed ImageMagic port, I got stuck at the installation of Webp: === Building for webp-0.4.1 Making all in src Making all in dec Making all in enc Making all in dsp CC libwebpdspdecode_sse2_la-lossless_sse2.lo lossless_sse2.c: In function 'ConvertBGRAToBGR': lossless_sse2.c:403: note: use -flax-vector-conversions to permit conversions between vectors with differing element types or numbers of subparts lossless_sse2.c:403: error: incompatible type for argument 1 of '__builtin_ia32_psrlqi128' lossless_sse2.c:404: error: incompatible type for argument 1 of '__builtin_ia32_psrlqi128' *** [libwebpdspdecode_sse2_la-lossless_sse2.lo] Error code 1 [...] I have the same issue here. Sunpoet, do you have this? I have attached a script of my failure. FreeBSD boffin 9.3-STABLE FreeBSD 9.3-STABLE #1 r268979: Tue Jul 22 22:42:39 EST 2014 root@boffin:/usr/obj/home/src/sys/GENERIC amd64 This is a bug in gcc's emmintrin.h header. I have committed a fix to head in r269948, and I will merge it to stable/10 and stable/9 in three days. Meanwhile, please apply the attached diff to emmintrin.h in /usr/include/gcc/4.2 manually. -Dimitry Hi dim, Thanks for your explanation. I've posted the information to ports/192600 and ports/192637. I have proposed in the latter that you switch the port to using a newer GCC version or clang on the affected systems, to sidestep the issue. Either that, or include a patched version of emmintrin.h in the port as a workaround? The bad macro for _mm_srli_epi64() has been in our tree for 7 years, and this is the first program that ever barfs on it. :-) I am unsure if we will have an erratum, so for the benefit of users who use the releases rather than STABLE/, it would be beneficial to have the port compilable on systems that installed a broken/unpatched gcc 4.2. Dimitry, any plans for an erratum? That is extremely unlikely. Release errata are normally only for severe security issues, and this is definitely not such an issue. It's actually less hassle to just patch the file in /usr/include/gcc/4.2 than to patch your sources, rebuild world, etc. :) You can even do this if you use binary updates. -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Re: SUHOSIN option on lang/php53
Ah, of course. I, for some reason, though the patch was there so that the extension could work, but I see now that's not actually the case. Carry on! :) On Wed, Aug 13, 2014 at 11:04 AM, Florian Smeets f...@smeets.im wrote: On 13/08/14 18:32, Kurt Jaeger wrote: Hi! Just wondering: since security/php-suhosin won't build on PHP 5.3, why is there still an option for Suhosin in the lang/php53 port? http://svnweb.freebsd.org/ports/head/security/php-suhosin/Makefile?r1=349250r2=349251; Because no-one noticed and send a patch/PR 8-} ? No, they are 2 different things. One is the Suhosin patch, one the extension. http://suhosin.org/stories/index.html Florian ___ 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: OCAML version 3 (legacy)
Thanks for the info, that's interesting. I solved my problem by digging up a binary package for OCAML 3.x. But it was not ideal, I think it was a 8.3 package when was on a 8.4 system. Also, it was the old pkg format, but a pkg2ng brought it into line with pkgng. It's great that the new pkgng doesn't block the old packages, and even greater that we can pkgng after the initial boot-strapping. How would dependency resolution be affected by your suggested method? The context of my issue was that I needed a unison built with OCAML 3.x. I would have thought that the port for unison232 would depend on OCAML (as a build dependency) and thet would pull down OCAML 4.x. So despite the OPAM provisioning OCAML 3.x, it would require some hacking to get it to build unison232. In the future, I may provision a FreeBSD 10.x server, and I will not find a binary package for OCAML 3.x. Idealy, the OCAML devs should have allowed for backwards compatability, like being abl e to create a 3.x database. BTW, I don't know anything about OCAML, other than it's needed by unison. On Tuesday, August 12, 2014 20:53 SGT, Gabor Pali p...@freebsd.org wrote: Hi Euan, 2014-08-11 17:03 GMT+01:00 Euan Thoms : However, I was suggesting we have a legacy port for OCAML 3.x, just like we have for php and other important stuff that newer versions breaks things. If you are really in need for the 3.x version of OCaml compiler, you may want to try OPAM [1]. That is the ocaml-opam package [2] in the FreeBSD repositories. Although OPAM is dubbed as a package manager, it can actually manage different compiler versions, using its switch command [3]. Then you could install OCaml packages atop that compiler separately, isola ted from other instances, giving the advantage of working with multiple OCaml versions at the same time. [1] https://opam.ocaml.org/ [2] http://www.freshports.org/devel/ocaml-opam [3] https://opam.ocaml.org/doc/Advanced_Usage.html ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: OCAML version 3 (legacy)
2014-08-13 22:29 GMT+01:00 Euan Thoms e...@potensol.com: How would dependency resolution be affected by your suggested method? OPAM manages the dependencies itself, without involving pkg(8). For what it is worth, you should be able to install unison via OPAM easily. Though, it will not put the unison binary to under /usr/local/bin but somewhere around ~/.opam/bin instead. The context of my issue was that I needed a unison built with OCAML 3.x. Why? Will not the net/unison232 or the net/unison port simply work? They should be using the latest version of lang/ocaml already. ___ 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: OCAML version 3 (legacy)
Why? Will not the net/unison232 or the net/unison port simply work? They should be using the latest version of lang/ocaml already. Yes, the unison232 will built and work with the OCAML in the tree. However with unison, it's critical that the client and server version matches. that's why I'm still on 2.32.52, because i have a couple hundred deployed clients potentially using unison. It seems that not only must the unison version match exactly, but the OCAML database it uses must also match. Or at least it must be compatable. OCAML 4.x databases are not compatable with 3.x. Hence the problem. Perhaps there are other ports out there that OCAML 4.x causes breakage. On Thursday, August 14, 2014 06:10 SGT, Gabor Pali p...@freebsd.org wrote: 2014-08-13 22:29 GMT+01:00 Euan Thoms : How would dep endency resolution be affected by your suggested method? OPAM manages the dependencies itself, without involving pkg(8). For what it is worth, you should be able to install unison via OPAM easily. Though, it will not put the unison binary to under /usr/local/bin but somewhere around ~/.opam/bin instead. The context of my issue was that I needed a unison built with OCAML 3.x. Why? Will not the net/unison232 or the net/unison port simply work? They should be using the latest version of lang/ocaml already. ___ 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: [Patch] Using MACHINE_ARCH identifiers in pkg
On 06/26/14 14:30, Baptiste Daroussin wrote: On Thu, Jun 19, 2014 at 10:22:30AM -0700, Nathan Whitehorn wrote: On 05/28/14 10:04, Baptiste Daroussin wrote: On Wed, May 28, 2014 at 09:54:03AM -0700, Nathan Whitehorn wrote: The following was in a deep and increasingly branched thread on the SVN list. I've forwarded the relevant part here. The discussion was on using MACHINE_ARCH codes for package architectures in pkg instead of the existing ones (which are equivalent) to make script-writing easier and improve consistency with the way the src and ports trees work. The patches below are designed to make transitioning the architecture identifiers as painless as possible. -Nathan I've written two patches today. The first (http://people.freebsd.org/~nwhitehorn/pkg_machinearch.diff) is to pkg itself and the second (http://people.freebsd.org/~nwhitehorn/pkg_bootstrap_machinearch.diff) is to the pkg bootstrapper in base. These switch pkg from using identifiers like freebsd:11:arm:32:eb:eabi:softfp to identifiers like FreeBSD:11:armeb, matching the canonical FreeBSD platform identifiers. The strings it uses can be predicted easily from scripts, as they are identical in all cases to the output of `uname -s`:`uname -r | cut -f 1 -d .`:`uname -p`. I tried to avoid changing much, so the patches are pretty short. Internally, the patch introduces a translation table to pkg that contains all extant FreeBSD and Dragonfly BSD architectures and moves between the ELF-based coding and MACHINE_ARCH values. This is kind of gross, but has the least possibility for regression, and can easily be changed behind the scenes later. Platform detection uses the same ELF-parsing code as before. The current/previous values are also kept so that the patched pkg can install a package marked either with an x86:64 or amd64-type architecture ID (symlinks will be needed for a little bit on the package server to allow both clients to work). Limited testing suggests it works well -- I can fetch and install packages fine. More testing would be great. One small issue is how to bootstrap the change for existing binary package users. The modified pkg can use packages with either architecture ID just fine, but the current one will barf on the FreeBSD:11:amd64 package containing its own update. There are a couple of options: manual instructions, marking that one package with the old-style architecture ID, etc. None should be more than slightly irritating, though. The least bumpy route, I think, is making directories with both the old and new names, but putting only one package in the old-named directory: a special intermediate version of pkg marked with the old architecture ID but able to install from the new one. Then you just have to deal with two rounds of updates without any other intervention, which is not so bad. -Nathan Thanks I'll be away for a couple of days, but I'll have a look and test your patch in all situation we need to support and come back to you if needed or directly commit; regards, Bapt Have you had a chance to look at this yet? I'm happy to help with any testing if you need. -Nathan I do like the appraoch but I haven't yet had time to study the side effect, it is already complicated to get pkg 1.3 out, I are quite close now so this will wait for 1.4, but I'll push it on top of my TODO list for 1.4. regards, Bapt Anything you need help with here? We seem to be moving pretty rapidly toward having official packages for more platforms, which is great, but it would be nice to have this in beforehand to reduce the number of needed compatibility shims on the package server. -Nathan ___ 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
pkgng bsd.pkgng.mk and upgrade vars
Hi,
I was playing with pkgng and making some new ports when I found in
bsd.pkgng.mk some features like:
KGPREINSTALL?= ${PKGDIR}/pkg-pre-install
PKGPOSTINSTALL?=${PKGDIR}/pkg-post-install
PKGPREDEINSTALL?= ${PKGDIR}/pkg-pre-deinstall
PKGPOSTDEINSTALL?= ${PKGDIR}/pkg-post-deinstall
PKGPREUPGRADE?= ${PKGDIR}/pkg-pre-upgrade
PKGPOSTUPGRADE?=${PKGDIR}/pkg-post-upgrade
PKGUPGRADE?=${PKGDIR}/pkg-upgrade
Anyone can tell me what can i do with this options? For instance, I can
suppose that PKGUPGRADE will only run if i'm upgrading an installed
package. Am i right?
Anyway, i tried to use that in my port with no success, here is the
important piece of my Makefile:
SUB_FILES= pkg-install pkg-upgrade
upgrade:
${SH} ${PKGUPGRADE} ${PKGNAME} UPGRADE
I created files/pkg-upgrade.in with some commands to be ran in an upgrade.
But when i upgrade my package on client side it didn't work.
Anyone is using that and can explain how it works?
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
pkg 1.3.5.1 -1.3.6: Repository has incompatible checksum format, need to re-create database
Greetings, I just upgraded pkg, and see this: $ pkg clean pkg: Repository pinyon has incompatible checksum format, need to re-create database Nothing to do. How do I recreate the database? This is a poudriere version 3.0.17 maintained pkg repo. On a different system, using the same poudriere maintained repo, with pkg 1.3.5.1 I don't see the re-create notice. Both systems fairly fresh currents. Russell ___ 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 1.3.5.1 -1.3.6: Repository has incompatible checksum format, need to re-create database
Try `pkg update`. It might be `pkg update -f`. On Wed, Aug 13, 2014 at 05:30:08PM -0700, Russell L. Carter wrote: Greetings, I just upgraded pkg, and see this: $ pkg clean pkg: Repository pinyon has incompatible checksum format, need to re-create database Nothing to do. How do I recreate the database? This is a poudriere version 3.0.17 maintained pkg repo. On a different system, using the same poudriere maintained repo, with pkg 1.3.5.1 I don't see the re-create notice. Both systems fairly fresh currents. Russell ___ 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 -- `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 1.3.5.1 -1.3.6: Repository has incompatible checksum format, need to re-create database
On 08/13/14 17:59, Koichiro IWAO wrote: Try `pkg update`. It might be `pkg update -f`. That seems to work, perhaps the message might read, Repository needs to be updated, run \pkg update\ or Repository has incompatible checksum format, see pkg-update Thanks! Russell On Wed, Aug 13, 2014 at 05:30:08PM -0700, Russell L. Carter wrote: Greetings, I just upgraded pkg, and see this: $ pkg clean pkg: Repository pinyon has incompatible checksum format, need to re-create database Nothing to do. How do I recreate the database? This is a poudriere version 3.0.17 maintained pkg repo. On a different system, using the same poudriere maintained repo, with pkg 1.3.5.1 I don't see the re-create notice. Both systems fairly fresh currents. Russell ___ 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 1.3.5.1 -1.3.6: Repository has incompatible checksum format, need to re-create database
On 14/08/2014 11:15 AM, Russell L. Carter wrote: On 08/13/14 17:59, Koichiro IWAO wrote: Try `pkg update`. It might be `pkg update -f`. That seems to work, perhaps the message might read, Repository needs to be updated, run \pkg update\ or Repository has incompatible checksum format, see pkg-update Thanks! Russell On Wed, Aug 13, 2014 at 05:30:08PM -0700, Russell L. Carter wrote: Greetings, I just upgraded pkg, and see this: $ pkg clean pkg: Repository pinyon has incompatible checksum format, need to re-create database Nothing to do. How do I recreate the database? This is a poudriere version 3.0.17 maintained pkg repo. On a different system, using the same poudriere maintained repo, with pkg 1.3.5.1 I don't see the re-create notice. Both systems fairly fresh currents. Russell ___ 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 Good idea Russell, please create an issue for it at https://github.com/freebsd/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: pkg-static error when installing php5 from ports
No response on freebsd-pkg@ so figured I would try my luck here. best Neel On Tue, Aug 12, 2014 at 5:57 PM, Neel Natu neeln...@gmail.com wrote: Hi, I am installing php5 from ports. It builds fine but fails with this error when installing: [/usr/ports/lang/php5]$ sudo make install === Installing for php5-5.4.31 === php5-5.4.31 depends on shared library: libpcre.so - found (/usr/local/lib/libpcre.so.3) === php5-5.4.31 depends on shared library: libxml2.so - found (/usr/local/lib/libxml2.so.2.9.1) === Checking if php5 already installed === Registering installation for php5-5.4.31 pkg-static: Invalid manifest format: could not find expected ':' *** Error code 74 Stop. make[1]: stopped in /usr/ports/lang/php5 *** Error code 1 Any clue what might be happening and how to fix? best Neel ___ 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
Enlarge business-from china hair manufacturer
Hi friend Here is summer from qingdao arison hair we factory is 4 years golden supplier in china. hair details : 1.length 8- 30 2.weight 100 g/bundle 3.material 100% natural raw virgin hair 4.weft head double layersmachine made 5.endfull and thick 6.remy full cuticle 7.paymentpaypal,western union,moneygram,t/t 8.shipping dhl,fedex(within 2-3 days) 9.delivery have 4000 pcs stock for fast delivery advantage : can be dyed , curl ,strength , bleach etc. Item :superiors quality hair weft (Brazilian, Malaysian, Indian, Chinese, Peruvian, European and etc ) Price-(Highest Quality) length7A8A 8 1927 10 2331 12 2633 14 3241 16 3747 18 4554 20 5358 22 5966 24 6370 26 6773 287077 Hair Weft Effect Picture summer -- Summer shang---Manager Skype:summer532531 Qingdao Arison hair product Co.,Ltd Phone:86-18678468605 Tel:86-532-68988853 ___ 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
