How much Is Your Opinion Worth?
___ 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"
pkg convert?
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. 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
I haven't tried attempted setting up the snapshot route, but that seems like it would be better choice. I'm sure it is possible. On Sun, Jun 18, 2017 at 9:49 AM, Ben Lavery-Griffiths < ben.lav...@hashbang0.com> 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: Keeping -CURRENT up to date with Poudriere
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 < ben.lav...@hashbang0.com> 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: [PATCH] lang/python27 -- Fix namespace collision
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. > Well, that's inconvenient. Seems attachments are stripped. --- Modules/mathmodule.c.orig 2017-06-18 11:09:05.938222000 -0700 +++ Modules/mathmodule.c2017-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)); } -- 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"
[PATCH] lang/python27 -- Fix namespace collision
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. -- 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"
Keeping -CURRENT up to date with Poudriere
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"