Re: Cant install any perl module via ports "Undefined symbol "PL_tainting"

[Mike Jakubik]

On 2015-11-17 12:58 PM, Mark Martinec wrote:

On 2015-11-17 18:19, Mike Jakubik wrote:

Undefined symbol "PL_tainting" at
/usr/local/lib/perl5/5.16/XSLoader.pm line 68.
 at /usr/local/lib/perl5/site_perl/mach/5.16/Encode.pm line 10.


Looks like a mismatch between a version of perl and a module.


Odd, it was only a minor update, in any case i ended up updating Perl to 
5.20 and rebuilding everything, that did the trick.



I decided to update spamassassin today and its dependencies only to
find out that perl is now somehow broken, i get the following errors
during installation.


Btw, the recent update of p5-Net-DNS to 1.03 broke its compatibility
with spamassassin-3.4.1_4 (as is currently in ports).

So, after you sort out your perl installation, until a better
solution is available, please consider downgrading Net::DNS to 1.02,
e.g. installing it from CPAN. See the recent topic on the
us...@spamassassin.apache.org mailing list:
  "DNS lookups fail with SpamAssassin since Net::DNS 1.03"


Thanks for the info.

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

Re: ports && /etc/ssl/cert.pem

[Kubilay Kocak]

On 18/11/2015 9:23 PM, Matthias Apitz wrote:
> 
> Hello,
> 
> I have on one system (r285885 and ports r392920) a sym link in /etc/ssl:
> 
> $ ls -l /etc/ssl/cert.pem 
> lrwxr-xr-x  1 root  wheel  38 26 Jul 21:19 /etc/ssl/cert.pem -> 
> /usr/local/share/certs/ca-root-nss.crt
> 
> I was not aware of the fact that ports now touch the base system. I saw
> with Google a discussion about ... Can someone please point me to the SVN
> rev in ports (or in base) when this was introduced? Thanks
> 
>   matthias
> 

Hi Matthias,

http://svnweb.freebsd.org/changeset/ports/388657

via:

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

Prior to that, a complementary fix for security/openssl consumers:

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

Re: pkg-fallout mails

[Fernando Apesteguía]

On Wed, Nov 18, 2015 at 11:14 AM, Matthew Seaman  wrote:
> On 2015/11/18 07:04, Fernando Apesteguía wrote:
>> !!! Jail is newer than host. (Jail: 1100090, Host: 1100085) !!!
>> !!! This is not supported. !!!
>> !!! Host kernel must be same or newer than jail. !!!
>> !!! Expect build failures. !!!
>>
>>
>> Can anyone please say if this is expected? Is anyone running
>> tests/changing things in the ports building infrastructure? I could
>> just ignore the mails, but I never received so many of these before.
>
> This warning appears on pretty much all pkg-fallout e-mails for HEAD.
> It is a red-herring, and has nothing at all to do with why the e-mail is
> being sent.  It's just a warning: the host and jail versions are
> sufficiently close there is no actual conflict between the system kernel
> and the jail's userland even though that userland is more recent.

Thanks for the explanation!

>
> The problem that is causing builds to fail in the pkg cluster will
> appear towards the *end* of the build log included in the e-mail.  If
> you're getting these e-mails then the affected port is failing to build
> on at least one of the supported environments where it is expected to
> work.  As port maintainer, you are meant to look into those build
> failures and preferably fix them; not just ignore the e-mails.  If you
> don't understand why this port is failing to build, then there are any
> number of people here who will be happy to assist.

I was just trying to understand why that port that hasn't been updated
in a while was suddenly failing to build... and well... the "Expect
build failures" was kind of an explanation :)

I'll have a look at it as soon as I can.

Cheers.

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

Re: License info Q

[Fabian Keil]

Roger Marquis  wrote:

> I need to get license info from a batch of ports and packages.
> 
> Problem is not all the specified ports/pkgs are installed or have license
> info in their Makefile.  Is there a reliable way to enumerate port or
> package license strings, preferably without fetching a package tarfile?

No. Also note that the "license information" in the Makefiles is often
misleading[1] and thus not particular useful if you actually care about
license compliance.

Unfortunately reporting incorrect license information seems to be
a waste of time so things are unlikely to improve any time soon:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195807

Fabian

[1] The lack of documentation doesn't help.


pgph_mtTcjPG0.pgp
Description: OpenPGP digital signature

Re: License info Q

[Kubilay Kocak]

On 18/11/2015 9:48 PM, Fabian Keil wrote:
> Roger Marquis  wrote:
> 
>> I need to get license info from a batch of ports and packages.
>>
>> Problem is not all the specified ports/pkgs are installed or have license
>> info in their Makefile.  Is there a reliable way to enumerate port or
>> package license strings, preferably without fetching a package tarfile?
> 
> No. Also note that the "license information" in the Makefiles is often
> misleading[1] and thus not particular useful if you actually care about
> license compliance.

Fabian,

If they're incorrect, please submit an issue to rectify them (either in
ports, or upstream), like Awesome George has here:

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

> Unfortunately reporting incorrect license information seems to be
> a waste of time so things are unlikely to improve any time soon:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195807

It's not a waste of time, it's a collaborative effort. For a full and
complete response (that I urge you to read and consider completely), see
the following thread, including my last reply:

https://lists.freebsd.org/pipermail/freebsd-ports/2015-July/099906.html

> Fabian
> 
> [1] The lack of documentation doesn't help.

In the meantime, we'll continue to attempt to annotate software metadata
in the ports tree as best we can.

P.S: Apologies for not honouring your Reply-To.

./koobs

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

Ports with LOCAL/xxx as a MASTER_SITE

[Yuri]

I came across a few ports like this. Most recently www/npm. It usually 
turns out that some slightly modified version of sources is kept there @ 
LOCAL/.


Why not just have the patches under files/ do the modification, so that 
it is public and reproducible? There are also GitHub and Bitbucket, 
among other places, to keep sources. There should be no need to allow 
LOCAL/xxx as a MASTER_SITE nowadays.


I suggest to abolish this practice. Begin with adding a warning to the 
port infrastructure when LOCAL/xxx is specified.


(It makes it more difficult to suggest the patch to such port, because 
outsiders should first "reverse-engineer" the patches, which should have 
been there in files/ in the first place.)


Yuri

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

Re: pkg-fallout mails

[Matthew Seaman]

On 2015/11/18 07:04, Fernando Apesteguía wrote:
> !!! Jail is newer than host. (Jail: 1100090, Host: 1100085) !!!
> !!! This is not supported. !!!
> !!! Host kernel must be same or newer than jail. !!!
> !!! Expect build failures. !!!
> 
> 
> Can anyone please say if this is expected? Is anyone running
> tests/changing things in the ports building infrastructure? I could
> just ignore the mails, but I never received so many of these before.

This warning appears on pretty much all pkg-fallout e-mails for HEAD.
It is a red-herring, and has nothing at all to do with why the e-mail is
being sent.  It's just a warning: the host and jail versions are
sufficiently close there is no actual conflict between the system kernel
and the jail's userland even though that userland is more recent.

The problem that is causing builds to fail in the pkg cluster will
appear towards the *end* of the build log included in the e-mail.  If
you're getting these e-mails then the affected port is failing to build
on at least one of the supported environments where it is expected to
work.  As port maintainer, you are meant to look into those build
failures and preferably fix them; not just ignore the e-mails.  If you
don't understand why this port is failing to build, then there are any
number of people here who will be happy to assist.

Cheers,

Matthew






signature.asc
Description: OpenPGP digital signature

ports && /etc/ssl/cert.pem

[Matthias Apitz]

Hello,

I have on one system (r285885 and ports r392920) a sym link in /etc/ssl:

$ ls -l /etc/ssl/cert.pem 
lrwxr-xr-x  1 root  wheel  38 26 Jul 21:19 /etc/ssl/cert.pem -> 
/usr/local/share/certs/ca-root-nss.crt

I was not aware of the fact that ports now touch the base system. I saw
with Google a discussion about ... Can someone please point me to the SVN
rev in ports (or in base) when this was introduced? Thanks

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de,  http://www.unixarea.de/  ☎ 
+49-176-38902045
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: www/[firefox|libxul]: configure: error: --enable-chrome-format must be set to either jar, flat, or omni

[Christoph Moench-Tegeder]

## O. Hartmann (ohart...@zedat.fu-berlin.de):

> Since the problem now appears to destroy every firefox installation on CURRENT
> (most recent, amd64), the problem got severe for us.

Until evidence to the contrary, I guess it's your local problem.
The --enable-chrome-format argument is set to omni by bsd.gecko.mk,
unless overridden. Check MOZ_OPTIONS and configure output, e.g.
obj-x86_64-portbld-freebsd10.2/.mozconfig.json or
obj-x86_64-portbld-freebsd10.2/js/src/config.status (I hope they
did not change since your version).

Regards,
Christoph

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