Re: [PATCH] lang/python27 -- Fix namespace collision

[Steve Kargl]

On Tue, Jun 20, 2017 at 01:06:28PM +1000, Kubilay Kocak wrote:
> On 6/19/17 4:31 AM, Steve Kargl wrote:
> > On Sun, Jun 18, 2017 at 11:29:05AM -0700, Steve Kargl wrote:
> >> Both IEEE-754 2008 and ISO/IEC TS 18661-4 define the half-cycle
> >> trignometric functions cospi, sinpi, and tanpi.  When libm (aka
> >> math.h) grows support for sinpi(x), lang/python27 has a namespace
> >> collision.  The attached patch fixes the problem.
> >>
> 
> Is this issue relevant only for particular (and/or future) FreeBSD
> versions ('where libm grows supports for x, y') or independent of base
> entirely?

It will be an issue with a future BSD.  It seems to take a long time
before any of my libm improvements are committed.  At the moment, bde
and I are probably the only people with sinpi(x) in our libm.

I do, however, anticipate that glibc will get these functions in
the future as portions of ISO/IEC TS 18661-4 have already been
implemented.

> Also, could you open an upstream issue regarding this please, as a
> long-term target for all local (Python port) patches is that they are
> included upstream.

In the 5 minutes that I've searched, I've found https://bugs.python.org/
but there are no instructions on how to submit a bug report. 

-- 
Steve
20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4
20161221 https://www.youtube.com/watch?v=IbCHE-hONow
___
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: [PATCH] lang/python27 -- Fix namespace collision

[Kubilay Kocak]

On 6/19/17 4:31 AM, Steve Kargl wrote:
> On Sun, Jun 18, 2017 at 11:29:05AM -0700, Steve Kargl wrote:
>> Both IEEE-754 2008 and ISO/IEC TS 18661-4 define the half-cycle
>> trignometric functions cospi, sinpi, and tanpi.  When libm (aka
>> math.h) grows support for sinpi(x), lang/python27 has a namespace
>> collision.  The attached patch fixes the problem.
>>

Hi Steve,

Is this issue relevant only for particular (and/or future) FreeBSD
versions ('where libm grows supports for x, y') or independent of base
entirely?

Also, could you open an upstream issue regarding this please, as a
long-term target for all local (Python port) patches is that they are
included upstream.

This also ensures we can document all patches with their relevant
upstream issue/commit references for our future selves and others.

./koobs

> Well, that's inconvenient.  Seems attachments are stripped.
> 
> --- Modules/mathmodule.c.orig 2017-06-18 11:09:05.938222000 -0700
> +++ Modules/mathmodule.c  2017-06-18 11:09:56.248307000 -0700
> @@ -71,7 +71,7 @@
>  static const double sqrtpi = 1.772453850905516027298167483341145182798;
>  
>  static double
> -sinpi(double x)
> +my_sinpi(double x)
>  {
>  double y, r;
>  int n;
> @@ -270,7 +270,7 @@
> integer. */
>  if (absx > 200.0) {
>  if (x < 0.0) {
> -return 0.0/sinpi(x);
> +return 0.0/my_sinpi(x);
>  }
>  else {
>  errno = ERANGE;
> @@ -294,7 +294,7 @@
>  }
>  z = z * lanczos_g / y;
>  if (x < 0.0) {
> -r = -pi / sinpi(absx) / absx * exp(y) / lanczos_sum(absx);
> +r = -pi / my_sinpi(absx) / absx * exp(y) / lanczos_sum(absx);
>  r -= z * r;
>  if (absx < 140.0) {
>  r /= pow(y, absx - 0.5);
> @@ -366,7 +366,7 @@
>  (x-0.5)*(log(x+lanczos_g-0.5)-1);
>  }
>  else {
> -r = log(pi) - log(fabs(sinpi(absx))) - log(absx) -
> +r = log(pi) - log(fabs(my_sinpi(absx))) - log(absx) -
>  (log(lanczos_sum(absx)) - lanczos_g +
>   (absx-0.5)*(log(absx+lanczos_g-0.5)-1));
>  }
> 


___
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: Keeping -CURRENT up to date with Poudriere

[Jov]

I use -m url=SOMEURL to setup 12-CURRENT jail,like this:

poudriere jail -c -j 12current-20170619 -m url=
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/12.0-CURRENT -v
12-CURRENTCURRENT

When update, I just delete the old jail and setup another new one.

Regards,
Jov

2017-06-20 5:24 GMT+08:00 Matt Smith <matt.x...@gmail.com>:

> On Jun 19 23:14, Jaap Akkerhuis wrote:
>
>>
>> On Jun 19, 2017, at 20:24, Ben Lavery-Griffiths <ben.lav...@hashbang0.com>
>>> wrote:
>>>
>>> Thanks very much,
>>>
>>> I’ll look into doing similar.
>>>
>>
>> What I do is to have STABLE and CURRENT jails using the svn method.
>> Then "poudriere jail -u" takes care of the update.
>>
>>
> Why bother having the system compile it twice? If you use -m src=/usr/src
> then it will just use the already built STABLE world from your host build.
> Easy way to make it synced to the live system. And poudriere jail -u still
> works fine to update it.
>
>
>
> --
> Matt
>
> ___
> 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"
>
___
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 convert?

[Thomas Mueller]

> On 19/06/2017 01:04, Thomas Mueller wrote:
> > Looking through the man page for pkg, I see there is still an entry for 
> > convert ("pkg help convert" or "man pkg-convert").

> DESCRIPTION
> >  pkg convert is used to convert from/to pkg(8) local database to legacy
> >  pkg_install tools format.

> OPTIONS
> >  The following options are supported by pkg convert:

> >  -d pkg_dbdir, --pkg-dbdir pkg_dbdir
> >  The location of the pkg_add(1) dbdir.  Defaults to /var/db/pkg.

> >  -n, --dry-run
> >  Dry-run mode.  Do not actually convert anything.  Just show 
> > what
> >  would be done.

> > What is this?  Looks obsolete to me, I thought the legacy pkg_install tools 
> > format was long gone with no going back.

> > I tried this with -n (dry-run) just for curiosity, and naturally it didn't 
> > work:

> > I got

> > pkg: Unable to open plist file: 
> > /var/db/pkg/texlive-texmf-20150523_3/+CONTENTS
> > Skipping invalid package: /var/db/pkg/texlive-texmf-20150523_3

> > and many more like that.

> > If this legacy functionality is long gone, why is it still in the man page 
> > or "pkg help convert"?

> > I saw it as recently as 11.1-PRERELEASE.

> I believe the documentation is somewhat inaccurate: pkg-convert(8) will
> convert the old pkg_tools format to pkg(8), but not the reverse.

> Yes, this is pretty much of legacy interest only nowadays, but I suspect
> there are still 8.x machines needing upgrade here and there.

> Cheers,

> Matthew

Actually, I have an old FreeBSD 8.2 installation on a 40 GB IDE hard drive, MBR 
with legacy FreeBSD bsdlabel on MBR slice 4, not enough maneuvering space for 
any upgrading.

I had the later thought, pkg is also in NetBSD pkgsrc, maybe pkg convert in 
NetBSD, but I would be inclined to try only on a system already messed up 
sufficiently that there is nothing further to lose.

Or one can use pkgsrc (ouch!) with FreeBSD with old pkg_* tools and decide to 
switch to FreeBSD pkgng format.  

Tom

___
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: Keeping -CURRENT up to date with Poudriere

[Matt Smith]

On Jun 19 23:14, Jaap Akkerhuis wrote:



On Jun 19, 2017, at 20:24, Ben Lavery-Griffiths  
wrote:

Thanks very much,

I’ll look into doing similar.


What I do is to have STABLE and CURRENT jails using the svn method.
Then "poudriere jail -u" takes care of the update.



Why bother having the system compile it twice? If you use -m 
src=/usr/src then it will just use the already built STABLE world from 
your host build. Easy way to make it synced to the live system. And 
poudriere jail -u still works fine to update it.




--
Matt
___
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: Keeping -CURRENT up to date with Poudriere

[Jaap Akkerhuis]

> On Jun 19, 2017, at 20:24, Ben Lavery-Griffiths  
> wrote:
> 
> Thanks very much,
> 
> I’ll look into doing similar.

What I do is to have STABLE and CURRENT jails using the svn method.
Then "poudriere jail -u" takes care of the update.

jaap


signature.asc
Description: Message signed with OpenPGP

Apache 2.4.26

[The Doctor]

Anyone noticing problems with Apache 2.4.26 when trying to replace Apache 
2.4.25 ?

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
Talk Sense to a fool and he calls you foolish - Euripides
___
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: Questions about order of adding application to freebsd ports.

[Kurt Jaeger]

Hi!

> Thank you too, Kurt, I will follow your instructions as you go along.

I've committed the two patches you submitted.

I also added them to the CPAN ticket system attached to the upstream
perl modules, so that the CPAN module maintainer can add them.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
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: Keeping -CURRENT up to date with Poudriere

[Ben Lavery-Griffiths]

Thanks very much,

I’ll look into doing similar.

Thanks again,
Ben

> On 18 Jun 2017, at 20:56, Ultima  wrote:
> 
> Poudriere will update based on how it initially was created
> unless it was modified in 
> /usr/local/etc/poudriere.d/jails/$JAIL/method. For the
> -STABLE and -CURRENT branch, It *may* somehow be
> obtained another way, but usually it has to be compiled
> from the respected branch. So it needs to be manually
> compiled in /usr/src before doing a poudriere update.
> 
> The way I handle multiple branches is adding adding
> multiple in /usr/src, eg /usr/src/head, /usr/src/11-stable,
> then setting the src in that directory with obj in it as well.
> 
> /usr/src/head/src and obj /usr/src/head/obj the method
> will need to be set to src=/usr/src/head/src and object
> export MAKEOBJDIRPREFIX=/usr/src/head/obj in the
> ${JAIL}-poudriere.conf.
> 
> I also make a dataset for each target branch so it can
> be zfs send/received.
> 
> 
> I hope this helps
> Ultima
> 
> On Sun, Jun 18, 2017 at 9:49 AM, Ben Lavery-Griffiths 
> > wrote:
> Hi all,
> 
> I’ve got a 12.0-CURRENT Poudriere jail for ports testing.  Am I right in 
> thinking that when Poudriere updates a jail it uses freebsd-update?  In which 
> case, -STABLE and -CURRENT jails can’t be updated - correct?
> 
> In this case, if I want to get the latest -STABLE or -CURRENT snapshot, will 
> I need to recreate my jail?  Or can Poudriere do it a different way?
> 
> Currently when I try to update I get this:
> 
> > [00:00:00] >> Upgrading using ftp
> > /etc/resolv.conf -> /poudriere/jails/12Ci386/etc/resolv.conf
> > mount: /poudriere/jails/12Ci386/compat: No such file or directory
> > Bad system call (core dumped)
> > 12.0-CURRENT
> > [00:00:01] >> Recording filesystem state for clean… done
> 
> 
> Many thanks,
> Ben
> ___
> 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 
> "
> 

___
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: databases/mariadb101-client broken in the quarterly branch (libressl)

[Xavi Garcia]

After discussing the issue with a colleague, Q3 will be available next week
and perhaps fixing the port in Q2 is not worth the effort if it's working
in HEAD.

I have to test this in our Poudriere running in the lab.

Kind regards,

Xavier Garcia

2017-06-19 14:35 GMT+02:00 Xavi Garcia :

> Hi,
>
> Mariadb101-client stopped compiling with libressl in the quarterly branch
> (2017Q2)  after upgrading to 10.1.23.
>
>
> Can somebody please have a look at:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219045#c16
>
> Kind regards,
>
> Xavier Garcia
>
___
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: Questions about order of adding application to freebsd ports.

[Borodin Oleg]

On Fri, 9 Jun 2017 10:24:38 +0200
Kurt Jaeger  wrote:

> Hi!
> 
> > > > I ask for little advice.
> > > > I wrote web manager X.509 certificates http://minica.unix7.org/ and 
> > > > created a freebsd port for it.
> > > > 
> > > > 1. Who could check quality and security of this code?
> > > 
> > > The committer would check the port quality etc.  
> > 
> > Next dummy question from novice, excuse me =)
> > 
> > How to become a new committer for a new port?  
> 
> There are two roles: The maintainer (the person that decides what
> changes go into a port), and the committer (the person that
> has commit rights to the freebsd port repository).
> 
> For a new port, the submitter of the new port is normally also the
> maintainer.
> 
> I found your port and patches at
> 
> http://minica.unix7.org/
> 
> and will have a look, anyway (if I find the time).
> 
> > > Submit patches via bugs.freebsd.org for the two ports, and
> > > the maintainers will decide if they include them.  
> > 
> > If they do not answer for a long-long time?  
> 
> Then the PR / patch runs into a maintainer timeout (14 days) and any
> committer can override the maintainer (if the patch is valid).
> 
> > Or the committer will have a bad mood?  
> 
> There are more committers, so one committer is hopefully not the bottleneck.
> If one committer is not doing the job, poke another one to ask to take over. 
> 
> > So already it was some times.  
> 
> If you have cases like that (and I'm guilty of that as well),
> post the PR number here and some other committer will pick it up.
> 

Thank you too, Kurt, I will follow your instructions as you go along.


With best regards,

Oleg Borodin
+7-952-058-72-64
boro...@unix7.org
onboro...@gmail.com
___
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"

databases/mariadb101-client broken in the quarterly branch (libressl)

[Xavi Garcia]

Hi,

Mariadb101-client stopped compiling with libressl in the quarterly branch
(2017Q2)  after upgrading to 10.1.23.


Can somebody please have a look at:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219045#c16

Kind regards,

Xavier Garcia
___
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: FreeBSD Port: MailScanner-5.0.3

[DutchDaemon - FreeBSD Forums Administrator]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
 
On 19-6-2017 07:18, Jeff Sickel wrote:
> The MailScanner-5.0.3 update didn’t keep the /usr/local and other FreeBSD 
> standard namespace in place.  I spent quite a bit of time correcting the perl 
> scripts to pick up the /usr/local install locations after the upgrade.  The 
> configuration files and other core pieces of MailScanner seem to keep more 
> standard Linux namespaces with this release.  An upgrade from earlier 
> versions is not recommended on FreeBSD until the correct file locations are 
> handled by default.
Yeah .. https://forums.freebsd.org/threads/61298/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
 
iQEcBAEBCAAGBQJZR772AAoJEA9a9BMWOKcx4u4IALFdgmHYH78bvPlL8ALqZiLw
4Ma9mS73sP98XuSWcKUWzI3c+6piT0Qk1RAn/+OGEK2hj99TNTDWQjOt9Ttlr4TN
iOiA3e9+gsKW3M9TrCzoOTGYj7sDagdzLgU3mH/xfTeHWKyM7J3KFEdqIpV267g6
3Ft69e6A3aUIrqMEtGx6qFl/F2NegoEZrmwMdDGiHceZlPn8wRoc0GPRCZUOZS2B
DvEZuU7tARQ8PaH0H84NL9r7t9e3N84328sPwqll2YyAsymU1Cjvi0MjKppqtFgz
KfwCrIi6AM/h6dkz1vR0eB4HoM/MfC1in0gQSR8nlCStT9iLvFePyOiRmjs0svc=
=HMeS
-END PGP SIGNATURE-

___
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: FreeBSD Port: MailScanner-5.0.3

[wen heping]

Would you have  a look of this PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219938

or file a patch to fix it ?

Thanks !

wen

2017-06-19 13:18 GMT+08:00 Jeff Sickel :
> The MailScanner-5.0.3 update didn’t keep the /usr/local and other FreeBSD 
> standard namespace in place.  I spent quite a bit of time correcting the perl 
> scripts to pick up the /usr/local install locations after the upgrade.  The 
> configuration files and other core pieces of MailScanner seem to keep more 
> standard Linux namespaces with this release.  An upgrade from earlier 
> versions is not recommended on FreeBSD until the correct file locations are 
> handled by default.
>
> Regards,
>
> Jeff Sickel
> Corpus Callosum Corporation
> cel. 312.286.0383
> fax. 847.328.7364
>
>
> ___
> 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"
___
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 convert?

[Matthew Seaman]

On 19/06/2017 01:04, Thomas Mueller wrote:
> Looking through the man page for pkg, I see there is still an entry for 
> convert ("pkg help convert" or "man pkg-convert").
> 
> DESCRIPTION
>  pkg convert is used to convert from/to pkg(8) local database to legacy
>  pkg_install tools format.
> 
> OPTIONS
>  The following options are supported by pkg convert:
> 
>  -d pkg_dbdir, --pkg-dbdir pkg_dbdir
>  The location of the pkg_add(1) dbdir.  Defaults to /var/db/pkg.
> 
>  -n, --dry-run
>  Dry-run mode.  Do not actually convert anything.  Just show what
>  would be done.
> 
> What is this?  Looks obsolete to me, I thought the legacy pkg_install tools 
> format was long gone with no going back.
> 
> I tried this with -n (dry-run) just for curiosity, and naturally it didn't 
> work:
> 
> I got
> 
> pkg: Unable to open plist file: /var/db/pkg/texlive-texmf-20150523_3/+CONTENTS
> Skipping invalid package: /var/db/pkg/texlive-texmf-20150523_3
> 
> and many more like that.
> 
> If this legacy functionality is long gone, why is it still in the man page or 
> "pkg help convert"? 
> 
> I saw it as recently as 11.1-PRERELEASE.

I believe the documentation is somewhat inaccurate: pkg-convert(8) will
convert the old pkg_tools format to pkg(8), but not the reverse.

Yes, this is pretty much of legacy interest only nowadays, but I suspect
there are still 8.x machines needing upgrade here and there.

Cheers,

Matthew





signature.asc
Description: OpenPGP digital signature