texinfo build failure

2017-05-26 Thread Michael Butler
Is anyone else seeing this failure to build texinfo on -CURRENT?

cd doc && gmake TEXMF=/usr/local/share/texmf install-tex
gmake[3]: Entering directory '/usr/ports/print/texinfo/work/texinfo-6.3/doc'
test -n "/usr/local/share/texmf" || (echo "TEXMF must be set." >&2; exit 1)
/bin/sh /usr/ports/print/texinfo/work/texinfo-6.3/build-aux/install-sh
-d /usr/ports/print/texinfo/work/stage/usr/local/share/texmf/tex/texinfo
/usr/ports/print/texinfo/work/stage/usr/local/share/texmf/tex/generic/epsf
install  -m 0644 ./texinfo.tex
/usr/ports/print/texinfo/work/stage/usr/local/share/texmf/tex/texinfo/texinfo.tex
install  -m 0644 ./epsf.tex
/usr/ports/print/texinfo/work/stage/usr/local/share/texmf/tex/generic/epsf/epsf.tex
for f in txi-ca.tex txi-cs.tex txi-de.tex txi-en.tex txi-es.tex
txi-fr.tex txi-hu.tex txi-is.tex txi-it.tex txi-ja.tex txi-nb.tex
txi-nl.tex txi-nn.tex txi-pl.tex txi-pt.tex txi-ru.tex txi-sr.tex
txi-tr.tex txi-uk.tex; do \
  install  -m 0644 ./$f
/usr/ports/print/texinfo/work/stage/usr/local/share/texmf/tex/texinfo/$f;
done
gmake[3]: Leaving directory '/usr/ports/print/texinfo/work/texinfo-6.3/doc'
gmake[2]: Leaving directory '/usr/ports/print/texinfo/work/texinfo-6.3'
install  -m 0644 /usr/ports/distfiles/texinfo/6.3/htmlxref.cnf
/usr/ports/print/texinfo/work/stage/usr/local/share/texinfo
/bin/rmdir /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo
rmdir: /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo: No
such file or directory
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/print/texinfo
*** Error code 1

Stop.
make: stopped in /usr/ports/print/texinfo
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade20170526-91663-1k3i9m0 env UPGRADE_TOOL=portupgrade
UPGRADE_PORT=texinfo-6.3_1,1 UPGRADE_PORT_VER=6.3_1,1 make
** Fix the problem and try again.
___
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: (head users) 64-bit inodes: Packages heads up and Poudriere errors

2017-05-26 Thread Bryan Drewery
On 5/26/2017 8:20 AM, Bryan Drewery wrote:
> For those running FreeBSD head, the ABI was majorly changed in r318736
> for 64-bit inodes.  This change was *backwards compatible* but not
> *forward compatible*.  This is normal and expected.
> 
> For Pkg users:
> 
> You are advised to upgrade your system past r318736 soon or avoid using
> official packages until you do.  Portmgr may upgrade the package
> builders at any time and without much notice.

I had forgotten a detail here.  The package builds are all automated.
The source jails are automatically updated before a build.  The package
builder's kernel doesn't matter here.  So head package builds _will_ be
ABI broken for systems older than r318736 either now or in the next day
or two once the builds finish and upload to the mirrors.

-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature


FreeBSD ports you maintain which are out of date

2017-05-26 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
+-+
lang/micropython| 1.5.1   | v1.9
+-+


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
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


(head users) 64-bit inodes: Packages heads up and Poudriere errors

2017-05-26 Thread Bryan Drewery

For those running FreeBSD head, the ABI was majorly changed in r318736
for 64-bit inodes.  This change was *backwards compatible* but not
*forward compatible*.  This is normal and expected.

For Pkg users:

You are advised to upgrade your system past r318736 soon or avoid using
official packages until you do.  Portmgr may upgrade the package
builders at any time and without much notice.

For Poudriere users:

What this means is that you may see warnings like this in Poudriere:

> [00:00:01] >> Warning: !!! Jail is newer than host. (Jail: 1200031, Host: 
> 1200030) !!!
> [00:00:01] >> Warning: This is not supported.
> [00:00:01] >> Warning: Host kernel must be same or newer than jail.
> [00:00:01] >> Warning: Expect build failures.

This warning is quite old and usually can be ignored as the
__FreeBSD_version number it is tracking is normally bumped for minor
things.  Large ABI breakage is relatively rare.  In this case it matters
though.

...
> [00:00:03] >> Starting jail exp-head-commit-test
> [00:00:03] >> Error: Unable to execute id(1) in jail. Emulation or ABI 
> wrong.

This is due to the ABI breakage - your older kernel cannot run the newer
binary from the jail.  The solution is to upgrade your host system past
r318736.  Be sure to follow the proper (and normal) upgrade procedure as
documented in UPDATING.
(For people finding this error on Google, it can indicate anything wrong
in the jail that is disallowing binaries from running from a broken QEMU
to a non-forward-compatible ABI change to simply missing files or broke
jail setup)

Lastly, Poudriere normally automatically rebuilds packages for head
jails anytime the VCS revision is changed, so SVN revision or GIT hash.
This is important in these ABI-breaking cases as you want all packages
to use the new ABI.  I am changing this in the next Poudriere updates to
track __FreeBSD_version for svn/git/-m src= builds.  It will still
continue to track "Release name" for other methods.  This will do 2 things:
1. Rebuild less often and only when someone updates __FreeBSD_version.
This is more proper and we should strive to update this only as needed
to rebuild things.
2. Fix -m src= *not* rebuilding packages after the recent ABI breakage.
If your jail uses -m src= I recommend forcifully doing a bulk -c once to
ensure you get working packages.


-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature


Re: Port for Resilio Sync

2017-05-26 Thread Kurt Jaeger
Hi!

> I presently use Resilio Sync 2.5 on my Windows based machines. I see
> that there is a version available for FreeBSD
> .
> I was wondering if there is a port of this application?

Not as far as I can see.

The distfiles just contain a binary, so a port is probably easy.

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


Port for Resilio Sync

2017-05-26 Thread Gerard Seibert
I presently use Resilio Sync 2.5 on my Windows based machines. I see
that there is a version available for FreeBSD
.
I was wondering if there is a port of this application? I could not
find one, but FreeBSD tends to change the names of applications in the
port system making it somewhat difficult to locate specific programs.

Thanks!

-- 
Carmel
___
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: Document for OPTIONS syntax in /etc/make.conf, where to find?

2017-05-26 Thread Thomas Mueller

> On 25 May 2017 at 19:47, Thomas Mueller  wrote:
[...]
> > The new synth has no mechanism for configuring options; I guess that would 
> > have to be done by
> > make config-recursive ,
> > possibly several times until there is nothing more left to configure, as I 
> > did when using portupgrade and later portmaster.

> >From synth(1) man page:
 -make.conf
   This is an optional, user-provided file. If it exists,
   the builder's /etc/make.conf will be appended with the
   contents of this file. For the default profile, the
   file would normally be located at
   /usr/local/etc/synth/LiveSystem-make.conf

> Cheers.

> Jonathan Chen 

Thanks for the tip.

I already have read the man page because I git-cloned synth tree from github 
repository.

I want to keep the Ada code for viewing, among other things.

My first attempt to build synth was on FreeBSD-current amd64 and failed when 
the system rebooted itself when I was sleeping.  Apparently no filesystem 
damage.

System came up in System Rescue CD 5.0.0 USB-stick installation.

I attribute this to FreeBSD-current instability rather than synth or ports, 
meaning I must first rebuild FreeBSD 11.0-STABLE amd64 installation, and then 
from there, FreeBSD-current amd64.

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"