Re: editors/abiword fails on not-really-missing dependency

[Ben Woods]

I have just submitted a bug report which includes a patch to update abiword
to the latest upstream release version 3.0.1.

This fixes the issues you have identified in your email.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199156

I would be greatful if you could test this patch to the port and confirm it
fixes your issue.

Regards,
Ben

On Mon, Mar 30, 2015 at 10:05 AM Thomas Mueller 
wrote:

> I tried to build editors/abiword, but it failed for lack of libwpg-0.1 and
> libwpd-0.8.
>
> pkg info -a | grep -n "libwp" produces
>
> 314:libwpd-0.9.9_2 Tools for importing and exporting
> WordPerfect(tm) documents
> 315:libwpg-0.2.2_3 Library and tools to work with
> WordPerfect Graphics (WPG) files
>
> So it looks like I have the required dependencies, but the configure
> script seemed to be looking for an earlier version.
>
> Relevant part of build log is
>
> configure: error: Package requirements ( libgsf-1 >= 1.12 libwpg-0.1 >=
> 0.1.0 libwpd-0.8 >= 0.8.0 ) were not met:
>
> Package libwpg-0.1 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libwpg-0.1.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libwpg-0.1', required by 'world', not found
> Package 'libwpd-0.8', required by 'world', not found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables WPG_CFLAGS
> and WPG_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> ===>  Script "configure" failed unexpectedly.
>
>
> Is this a bug in the configure script or FreeBSD ports' patches?
>
> I could cd /usr/local/libdata/pkgconfig  and
> ln -s libwpg-0.2.pc libwpg-0.1.pc
> ln -s libwpd-0.9.pc libwpd-0.8.pc
>
> and thereby give the configure script what it's looking for, a kludge with
> no certainty of success.
>
> Maybe delete the symbolic links afterward.
>
> Tom
>
> ___
> 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: poudriere 3.1.2: bulk fails and deletes jail

[Bryan Drewery]

On 4/2/2015 12:19 PM, Stefan Ehmann wrote:
> The following commands work as expected with poudriere 3.1.1:
> 
> # poudriere jail -c -v 10.1-RELEASE -a amd64 -j 101amd64
> # poudriere bulk -j 10amd64 ports-mgmt/poudriere
> 
> 
> After upgrade to 3.1.2 it fails:
> 
> # poudriere bulk -j 101amd64 ports-mgmt/poudriere
> [00:00:00] >> Creating the reference
> jail.../usr/local/share/poudriere/bulk.sh: cannot create
> /usr/local/poudriere/jails/101amd64/usr/.cpignore: No such file or
> directory
> /usr/local/share/poudriere/bulk.sh: cannot create
> /usr/local/poudriere/jails/101amd64/usr/lib/.cpignore: No such file or
> directory
>  done
> [00:00:04] >> Mounting system devices for 101amd64-default
> [00:00:04] >> Mounting ports/packages/distfiles
> [00:00:04] >> Stashing existing package repository
> [00:00:04] >> Mounting packages from:
> /usr/local/poudriere/data/packages/101amd64-default
> [00:00:04] >> Copying /var/db/ports from:
> /usr/local/etc/poudriere.d/options
> /usr/local/share/poudriere/bulk.sh: cannot create
> /usr/local/poudriere/data/.m/101amd64-default/ref/etc/make.conf: No such
> file or directory
> [00:00:04] >> Cleaning up
> [00:00:04] >> Umounting file systems
> 
> And worse: The contents of the jail are deleted:
> # du -sh /usr/local/poudriere/jails/101amd64/
> 4.0K/usr/local/poudriere/jails/101amd64/
> 
> 
> The problem probably only occurs in specific configurations. Otherwise,
> I would have expected several reports by now.
> 
> # diff poudriere.conf.sample poudriere.conf | grep \>
>> NO_ZFS=yes
>> USE_TMPFS=all
>> CHECK_CHANGED_DEPS=yes
>> PARALLEL_JOBS=1
>> ALLOW_MAKE_JOBS=yes

3.1.3 is now out which fixes this. Sorry about that.


-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: Share your pkg aliases

[Kevin Oberman]

On Fri, Apr 3, 2015 at 12:47 PM, Craig Rodrigues 
wrote:

> On Thu, Apr 2, 2015 at 1:19 PM, Baptiste Daroussin 
> 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.
> >
>
> I notice that there is a /usr/local/etc/bash_completion.d/_pkg.bash file
> which implements tab completion
> for pkg commands.  Is there a way to make this file get picked up
> by default when ports-mgmt/pkg is installed,
> instead of having to edit .bashrc?
>
> It's a minor thing, but tab completions are really nice for usability.
> bash shell users can use this, but zsh also has a way to read bash
> completion scripts.
>
> --
> Craig
>

And I  keep meaning to write a tcsh completion script for pkg. Maybe I'll
get to at least a basic one next week. I see that bash completion scripts
are quite different, but I'll see if the _pkg.bash file can at least get me
started. It does more than I'd probably get done in the first pass.
--
Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: How do I specify port opt1 requires opt2

[Kevin Oberman]

On Fri, Apr 3, 2015 at 11:51 AM, Mathieu Arnold  wrote:

>
>
> +--On 3 avril 2015 05:46:45 + Ben Woods  wrote:
> | I am working on modifying a port, and was wondering how do I specify that
> | selecting port option1 requires that option2 is also selected?
> |
> | Note that in my example it is perfectly acceptable to have option2
> | selected without option1.
>
> This functionnality is coming, it's being discussed in
>  but for now,
> you'll have to do some testing in your Makefile and either add an IGNORE or
> force the other option.
>
> --
> Mathieu Arnold
>

What I have done in the past is to put "(Forces option OPTION)" in the
description line and then either set opt2 in the IF block for opt1 or
simply set the opt2 flag, if that is all opt2 requires, in that block.
--
Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

blender 2.74

[ajtiM]

Hi!

I did install Blender 2.74 on my FreeBSD 10.1 (amd64) without a problem
but it doesn't want to start. When I run from terminal I got:

"blender
Two passes with the same argument (-alloca-hoisting) attempted to be
registered!
Writing: /tmp/blender.crash.txt
Segmentation fault (core dumped)"


In /tmp/blender.crash.txt is just:
# Blender 2.74 (sub 0), Unknown revision

# backtrace

Thank you.


-- 
ajtiM
-
http://www.redbubble.com/people/lumiwa
https//www.facebook.com/pages/Lumiwa-FARM/775292915882930

___
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

[Craig Rodrigues]

On Thu, Apr 2, 2015 at 1:19 PM, Baptiste Daroussin  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.
>

I notice that there is a /usr/local/etc/bash_completion.d/_pkg.bash file
which implements tab completion
for pkg commands.  Is there a way to make this file get picked up
by default when ports-mgmt/pkg is installed,
instead of having to edit .bashrc?

It's a minor thing, but tab completions are really nice for usability.
bash shell users can use this, but zsh also has a way to read bash
completion scripts.

--
Craig
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: How do I specify port opt1 requires opt2

[Mathieu Arnold]

+--On 3 avril 2015 05:46:45 + Ben Woods  wrote:
| I am working on modifying a port, and was wondering how do I specify that
| selecting port option1 requires that option2 is also selected?
| 
| Note that in my example it is perfectly acceptable to have option2
| selected without option1.

This functionnality is coming, it's being discussed in
 but for now,
you'll have to do some testing in your Makefile and either add an IGNORE or
force the other option.

-- 
Mathieu Arnold
___
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

[Mathieu Arnold]

+--On 2 avril 2015 09:08:00 -0500 Mark Felder  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?

Like gssapi from base, yes, we would need to only link with gssapi from
ports.

There is also the problems of ports linking with libpkg.so and
libcrypto.so... (like net-snmp)

-- 
Mathieu Arnold
___
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: Synchronising ports with package cluster

[Mathieu Arnold]

+--On 2 avril 2015 10:13:34 -0700 Mel Pilgrim
 wrote:
| On 2015-04-01 13:42, Mike Clarke wrote:
|> Where can I now obtain the revision number for the ports tree used for
|> the latest package build?
|> 
|> Although the above method has worked in the past it's a bit of a bodge.
|> The ideal way would be if this information could be accessed directly
|> from the relevant package repository. Would it be possible to provide
|> such a facility?
| 
| This is has been asked for many times in many forms--from SVN branching
| to simply an extra bit of metadata provided by pkg itself.  The usual
| answer is, "we'll put this in a future version," but it remains not
| implemented.

Do feel free to provide a patch, adding this to, say, the repo metadata.

-- 
Mathieu Arnold
___
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: [CFT] Call for testing pkg 1.5.0

[Baptiste Daroussin]

On Fri, Apr 03, 2015 at 02:35:43PM +0100, Big Lebowski wrote:
> >
> > Please test and report as much bugs as you can!
> > We could be very grateful if regressions tests could be provided along with 
> > the
> > bug reports :)
> >
> 
> Mine just did something like that:
> 
> foobar# uname -a
> FreeBSD foobar.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r280994M: Thu
> Apr  2 20:16:53 CEST 2015
> r...@pd.valinor.palantiri.org:/usr/obj/usr/src/sys/FOOBAR  amd64
> foobar [uname -a] ~/
>   15-04-03
>  3:33PM
> foobar# pkg --version
> 1.4.99.15
> foobar [pkg --version] ~/
>   15-04-03
>  3:33PM
> foobar# pkg version
> Child process pid=41119 terminated abnormally: Segmentation fault
> foobar [pkg version] ~/
>   15-04-03
>  3:33PM
> foobar# pkg version -t 0.2.o.git20150311 0.2.o.20150402
> <
> foobar [pkg version -t 0.2.o.git20150311 0.2.o.20150402] ~/
>   15-04-03
>  3:33PM
> pd#

Let me fix that :)

Best regards,
Bapt


pgp1ItMlsmvf9.pgp
Description: PGP signature

Re: [CFT] Call for testing pkg 1.5.0

[Big Lebowski]

>
> Please test and report as much bugs as you can!
> We could be very grateful if regressions tests could be provided along with 
> the
> bug reports :)
>

Mine just did something like that:

foobar# uname -a
FreeBSD foobar.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r280994M: Thu
Apr  2 20:16:53 CEST 2015
r...@pd.valinor.palantiri.org:/usr/obj/usr/src/sys/FOOBAR  amd64
foobar [uname -a] ~/
  15-04-03
 3:33PM
foobar# pkg --version
1.4.99.15
foobar [pkg --version] ~/
  15-04-03
 3:33PM
foobar# pkg version
Child process pid=41119 terminated abnormally: Segmentation fault
foobar [pkg version] ~/
  15-04-03
 3:33PM
foobar# pkg version -t 0.2.o.git20150311 0.2.o.20150402
<
foobar [pkg version -t 0.2.o.git20150311 0.2.o.20150402] ~/
  15-04-03
 3:33PM
pd#
___
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: [CFT] Call for testing pkg 1.5.0

[Big Lebowski]

>> I just wanted to take the time to thank you for all the
>> work you've put into this.
>>
>> Thanks!
>
> Thanks much appreciated, I want to share that with vsevolod@ and az@ who also
> spent a lot of time working on it!
>

Indeed, HUGE THANKS for what you guys are doing with pkg - I cant wait
to see that OS X integration in action (and other things as well), you
rock!

S.
___
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

[Mathieu Arnold]

+--On 2 avril 2015 22:19:10 +0200 Baptiste Daroussin 
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.

leaf = "query -e \"%#r == 0\" \"%n-%v\"";
noauto = "query -e \"%a == 0\" \"%n-%v\"";

-- 
Mathieu Arnold
___
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

[Lars Engels]

On Thu, Apr 02, 2015 at 10:19:10PM +0200, Baptiste Daroussin 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.

myports: rquery -e '%m = l...@freebsd.org' %o,  # Show ports maintained by me
unmaintained: query -e '%m = po...@freebsd.org' %o, # Show unmaintained ports
csearch: search -U -c, # Search a port's short description



pgp6pV8wA4MSc.pgp
Description: PGP signature

FreeBSD ports you maintain which are out of date

[portscout]

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
+-+
www/drupal6-webform | 6.x-3.17| 6.x-3.23
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Share your pkg aliases

[Henry Hu]

On Fri, Apr 3, 2015 at 2:53 AM Baptiste Daroussin  wrote:

> On Fri, Apr 03, 2015 at 06:36:52AM +, Henry Hu wrote:
> > On Thu, Apr 2, 2015 at 4:19 PM Baptiste Daroussin 
> 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.
> > >
> >
> > I have two aliases:
> > alias: {
> > "locked": "query -e '%k == 1' %n",
> > "leaf": "query -e '%#r == 0' '%n auto: %a'",
> > }
> > The first one queries the locked packages, and the second one queries the
> > leaf packages.
>
> Thanks
>
> How is locked different from pkg lock -l ?
>

Basically the same... I'm not aware of pkg lock -l.

>
> Best regards,
> Bapt
>
___
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"