date:20140801

FreeBSD ports you maintain which are out of date

2014-08-01 Thread 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
+-+
editors/zim | 0.60| 0.61
+-+
net-mgmt/pandorafms_agent   | 4.0.1   | 5.1-140801
+-+
net-mgmt/pandorafms_console | 4.0.1   | 5.1-140801
+-+
net-mgmt/pandorafms_server  | 4.0.1   | 5.1-140801
+-+
x11/roxterm | 2.8.3   | 2.9.1
+-+


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

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

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: OPTIONS_REQUIRES

2014-08-01 Thread Daniel Morante

I've recently had this issue .  The following forum post provides a 
decent work around for the time being:

https://forums.freebsd.org/viewtopic.php?f=22&t=47412

Also consider the following case as well:

OPTIONS_GROUP= X11
OPTIONS_GROUP_X11= OPT1 QT4 QT5

I'd like to be able to allow choosing OPT1,  and either QT4 or QT5. I 
tried doing this:


OPTIONS_RADIO= QTVERSION
OPTIONS_RADIO_QTVERSION= QT4 QT5
OPTIONS_GROUP= X11
OPTIONS_GROUP_X11= OPT1  QTVERSION

But that did not work.


On 7/31/2014 11:54 AM, Warren Block wrote:
Right now, we have no standard method of making options depend on 
other options.  For example, many ports have an X11 option, and later 
options that require X11.  If the user disables X11 but chooses one of 
the options that require it, the best case is that the port build 
stops with a message.  Worst case, it just stops.


We need a way to make options depend on others.  This could be used in 
the option configuration screen.  If the X11 option from the example 
is disabled, all the options that depend on it are also disabled.  
This could also be used for groups.


Of course, it would also be evaluated after the configuration screen, 
stopping with an error message if the required dependencies are not set.


Given that I don't know if this is a good way to name the variables, 
something like (from emulators/virtualbox-ose):


OPTIONS_REQUIRES_X11=QT4

In the configuration screen, the QT4 option is disabled (grayed out) 
unless X11 is on.


If QT4 is on but X11 is not (say, BATCH is used), the build stops with
  option QT4 requires option X11

Groups (single, radio, multi, group) could be made to depend on an 
option, too.  The only difference would be some tuning of the message 
to show the individual option names rather than the group name, which 
the user can't see.

___
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"






smime.p7s
Description: S/MIME Cryptographic Signature

Trying to build a QT5 application

2014-08-01 Thread Daniel Morante

I am trying to create a port for an application that supports both Qt4 
and Qt5.


Qt4 builds fine and I am using the following in the port's Makefile:

QT4_CONFIGURE_WITH=gui=qt4
QT4_USE= qt4=corelib,gui,qmake_build,linguist,uic,moc,rcc,qtestlib_build

For Qt5 I have:

QT5_CONFIGURE_WITH=gui=qt5
QT5_USE= 
qt5=core,gui,dbus,widgets,network,qmake_build,linguisttools,buildtools_build,testlib_build


Using Qt5 fails to configure properly.  It's unable to find "lrelease":

checking for lrelease-qt5... no
checking for lrelease5... no
checking for lrelease... no
configure: error: LRELEASE not found

According to the porters handbook, that should be provided by 
"linguisttools" above.  I also tried with and had the same result:


QT5_USE= 
qt5=core,gui,dbus,widgets,network,qmake_build,linguist,linguisttools,buildtools_build,testlib_build




___
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"

Yet another pkg bug?

2014-08-01 Thread Andrea Venturoli


Hello.

On a 10.0/amd64 system:


# cat /usr/ports/UPDATING

> ...

20140730:
  AFFECTS: users of security/libgcrypt
  AUTHOR: p...@freebsd.org

  libgcrypt has been updated to 1.6.1 and all shared libraries versions have
  been bumped. So you need to rebuild all applications that depend on
  libgcrypt.

  # portmaster -r libgcrypt
or
  # portupgrade -fr security/libgcrypt
or
  # pkg install -fR security/libgcrypt

> ...

# pkg info -r libgcrypt|less
libgcrypt-1.6.1_1:
libgnome-keyring-2.32.0_8
gnupg-2.0.25_1
libxslt-1.1.28_4
# pkg info -r libxslt | less
libxslt-1.1.28_4:
rarian-0.8.1_1
gnome-doc-utils-0.20.10_2
gtk-doc-1.18_1
inkscape-0.48.4_4
vala-0.20.1_1
policykit-gnome-0.9.2_7
raptor2-2.0.14
xmlto-0.0.26_2
shiboken-1.2.2
apiextractor-0.10.10_2
libreoffice-4.2.5_3
# portupgrade -frn libgcrypt
--->  Listing the results (+:done / -:ignored / *:skipped / !:failed)
+ security/libgcrypt (libgcrypt-1.6.1_1 -> libgcrypt-1.6.1_1)
+ textproc/libxslt (libxslt-1.1.28_4 -> libxslt-1.1.28_4)
+ security/gnupg (gnupg-2.0.25_1 -> gnupg-2.0.25_1)
+ security/libgnome-keyring (libgnome-keyring-2.32.0_8 -> 
libgnome-keyring-2.32.0_8)


So, libreoffice is not rebuilt and after "portupgrade -fr libgcrypt"...


# libchk -v | less -S

> ...

Binaries that are linked with: /usr/local/lib/compat/pkg/libgcrypt.so.19
/usr/local/lib/compat/pkg/libsoup-gnome-2.4.so.1.5.0
/usr/local/lib/libreoffice/program/libxsltfilterlo.so


... libreoffice is still using the old library.



Is the command provided in "UPGRADING" wrong?
Is it yet another bug in pkg? In portupgrade? In libreoffice?
Is something wrong in my setup?

 bye & Thanks
av.
___
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: Yet another pkg bug?

2014-08-01 Thread Baptiste Daroussin

On Fri, Aug 01, 2014 at 03:53:56PM +0200, Andrea Venturoli wrote:
> Hello.
> 
> On a 10.0/amd64 system:
> 
> > # cat /usr/ports/UPDATING
>  > ...
> > 20140730:
> >   AFFECTS: users of security/libgcrypt
> >   AUTHOR: p...@freebsd.org
> >
> >   libgcrypt has been updated to 1.6.1 and all shared libraries versions have
> >   been bumped. So you need to rebuild all applications that depend on
> >   libgcrypt.
> >
> >   # portmaster -r libgcrypt
> > or
> >   # portupgrade -fr security/libgcrypt
> > or
> >   # pkg install -fR security/libgcrypt
>  > ...
> > # pkg info -r libgcrypt|less
> > libgcrypt-1.6.1_1:
> > libgnome-keyring-2.32.0_8
> > gnupg-2.0.25_1
> > libxslt-1.1.28_4
> > # pkg info -r libxslt | less
> > libxslt-1.1.28_4:
> > rarian-0.8.1_1
> > gnome-doc-utils-0.20.10_2
> > gtk-doc-1.18_1
> > inkscape-0.48.4_4
> > vala-0.20.1_1
> > policykit-gnome-0.9.2_7
> > raptor2-2.0.14
> > xmlto-0.0.26_2
> > shiboken-1.2.2
> > apiextractor-0.10.10_2
> > libreoffice-4.2.5_3
> > # portupgrade -frn libgcrypt
> > --->  Listing the results (+:done / -:ignored / *:skipped / !:failed)
> > + security/libgcrypt (libgcrypt-1.6.1_1 -> libgcrypt-1.6.1_1)
> > + textproc/libxslt (libxslt-1.1.28_4 -> libxslt-1.1.28_4)
> > + security/gnupg (gnupg-2.0.25_1 -> gnupg-2.0.25_1)
> > + security/libgnome-keyring (libgnome-keyring-2.32.0_8 -> 
> > libgnome-keyring-2.32.0_8)
> 
> So, libreoffice is not rebuilt and after "portupgrade -fr libgcrypt"...
> 
> > # libchk -v | less -S
>  > ...
> > Binaries that are linked with: /usr/local/lib/compat/pkg/libgcrypt.so.19
> > /usr/local/lib/compat/pkg/libsoup-gnome-2.4.so.1.5.0
> > /usr/local/lib/libreoffice/program/libxsltfilterlo.so
> 
> ... libreoffice is still using the old library.
> 
> 
> 
> Is the command provided in "UPGRADING" wrong?
> Is it yet another bug in pkg? In portupgrade? In libreoffice?
> Is something wrong in my setup?
> 

This is not related to pkg

regards,
Bapt


pgpM2zRaWr2Dy.pgp
Description: PGP signature

Re: Yet another pkg bug?

2014-08-01 Thread Andrea Venturoli


On 08/01/14 16:40, Baptiste Daroussin wrote:


This is not related to pkg


Thanks.
So, what's the reason?
Did I setup something wrong?

 bye & Thanks
av.

___
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: OPTIONS_REQUIRES

2014-08-01 Thread Warren Block


On Fri, 1 Aug 2014, Daniel Morante wrote:

I've recently had this issue .  The following forum post provides a decent 
work around for the time being:

https://forums.freebsd.org/viewtopic.php?f=22&t=47412


Yes, that is why I posted here.  By adding this, we can make handling 
option dependencies a lot easier for porters and users.

___
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 meta.txz: Not Found

2014-08-01 Thread Patrick Powell


I updated to pkg-1.3.3 and am getting these annoying messages:

pkg: http://pkg.FreeBSD.org/freebsd:9:x86:64/latest/meta.txz: Not Found
pkg: http://pkg.FreeBSD.org/freebsd:9:x86:64/new_xorg/meta.txz: Not Found

They appear to be harmless,  but is there a way to turn them off or can 
the repository put in meta.txz file?


Ummm... I think that the 'official' FreeBSD repositories should not 
generate these messages...

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

[QAT] 363529: 3x deleted, 1x leftovers

2014-08-01 Thread Ports-QAT

Add devel/cask.

Cask is a project management tool for Emacs that helps automate the package
development cycle; development, dependencies, testing, building, packaging and
more.

Cask can also be used to manage dependencies for your local Emacs
configuration.

Reviewed by:bapt
Approved by:bapt (mentor)
-

  Build ID:  20140731005601-23301
  Job owner: rpa...@freebsd.org
  Buildtime: 41 hours
  Enddate:   Fri, 01 Aug 2014 17:35:43 GMT

  Revision:  363529
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=363529

-

Port:devel/cask 0.7.0

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   DELETED

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   DELETED

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   DELETED

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~rpa...@freebsd.org/20140731005601-23301-389669/cask-0.7.0.log


--
Buildarchive URL: 
redports 
___
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"

getting packages for ports when installing or upgrading

2014-08-01 Thread Hilko Meyer

Hi,

when staging was introduced packages of the ports I built were automagically
generated in /usr/ports/packages. I used 'portupgrade -p' before to get that
functionality so that change was very convenient for me. Got hit by ports/184672
though. But that wasn't a problem because the '-p' option to portupgrade wasn't
needed anymore.

Now I migrated to pkgng and after the change the automatic package generation
stopped. Falling back to 'portupgrade -p' isn't an option cause ports/184672
stil isn't solved.

So a couple of questions:
1. Was the autmotic package building when installing or upgrading after staging
was introduced not intentional? Or why did that behaviour changed again?
2. So how can I get automatically packages from the ports I install or upgrade?
Having to manually execute "make package" every time would be a pita.

regards,
Hilko
___
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: more problems after last upgrade(s) pkg

2014-08-01 Thread Adam McDougall

On 08/01/2014 09:27, Alex Keda wrote:
> first:
> 
> srv7# pkg -v
> 1.3.3
> srv7# uname -a
> FreeBSD srv7.host-food.ru 9.2-RELEASE-p8 FreeBSD 9.2-RELEASE-p8 #0: Mon
> Jun  9 20:12:11 MSK 2014
> t...@srv7.host-food.ru:/usr/obj/usr/src/sys/HOST-FOOD  amd64
> srv7#
> 
> 
> srv7# pkg install -fy ap22-mod_geoip2
> Updating repository catalogue
> HostFood repository is up-to-date
> All repositories are up-to-date
> The following 1 packages will be affected (of 756 checked):
> 
> Installed packages to be REINSTALLED:
> ap22-mod_geoip2-1.2.9 (forced reinstall)
> 
> Fetching ap22-mod_geoip2-1.2.9.txz: 100% of 18
> kB
>   pkg: cached
> package ap22-mod_geoip2-1.2.9: size mismatch, fetching from
> remote
> Fetching ap22-mod_geoip2-1.2.9.txz: 100% of 18
> kB
>   pkg: cached
> package ap22-mod_geoip2-1.2.9: size mismatch, cannot continue
> srv7#
> 
> whats size mismatch? it's my own repo, all ports rebuilded and all pkg
> and repository recreated every day.
> 

I am also getting "size mismatch" on rt-3.8.17_1.txz:

# pkg upgrade -F
...
Proceed with this action [y/N]: y
Fetching t1lib-5.1.2_3,1.txz: 100% of 708 kB
Fetching rt-3.8.17_1.txz: 100% of 2 MB
pkg: cached package rt-3.8.17_1: size mismatch, fetching from remote
Fetching rt-3.8.17_1.txz: 100% of 2 MB
pkg: cached package rt-3.8.17_1: size mismatch, cannot continue

-rw-r--r--  1 mcdouga9  wheel  2923996 Aug  1 12:36 rt-3.8.17_1.txz

I deleted it in poudriere, updated my ports tree to include pkg 1.3.4,
let poudriere compile both of those but I still have the issue.

# pkg rquery %sb rt-3.8.17_1
20164010

___
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"

Apache 24 + mod_perl

2014-08-01 Thread Patrick Powell

Question:  when will mod_perl be available for Apache 24?  Is anybody 
using it (see below), and what problems (if any) were there?  The method 
outlined below may or may not work - I haven't tried it.  Any comments 
or suggestions?


Background:

I wanted to update to Apache 24/FreeBSD 9.2. Everything went fine until 
I hit mod_perl.  The

current Port Makefile as of Fri 01 Aug 2014 is marked as:

.if ${APACHE_VERSION} > 22
BROKEN= Does not build with apache24
.endif

Apparently mod_perl is currently not compatible with Apache24.  The 
perl-modperl mailing list has a posting:


http://mail-archives.apache.org/mod_mbox/perl-modperl/201402.mbox/%3CCADED=k4p2hfc6k1san3mpmm8vz+gwt5rsij5samvlrv7z5z...@mail.gmail.com%3E

This has the following information:
Date: Sun, 16 Feb 2014 15:36:18 GMT


The Debian project is shipping mod_perl with httpd24 support
based on http://svn.apache.org/repos/asf/perl/modperl/branches/httpd24/.


An update on the state of things regarding httpd-2.4 support in mod_perl:

We are working hard to get this done and are 99% of the way there.
Both volunteers and volunteers' time is limited, though, so progress
has been slow. A lot of work has taken place in the httpd24 branch,
and as Dominic says, some Linux distros are already shipping that.

There is also a posting on how to abuse the mod_perl2 port, download the 
source from the SVN repository and force mod_perl2 to compile it:


https://forums.freebsd.org/viewtopic.php?f=5&t=46523



___
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: Apache 24 + mod_perl

2014-08-01 Thread Kurt Jaeger

Hi!

> Question:  when will mod_perl be available for Apache 24?

There's a PR where people are discussing this:

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

This PR needs more testers etc.

-- 
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"

pkg: pkg repo most recent package for origin?

2014-08-01 Thread Gmelin

pkg-repo(8) says:

 To create a package repository catalogue you must specify the
 top-level directory where all the packages are stored as
 repo-path.  pkg repo will search the filesystem beneath repo-path
 to find all the packages it con- tains.  Symbolic links are
 ignored, and *only the most recent package for each origin is
 included in the catalogue.*

I played with this tonight and had a couple of cases where this didn't
work, e.g.

git-1.7.11.5.txz
git-2.0.2.txz

or

pkg-1.3.3.txz
pkg-1.3.4.txz


pkg info -F git-1*
git-1.7.11.5
Name   : git
Version: 1.7.11.5
Installed on   : Thu Jan  1 00:00:00 UTC 1970
Origin : devel/git
...

pkg info -F git-2*
git-2.0.2
Name   : git
Version: 2.0.2
Installed on   : Thu Jan  1 00:00:00 UTC 1970
Origin : devel/git
...

pkg repo . signkey

Creates a repository that only includes git-2.0.2, I have to delete
git-1.7.11.5.txz to create repo that contains the new version.

Is this a bug?

Thanks
Michael

-- 
Michael Gmelin
___
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: pkg repo most recent package for origin?

2014-08-01 Thread Michael Gmelin

pkg-repo(8) says:

 To create a package repository catalogue you must specify the
 top-level directory where all the packages are stored as
 repo-path.  pkg repo will search the filesystem beneath repo-path
 to find all the packages it con- tains.  Symbolic links are
 ignored, and *only the most recent package for each origin is
 included in the catalogue.*

I played with this tonight and had a couple of cases where this didn't
work, e.g.

git-1.7.11.5.txz
git-2.0.2.txz

or

pkg-1.3.3.txz
pkg-1.3.4.txz


pkg info -F git-1*
git-1.7.11.5
Name   : git
Version: 1.7.11.5
Installed on   : Thu Jan  1 00:00:00 UTC 1970
Origin : devel/git
...

pkg info -F git-2*
git-2.0.2
Name   : git
Version: 2.0.2
Installed on   : Thu Jan  1 00:00:00 UTC 1970
Origin : devel/git
...

pkg repo . signkey

Creates a repository that only includes git-2.0.2, I have to delete
git-1.7.11.5.txz to create repo that contains the new version.

Is this a bug?

Thanks
Michael

-- 
Michael Gmelin
___
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: Yet another pkg bug?

2014-08-01 Thread Bryan Drewery


On 2014-08-01 08:53, Andrea Venturoli wrote:

Hello.

On a 10.0/amd64 system:


# cat /usr/ports/UPDATING
...
20140730:
  AFFECTS: users of security/libgcrypt
  AUTHOR: p...@freebsd.org

  libgcrypt has been updated to 1.6.1 and all shared libraries 
versions have

  been bumped. So you need to rebuild all applications that depend on
  libgcrypt.

  # portmaster -r libgcrypt
or
  # portupgrade -fr security/libgcrypt
or
  # pkg install -fR security/libgcrypt
...
# pkg info -r libgcrypt|less
libgcrypt-1.6.1_1:
libgnome-keyring-2.32.0_8
gnupg-2.0.25_1
libxslt-1.1.28_4
# pkg info -r libxslt | less
libxslt-1.1.28_4:
rarian-0.8.1_1
gnome-doc-utils-0.20.10_2
gtk-doc-1.18_1
inkscape-0.48.4_4
vala-0.20.1_1
policykit-gnome-0.9.2_7
raptor2-2.0.14
xmlto-0.0.26_2
shiboken-1.2.2
apiextractor-0.10.10_2
libreoffice-4.2.5_3
# portupgrade -frn libgcrypt
--->  Listing the results (+:done / -:ignored / *:skipped / !:failed)
+ security/libgcrypt (libgcrypt-1.6.1_1 -> libgcrypt-1.6.1_1)
+ textproc/libxslt (libxslt-1.1.28_4 -> libxslt-1.1.28_4)
+ security/gnupg (gnupg-2.0.25_1 -> gnupg-2.0.25_1)
+ security/libgnome-keyring (libgnome-keyring-2.32.0_8 -> 
libgnome-keyring-2.32.0_8)


So, libreoffice is not rebuilt and after "portupgrade -fr libgcrypt"...


# libchk -v | less -S
...
Binaries that are linked with: 
/usr/local/lib/compat/pkg/libgcrypt.so.19

/usr/local/lib/compat/pkg/libsoup-gnome-2.4.so.1.5.0
/usr/local/lib/libreoffice/program/libxsltfilterlo.so


... libreoffice is still using the old library.




Agreed it is not a pkg problem, nor a portupgrade problem.

libreoffice is not directly depending on libgcrypt so it was not 
rebuilt. Only direct dependencies are rebuilt. But this is not really 
the problem. The problem is that Libreoffice seems to be doing something 
special by building its own libxsltfilterlo.so into its own directory. 
So the libxslt rebuild had no idea about it. It's not a file actually 
provided by libxslt.


# pkg info -l libxslt|grep /usr/local/lib
/usr/local/lib/libexslt.a
/usr/local/lib/libexslt.la
/usr/local/lib/libexslt.so
/usr/local/lib/libexslt.so.8
/usr/local/lib/libxslt.a
/usr/local/lib/libxslt.la
/usr/local/lib/libxslt.so
/usr/local/lib/libxslt.so.2

Note the lack of libxsltfilterlo.so.

I'd say the instructions were lacking. My guess is a small handfull of 
people realize what's going on here and none of the other committers do. 
So it's very likely that many UPDATING entries need special libreoffice 
care as well and have not had it documented. I.e., every dependency of 
libreoffice would require rebuilding libreoffice.


I'm not sure what this program/ dir is, perhaps some cache. It would be 
safer to have it disabled so this special care is not needed.





Is the command provided in "UPGRADING" wrong?
Is it yet another bug in pkg? In portupgrade? In libreoffice?
Is something wrong in my setup?

 bye & Thanks
av.

___
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"

devel/pcre is broken. please fix.

2014-08-01 Thread Steve Kargl

% portmaster --force-config devel/pcre

(Select the build with libedit option)
(Do not select the build with readline option)

make
...

===>  Building for pcre-8.34_2
--- all ---
/usr/bin/make  all-am
--- pcretest-pcretest.o ---
--- pcretest-pcre_printint.o ---
--- pcretest-pcretest.o ---
  CC   pcretest-pcretest.o
--- pcretest-pcre_printint.o ---
  CC   pcretest-pcre_printint.o
--- pcretest-pcretest.o ---
pcretest.c:77:10: fatal error: 'readline/readline.h' file not found
#include 
 ^
1 error generated.
*** [pcretest-pcretest.o] Error code 1

make[3]: stopped in /usr/ports/devel/pcre/work/pcre-8.34
1 error

make[3]: stopped in /usr/ports/devel/pcre/work/pcre-8.34
*** [all] Error code 2

make[2]: stopped in /usr/ports/devel/pcre/work/pcre-8.34
1 error


If the port offers an option, then it should be buildable
with that option.  Please fix.

-- 
Steve
___
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"

math/lapack broken

2014-08-01 Thread Steve Kargl

% portmaster --force-config math/lapack

(Select to build/install profiled libraries)

===>>> Port directory: /usr/ports/math/lapack

===>>> This port is marked IGNORE
===>>> you have chosen WITH_PROFILE, but have not installed
   the base system profiling libraries

WTF!.  I know the base system doesn't have the profiled
libraries installed.  I don't need nor want profiled
versions of the base system libraries.  I want profiled
versions of the math/lapack and math/blas libraries.

===>>> If you are sure you can build it, remove the
   IGNORE line in the Makefile and try again.

This is just unbelievably stupid.  Please fix the port.

-- 
Steve
___
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: math/lapack broken

2014-08-01 Thread William Grzybowski

I can't help but notice how unrespectful you have been.
Its not the first message ranting about something broken.

This is a open source project, people work on it in their spare times.
I think you should know that as a src@ committer.

If you do not want to provide a patch for the problem please fill out
a PR (bugs.freebsd.org) and/or contact the maintainer.

Thank you!

On Fri, Aug 1, 2014 at 9:47 PM, Steve Kargl
 wrote:
> % portmaster --force-config math/lapack
>
> (Select to build/install profiled libraries)
>
> ===>>> Port directory: /usr/ports/math/lapack
>
> ===>>> This port is marked IGNORE
> ===>>> you have chosen WITH_PROFILE, but have not installed
>the base system profiling libraries
>
> WTF!.  I know the base system doesn't have the profiled
> libraries installed.  I don't need nor want profiled
> versions of the base system libraries.  I want profiled
> versions of the math/lapack and math/blas libraries.
>
> ===>>> If you are sure you can build it, remove the
>IGNORE line in the Makefile and try again.
>
> This is just unbelievably stupid.  Please fix the port.
>
> --
> Steve
> ___
> 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"



-- 
William Grzybowski / wg
FreeBSD Ports Committer
___
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: math/lapack broken

2014-08-01 Thread Steve Kargl

On Fri, Aug 01, 2014 at 10:14:43PM -0300, William Grzybowski wrote:
> I can't help but notice how unrespectful you have been.
> Its not the first message ranting about something broken.
> 

I can't help but notice how poorly some decisions are made
within the ports community, and no, this isn't the nearly
the first poor decision.

If the port has an option to build the profiled libraries
and that option is selected, then I expect the port to 
build the profiled library.

-- 
Steve
___
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 you maintain which are out of date

Re: OPTIONS_REQUIRES

Trying to build a QT5 application

more problems after last upgrade(s) pkg

more problems фаеук last upgrade(s) pkg

Yet another pkg bug?

Re: Yet another pkg bug?

Re: Yet another pkg bug?

Re: OPTIONS_REQUIRES

pkg meta.txz: Not Found

[QAT] 363529: 3x deleted, 1x leftovers

getting packages for ports when installing or upgrading

Re: more problems after last upgrade(s) pkg

Apache 24 + mod_perl

Re: Apache 24 + mod_perl

pkg: pkg repo most recent package for origin?

pkg: pkg repo most recent package for origin?

Re: Yet another pkg bug?

devel/pcre is broken. please fix.

math/lapack broken

Re: math/lapack broken

Re: math/lapack broken

22 matches

Site Navigation

Mail list logo

Footer information