On 4/1/2015 1:54 AM, Don Lewis wrote:
> I'm working on a couple of new ports where I'm using fetching the
> distfiles from github. One quirk is that the tags start with a prefix
> of "tags/v". I'm setting PKGNAMEPREFIX=${PYTHON_PKGNAMEPREFIX}.
>
> If I follow the example for in the Porters Handb
On 1 Apr, Bryan Drewery wrote:
> On 4/1/2015 1:54 AM, Don Lewis wrote:
>> I'm working on a couple of new ports where I'm using fetching the
>> distfiles from github. One quirk is that the tags start with a prefix
>> of "tags/v". I'm setting PKGNAMEPREFIX=${PYTHON_PKGNAMEPREFIX}.
>>
>> If I foll
On 31.03.2015 21:03, Baptiste Daroussin wrote:
> - pkg has grown with an initial support for provides/requires: this is a naive
> version but good enough to at least make major upgrade of php safer as well
> as
> making pear/pecl maintenance saner (note that this will need modifications
> in
On 4/1/2015 2:13 AM, Don Lewis wrote:
> On 1 Apr, Bryan Drewery wrote:
>> On 4/1/2015 1:54 AM, Don Lewis wrote:
>>> I'm working on a couple of new ports where I'm using fetching the
>>> distfiles from github. One quirk is that the tags start with a prefix
>>> of "tags/v". I'm setting PKGNAMEPREF
On 1 Apr, Bryan Drewery wrote:
> On 4/1/2015 2:13 AM, Don Lewis wrote:
>> On 1 Apr, Bryan Drewery wrote:
>>> On 4/1/2015 1:54 AM, Don Lewis wrote:
I'm working on a couple of new ports where I'm using fetching the
distfiles from github. One quirk is that the tags start with a prefix
>>>
Hello port maintainers,
I use boinc-client on 10.1-RELEASE-p6. I found that at least one MilkyWay@Home
task needs libstdc++.so.6, so I had install lang/gcc to make it work.
Mabye it makes sense to add lang/gcc as a dependency for boinc-client or just
add a note
that some BOINC projects or proje
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
Hello,
I maintain 4 different ports. The port maintainer email address listed with
the ports have been harvested by spammers and I am now receiving over 100
spam emails per email address each day.
The ports in question do not require update. Just want to change the
maintainer email address.
Is th
Submit patches in bugzilla with the diff from your new mail account. Login
with your old mail account and approve the patches. Someone will take care
of it.
On Wed, Apr 1, 2015 at 4:37 PM, joeb1 wrote:
> Hello,
>
> I maintain 4 different ports. The port maintainer email address listed with
> the
Excerpt from Baptiste Daroussin:
- Initial support for OS X
- Initial support for NetBSD/EdjeBSD
How would pkg-1.5.0 integrate with NetBSD pkgsrc?
I didn't think there were any plans to port FreeBSD ports to NetBSD. Or is
such a plan in the works?
EdjeBSD should be EdgeBSD. A little spelling
On Wed, Apr 01, 2015 at 11:48:27AM +, Thomas Mueller wrote:
> Excerpt from Baptiste Daroussin:
>
> - Initial support for OS X
> - Initial support for NetBSD/EdjeBSD
>
> How would pkg-1.5.0 integrate with NetBSD pkgsrc?
>
> I didn't think there were any plans to port FreeBSD ports to NetBSD.
> I would propose to add something like WSREP knob to existing mysql*-server
ports that adds the extra patches and then make slaves with WSREP option
selected
That's a great idea, Nikolai!
And I think databases/galera should be renamed to something more obvious,
like databases/galera-plugin or so
On 1 Apr 2015, at 05:03, Rui Paulo wrote:
>
> That is expected. WITH_PKG=devel is a make(1) option that only affects ports
> (non-binary pkgs).
Are you sure? I have it in make.conf on one of my systems where I never build
ports manually (and don't even have a ports tree installed) and there
Upgrading libdrm to version 2.4.58 fails:
root@kg-v7# uname -a
FreeBSD kg-v7.kg4.no 10.1-STABLE FreeBSD 10.1-STABLE #0 r278322: Fri
Feb 6 21:36:01 CET 2015
r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
root@kg-v7# pv libdrm*
[Reading data from pkg(8) ... - 488 packages found - done]
libdrm
On Wed, Apr 01, 2015 at 01:56:38PM +0100, David Chisnall wrote:
> On 1 Apr 2015, at 05:03, Rui Paulo wrote:
> >
> > That is expected. WITH_PKG=devel is a make(1) option that only affects
> > ports (non-binary pkgs).
>
> Are you sure? I have it in make.conf on one of my systems where I never
Hi,
The 2015Q2 branch has been created. It means that the next update on the
quarterly packages will be on the 2015Q2 branch
A lot of things happened in the last three months:
- pkg 1.4.12
- New USES: blaslapack, fonts, metaport, xfce
- Removed keywords: @fc, @fontsdir
- Default version of MySQL
I was getting indications that mysql connections through the com.mysql.jdbc
driver was not working. So I searched for a test method (included below) and
here are the results.
* Server: mariadb100--10.0.17, jailed, tcp connection. Able to connect through
other drivers & using same params.
* Clie
On 1-4-2015 15:06, Torfinn Ingolfsen wrote:
1 warning generated.
CCLD modetest
libtool: link: cannot find the library
`/usr/local/lib/libfontconfig.la' or unhandled argument
`/usr/local/lib/libfontconfig.la'
Makefile:418: recipe for target 'modetest' failed
gmake[5]: *** [modetest] Error 1
This port is failing to install at the moment. Is there a bug in
autoplist? I've opened the following bug report:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199021
Using make makeplist seems to work around this problem, but is suboptimal.
___
free
On 04/01/15 15:31, Beeblebrox via freebsd-ports wrote:
> I was getting indications that mysql connections through the com.mysql.jdbc
> driver was not working. So I searched for a test method (included below) and
> here are the results.
>
> * Server: mariadb100--10.0.17, jailed, tcp connection. A
Thanks Matt.
I forgot to mention that my make.conf has these defined (however redundant or
ridiculous):
JAVA_PREFERRED_PORTS= JAVA_PORT_NATIVE_OPENJDK_JDK_1_8
JAVA_PORT_VERSION= 1.8+
JAVA_DEFAULT?= 1.8+
OVERRIDE_JAVA_VERSION= 1.8+
JAVA_OS=native
JAVA_VERSION=
On Wed, 1 Apr 2015, joeb1 wrote:
> I maintain 4 different ports. The port maintainer email address listed
> with the ports have been harvested by spammers and I am now receiving
> over 100 spam emails per email address each day.
Doesn't a1poweruser.com use spam filters such as the various DNSBL
I use pkg upgrade to maintain most of my ports but a small number need to be
built
from source. To avoid problems I aim to keep my ports tree in sync with the
snapshots
used by the package cluster.
Until a couple of weeks ago I was able to obtain the revision number of the
ports
snapshot by
Update,
On Wed, Apr 1, 2015 at 4:40 PM, Koop Mast wrote:
>
> Please read ports/UPDATING entry 20140909 for instructions for a solution
> how to deal with missing .la files.
>
Thanks for the hint, but it doesn't appear to be any missing ("not
found in the database") files:
root@kg-v7# find /usr/
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'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/01/2015 16:59, 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 o
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
On 04/01/2015 14:17, Jung-uk Kim wrote:
I know bsd.openssl.mk has been broken for very long time. For example,
http://docs.freebsd.org/cgi/mid.cgi?50108FEF.3030405
However, I am not sure whether entirely removing it is the best way
going forward.
I mean, removing of the dependency on base. P
On Wed, Apr 1, 2015 at 10:52 PM, Torfinn Ingolfsen wrote:
> Update,
>
>
> Furthermore, how do I rebuiuld all these ports? They all refer to
> (have as dependency) the libdrm port, and therefore fail when I try to
> portupgrade them.
I figured it out; I had to rebuild a few (about a handful) ports
On 04/01/15 23: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 openss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/01/2015 17:21, Yuri wrote:
> On 04/01/2015 14:17, Jung-uk Kim wrote:
>> I know bsd.openssl.mk has been broken for very long time. For
>> example,
>>
>> http://docs.freebsd.org/cgi/mid.cgi?50108FEF.3030405
>>
>> However, I am not sure whether
> On 01 Apr 2015, at 23: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
>> p
+--On 1 avril 2015 14:21:48 -0700 Yuri wrote:
| On 04/01/2015 14:17, Jung-uk Kim wrote:
|> I know bsd.openssl.mk has been broken for very long time. For example,
|>
|> http://docs.freebsd.org/cgi/mid.cgi?50108FEF.3030405
|>
|> However, I am not sure whether entirely removing it is the best way
On 04/01/2015 14:30, Guido Falsi wrote:
Some examples of things that could (and will) go wrong:
- ports silently linking to base ssl due to weirdness in their build scripts
- ports linking to other libraries in base which are linked to base ssl,
causing conflicts
- ports interacting with base
On 04/01/15 23:21, Yuri wrote:
> On 04/01/2015 14:17, Jung-uk Kim wrote:
>> I know bsd.openssl.mk has been broken for very long time. For example,
>>
>> http://docs.freebsd.org/cgi/mid.cgi?50108FEF.3030405
>>
>> However, I am not sure whether entirely removing it is the best way
>> going forward.
Le mer 1 avr 15 à 22:59:56 +0200, Yuri
écrivait :
> 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 he
On Wed, Apr 01, 2015 at 11:30:20PM +0200 I heard the voice of
Guido Falsi, and lo! it spake thus:
>
> - ports linking to other libraries in base which are linked to base ssl,
> causing conflicts
On my system, libssl/libcrypto is used by:
/usr/lib/libarchive.so
/usr/lib/libbsnmp.so
/usr/lib/libfe
On 04/01/15 23:37, Yuri wrote:
> On 04/01/2015 14:30, Guido Falsi wrote:
>> Some examples of things that could (and will) go wrong:
>>
>> - ports silently linking to base ssl due to weirdness in their build
>> scripts
>>
>> - ports linking to other libraries in base which are linked to base ssl,
>>
On 04/01/2015 15:08, Guido Falsi wrote:
This would be good.
What I am most worried about, though, are problems showing up at runtime
only on specific configurations or use cases.
This would help nailing them down.
Such stage-qa check will currently likely fail on many ports. It can
help in t
I implemented the new 'basemix' stage-qa test:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199106
Currently it complains about libssl.so libcrypto.so from base.
Yuri
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/li
> On 1 April 2015, at 14:21, Yuri wrote:
>
> On 04/01/2015 14:17, Jung-uk Kim wrote:
>> I know bsd.openssl.mk has been broken for very long time. For example,
>>
>> http://docs.freebsd.org/cgi/mid.cgi?50108FEF.3030405
>>
>> However, I am not sure whether entirely removing it is the best way
>
41 matches
Mail list logo
