Re: FreeBSD Port: evolution-3.12.11

2015-04-05 Thread Ting-Wei Lan
於 六,2015-04-04 於 22:19 -0700,Randall R. King 提到:
 Hi,
 
 A quick note to let you know that I had difficulty restoring data from a
 backup (whatever version was running under FreeBSD 9.2). After a careful
 look at the debug messages, it looked like the tar commands used in the
 restoration used the option --strip-components=3 (or 2), and the tar
 command barfed on that option (the '=' sign should be a space). Hiding
 tar and linking tar to gtar fixed the problem. Perhaps the script(s) for
 restoration should either lose the equal sign on the --strip-components
 option or use gtar instead of tar?

Thanks for finding the cause of the bug. Does the following patch work for you?
If yes then I will file an upstream bug report with this patch attached.

diff --git a/modules/backup-restore/evolution-backup-tool.c b/modules/backup
-restore/evolution-backup-tool.c
index 9604513..3eef5f9 100644
--- a/modules/backup-restore/evolution-backup-tool.c
+++ b/modules/backup-restore/evolution-backup-tool.c
@@ -538,13 +538,13 @@ restore (const gchar *filename,
g_mkdir_with_parents (e_get_user_config_dir (), 0700);
 
command = g_strdup_printf (
-   cd $DATADIR  tar xzf %s %s --strip-components=%d,
+   cd $DATADIR  tar --strip-components %d -xzf %s %s,
quotedfname, data_dir, get_dir_level (data_dir));
run_cmd (command);
g_free (command);
 
command = g_strdup_printf (
-   cd $CONFIGDIR  tar xzf %s %s --strip-components=%d,
+   cd $CONFIGDIR  tar --strip-components %d -xzf %s
%s,
quotedfname, config_dir, get_dir_level (config_dir));
run_cmd (command);
g_free (command);


 
 Sincerely,
 Randall R. King
 
 ___
 freebsd-gn...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
 To unsubscribe, send any mail to freebsd-gnome-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

pipelight update

2015-04-05 Thread philippe . rodride
Hi, 

I've installed pipelight 0.2.7.3_7 from the ports and i encounter some 
problems. 

It is possible to know when a new version (0.2.8.x) will be available ? 

Thanks. 


Philippe R. 


___
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: Blender 2.74 cannot compile on FreeBSD 10.1

2015-04-05 Thread Ben Woods
The graphics/libraw package installs /usr/local/lib/libraw_r.so.10, not
libraw_r.so.9 so it will not be detected. See the pkg-plist for
graphics/libraw here:
https://svnweb.freebsd.org/ports/head/graphics/libraw/pkg-plist?revision=379518view=markup

The interesting thing is that whilst graphics/blender depends on
the graphics/openimageio library, neither depend on the graphics/libraw
library.

It might be worth asking the port maintainers for graphics/blender and
graphics/openimageio if they have come across this before. I have added
m...@freebsd.org and free...@shaneware.biz to the recipients of this email
to check with them.

Regards,
Ben

On Sun, Apr 5, 2015 at 9:33 AM Robert Backhaus rob...@robbak.com wrote:

 To get the simple things out of the road - you have reinstalled libraw, and
 checked that libraw_r.so.9 is in /usr/local/lib?

 This error tells me that your install of libOpenImageIO.so.1.4 is faulty,
 so you should also rebuild the port that includes that (pkg which `locate
 \*libOpenImageIO.so.1.4`)

 On 5 April 2015 at 02:36, pipolandi pipola...@gmail.com wrote:

  I forgot to say that libraw is installed.
 
 
 
  --
  View this message in context:
  http://freebsd.1045724.n5.nabble.com/Blender-2-74-
 cannot-compile-on-FreeBSD-10-1-tp6002715p6002716.html
  Sent from the freebsd-ports mailing list archive at Nabble.com.
  ___
  freebsd-ports@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-ports
  To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
 
 ___
 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: Share your pkg aliases

2015-04-05 Thread Ion-Mihai Tetcu
On Thu, 2 Apr 2015 22:19:10 +0200
Baptiste Daroussin b...@freebsd.org wrote:

 Hi,
 
 For pkg 1.5.0 we do plan to provide a default pkg.conf full of useful
 aliases, of course this is subjective, if you think you have added
 some useful aliases into your pkg.conf please share those so we can
 add them directly into the next release.

  options: query -i %n - %Ok: %Ov,
  roptions: rquery -i %n - %Ok: %Ov,
  comment: query -i %c,
  desc: query -i %e,

roptions is particularly useful to see if the default options fit
one's needs (either on the initial install or on an upgrade when
OPTIONS changed).

-- 
IOnut - Un^d^dregistered ;) FreeBSD user
  Intellectual Property is   nowhere near as valuable   as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 29597D20

___
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: Pourdriere produces faulty build results due to bsd.openssl.mk bug

2015-04-05 Thread Spil Oss
Linking OpenSSL in ports and also requiring something from base that
links OpenSSL seems to be pretty rare indeed. A notable example being
ftp/curl that requires GSSAPI from base kerberos by default (this is
now fixed in ports) and thus relying on both ports and base ssl via
libkrb5.so. This is likely to be the most common case, something
relying on kerberos from base. I'm not quite sure how hard the
reliance on kerberos in base is but I'd like to see it made private
for base, we have multiple alternatives in ports.

This thread misses a reference for the starter to
https://bugs.freebsd.org/195796 which lists ports linking base
libssl/libcrypto whilst WITH_OPENSSL_PORT=yes is set. I'm trying to
collect work done to get these ports to link to ports OpenSSL in
https://wiki.freebsd.org/OpenSSL/PortsLinkingBase (that is just a
placeholder for now, trying to finish the LibreSSL fallout first)

Thanks, Bernard

On Thu, Apr 2, 2015 at 4:08 PM, Mark Felder f...@freebsd.org wrote:


 On Wed, Apr 1, 2015, at 16:21, Bryan Drewery wrote:
 On 4/1/2015 3:59 PM, Yuri wrote:
  I found that packages produced by poudriere likely link with base
  openssl, while port make likely links with the port openssl.
  This is because of the lines in bsd.openssl.mk which check for the
  presence of openssl shared library and headers under PREFIX, and set
  WITH_OPENSSL_BASE when they aren't present. In case of port make files
  are likely present, and in case of poudriere build files are likely not
  present.
 
  Example is ftp/curl (with GSSAPI=NONE,  OPENSSL=yes options). *Poudriere
  produces curl library, that causes VirtualBox to break* due to the
  openssl base vs. port conflicts. See recent emulation@ ML threads. Port
  make produces curl library that works fine with VirtualBox.
 
  I think both WITH_OPENSSL_BASE and WITH_OPENSSL_PORT should be retired,
  and code checking file presence also should be removed, and all ports
  should be made to build with an openssl port instead. Ports should never
  use base OpenSSL.
 
  Only 100 ports touch WITH_OPENSSL_... variables. Somebody who is able
  to make such decisions and has the commit bit should bit should look
  into this. Otherwise, massively faulty package repositories are produces.
 
  Yuri

 I've wanted this for a long time. I think we should just do it.


 What are the risks of something linking to OpenSSL in ports also
 requiring something from base which in turn... links in OpenSSL from
 base?
 ___
 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: Blender 2.74 cannot compile on FreeBSD 10.1

2015-04-05 Thread pipolandi
Thank you both for your time and answers. 

Looks like openimageio was not properly updated.

I had to execute:

1- portmaster graphics/openimageio
2- portmaster graphics/blender

to get a functional Blender.

I thought portmaster was capable of resolving all dependencies of Blender by
just doing 'portmaster graphics/blender'. 

Many thanks again for your answers.

Saludos!.



--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Blender-2-74-cannot-compile-on-FreeBSD-10-1-tp6002715p6002885.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org