Re: FreeBSD Port: MailScanner-5.0.3

___ 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 does not upgrade if more than one repository is defined

Am 28.07.2017 um 13:13 schrieb Matt Smith: > > This might also be related to the CONSERVATIVE_UPGRADE setting of > pkg.conf. According to the man page: > > CONSERVATIVE_UPGRADE: boolean > Ensure in multi repository mode that the priority is > given as much as possible to the repository where a >

Re: rust problem

But you are right. I got it to compile in the port with WITHOUT_FBSD10_FIX=yes (I think this unlogical, but it seems to work). ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any

Re: FreeBSD Port: MailScanner-5.0.3

After your commit, I now get an error during staging: (00:00:54) === (00:00:54) === (00:00:54) ===> Staging for MailScanner-5.0.3_1 (00:00:54) ** Missing

rust problem

Rust does not compile in the port on 10.3 amd64. error: the listed checksum of `/usr/ports/lang/rust/work/rustc-1.19.0-src/src/vendor/lzma-sys/xz-5.2.3/build-aux/config.rpath` has changed: expected: c8b4c017079da9dfb3086a0583e60ffe736184d89005dc5973f0bb0fd17c04bb actual:

Re: rust problem

Am 29.07.2017 um 14:01 schrieb Christoph Moench-Tegeder: > ## Christoph Moench-Tegeder (c...@burggraben.net): > >>> I mailed it the maintainer. He said it is a local problem. >> I'd like to disagree: the problem is caused by this: > I have to retract this: a poudriere build (10.3 again)

Re: Trying to get poudriere to start

Op 29-7-2017 om 13:34 schreef Chris Rees: On 29 Jul 2017 11:56, Willem Jan Withagen wrote: Op 28-7-2017 om 22:50 schreef Chris Rees: On 26 Jul 2017 23:59, Willem Jan Withagen wrote: Op

Re: JVM based port dependencies?

2017-07-20 21:27 GMT+03:00 Dmytro Bilokha : > 20 липня 2017 р. 18:17:13 GMT+02:00, Pavel Timofeev > написав: >> >> Hello! >> What is the best practice for ports running on top of JVM (like >> ZooKeeper or ElasticSearch): >> use all bundled jars (for example,

Re: Clang5 crashing on RPI2 compiling gnome3

On 29 Jul 2017, at 03:09, bob prohaska wrote: > > Attempts to compile gnome3 on an RPI2 have run hard aground on > > :57:6: note: expanded from here > Assertion failed: (0 <= N && N < static_cast(m_byteToColumn.size())), > function byteToContainingColumn, file >

Re: Trying to get poudriere to start

Op 28-7-2017 om 22:50 schreef Chris Rees: On 26 Jul 2017 23:59, Willem Jan Withagen wrote: Op 27-7-2017 om 00:48 schreef Miroslav Lachman: > Willem Jan Withagen wrote on 2017/07/26 23:24: >> Hi, >> >> This has been working, but now the jail does not

Re: rust problem

## Walter Schwarzenfeld (w.schwarzenf...@utanet.at): > Rust does not compile in the port on 10.3 amd64. I'm just debugging the very same problem. > I mailed it the maintainer. He said it is a local problem. I'd like to disagree: the problem is caused by this: ===> Configuring for rust-1.19.0

Re: Trying to get poudriere to start

___ 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: rust problem

## Christoph Moench-Tegeder (c...@burggraben.net): > > I mailed it the maintainer. He said it is a local problem. > > I'd like to disagree: the problem is caused by this: I have to retract this: a poudriere build (10.3 again) completes. That shows that the rust build suffers from some

FreeBSD 11.0 to FreeBSD 11.1 update concerns

[2]: stopped in /usr/source/openssl-1.0.2-stable-SNAP-20170729 *** Error code 1 Stop. make[1]: stopped in /usr/source/openssl-1.0.2-stable-SNAP-20170729/crypto *** Error code 1 Stop. make: stopped in /usr/source/openssl-1.0.2-stable-SNAP-20170729 Huh?? 2) Updating dns/bind911 with threads checki