net/samba43's NSUPDATE
(Please forgive me if this arrives twice... I sent it yesterday, but I don't see it on the ML.) Hello. Forgive me, but I'm quite new to AD and I've been searching the web for a couple of days, but found nothing relevant... What's exaclty the NSUPDATE option of this port? Is it intended to work with BIND (like the other two in that group)? What are its requirements? Any reference to a tutorial or any other documentation on how to use it? bye & Thanks av. ___ 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: WANT_BDB_VER Ignored
Daniel Morante skrev: > > I have the following in a port Makefile: > USE_BDB=yes > WANT_BDB_VER=48 Is your ports tree up-to-date? Try: USES= bdb:48 Check Uses/bdb.mk for available options. -- Herbert ___ 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: WANT_BDB_VER Ignored
Herbert J Skuhra skrev: > > Daniel Morante skrev: >> >> I have the following in a port Makefile: >> USE_BDB=yes >> WANT_BDB_VER=48 > > Is your ports tree up-to-date? > > Try: USES= bdb:48 > > Check Uses/bdb.mk for available options. Should be /usr/ports/Mk/Uses/bdb.mk. -- Herbert ___ 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: WANT_BDB_VER Ignored
+--On 26 avril 2016 22:24:34 -0400 Daniel Morante wrote: | I have the following in a port Makefile: | | USE_BDB=yes | WANT_BDB_VER=48 Mmm, WANT_BDB_VER is not supported any more, like the commit says, use USES=bdb:48. -- Mathieu Arnold pgpMgupFH4L8t.pgp Description: PGP signature
FreeBSD ports you maintain which are out of date
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 +-+ emulators/mame | 0.166 | mame0173 +-+ emulators/mess | 0.166 | mame0173 +-+ textproc/elasticsearch-plugin-marvel| 1.3.1 | 2.3.2 +-+ 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"
FreeBSD Port: owncloud-9.0.1_1
Hello,
I'm currently trying to setup Owncloud on FreeBSD 10.2.
I'm using the provided files_external app to give access to SMB shares, but it
fails when I try to upload files.
looking at apache's logs reveal many errors:
net: not found
net: not found
ps: illegal option -- -
usage: ps [-aCcdefHhjlmrSTuvwXxZ] [-O fmt | -o fmt] [-G gid[,gid...]]
[-J jid[,jid...]] [-M core] [-N system]
[-p pid[,pid...]] [-t tty[,tty...]] [-U user[,user...]]
ps [-L]
net: not found
net: not found
net: not found
digging in the code shows things like:
preg_split('/\s+/', `ps -o pid --no-heading --ppid $ppid`);
(from apps/files_external/3rdparty/icewind/smb/src/RawConnection.php)
which will never work on FreeBSD because it requires a GNU ps...
Similarly, in apps/files_external/3rdparty/icewind/smb/src/Server.php and
apps/files_external/3rdparty/icewind/smb/src/Share.php some references to
/proc/self/fd exist that must be changed in /dev/fd.
Is there any plan to patch linux-only commands and paths in Owncloud
package/port?
thanks,
Patrick
___
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: HTML5 videos crashes Firefox
On 04/27/16 08:41, Andrea Venturoli wrote: On 03/29/16 18:20, Andrea Venturoli wrote: So do I, but I've gone through every minor update since I'm experiencing these crashes. Just to say version 46 works fine again. Forget this. Youtube works, but other sites are still crashing :( bye av. ___ 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 tree gone unstable?
After a portsnap update it seems all my jails won't build the current tree returning the following error: >> MOVED: sysutils/puppet renamed to sysutils/puppet38 >> MOVED: textproc/rubygem-augeas renamed to textproc/rubygem-ruby-augeas >> Computing deps for converters/libiconv >> Computing deps for archivers/unzip >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-Encode >> Computing deps for converters/p5-Convert-BinHex >> Computing deps for converters/p5-Encode-Locale >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-JSON-PP >> Computing deps for converters/p5-JSON >> Computing deps for converters/p5-JSON-XS >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-Text-Iconv >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/ip4r >> Computing deps for databases/gdbm >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/p5-Bucardo >> Error: Invalid port origin '/usr/local/bin/ccache' not found. Terminated Terminated Terminated Terminated >> Cleaning up >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/p5-DBD-Pg >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/memcached >> Error: Invalid port origin '/usr/local/bin/automake-1.15' not found. >> Umounting file systems Checked updating but don't see anything to suggest that port origins of '/usr/local/bin/ccache' are normal.. Regards, -- Michelle Sullivan http://www.mhix.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"
Internal Breach - Security Report #305767
== IMPORTANT INFORMATION == Firewall Red Alert. Security Attack Detected. IP: 184.298.374.98 PORT: 8600 TIME: 09:08 AM (GMT-6) DATA: APRIL 11, 2016 PROVIDE: COX COMMUNICATIONS LOCATION: CHICAGO, ILLINOIS In order to review the further information and take all the required actions, please check the report enclosed down below. ___ 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 tree gone unstable?
On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan wrote: > After a portsnap update it seems all my jails won't build the current tree > returning the following error: > > >> MOVED: sysutils/puppet renamed to sysutils/puppet38 > >> MOVED: textproc/rubygem-augeas renamed to > textproc/rubygem-ruby-augeas > > >> Computing deps for converters/libiconv > >> Computing deps for archivers/unzip > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > > >> Computing deps for converters/p5-Encode > >> Computing deps for converters/p5-Convert-BinHex > >> Computing deps for converters/p5-Encode-Locale > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for converters/p5-JSON-PP > >> Computing deps for converters/p5-JSON > >> Computing deps for converters/p5-JSON-XS > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > > >> Computing deps for converters/p5-Text-Iconv > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/ip4r > >> Computing deps for databases/gdbm > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/p5-Bucardo > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > > Terminated > Terminated > Terminated > Terminated > >> Cleaning up > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/p5-DBD-Pg > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/memcached > >> Error: Invalid port origin '/usr/local/bin/automake-1.15' not found. > >> Umounting file systems > > Checked updating but don't see anything to suggest that port origins of > '/usr/local/bin/ccache' are normal.. > > Regards, > > > -- > Michelle Sullivan > http://www.mhix.org/ > I could be entirely wrong, but I think that you are misinterpreting the error. It looks to me like it fails to find the origins of ports because it can't find ccache. Have you confirmed that /usr/local/bin/ccache exists and is available to the jail? -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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 tree gone unstable?
Kevin Oberman wrote: On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan wrote: After a portsnap update it seems all my jails won't build the current tree returning the following error: >> MOVED: sysutils/puppet renamed to sysutils/puppet38 >> MOVED: textproc/rubygem-augeas renamed to textproc/rubygem-ruby-augeas >> Computing deps for converters/libiconv >> Computing deps for archivers/unzip >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-Encode >> Computing deps for converters/p5-Convert-BinHex >> Computing deps for converters/p5-Encode-Locale >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-JSON-PP >> Computing deps for converters/p5-JSON >> Computing deps for converters/p5-JSON-XS >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-Text-Iconv >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/ip4r >> Computing deps for databases/gdbm >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/p5-Bucardo >> Error: Invalid port origin '/usr/local/bin/ccache' not found. Terminated Terminated Terminated Terminated >> Cleaning up >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/p5-DBD-Pg >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/memcached >> Error: Invalid port origin '/usr/local/bin/automake-1.15' not found. >> Umounting file systems Checked updating but don't see anything to suggest that port origins of '/usr/local/bin/ccache' are normal.. Regards, -- Michelle Sullivan http://www.mhix.org/ I could be entirely wrong, but I think that you are misinterpreting the error. It looks to me like it fails to find the origins of ports because it can't find ccache. I hadn't considered that but sounds a little assine doesn't it? Have you confirmed that /usr/local/bin/ccache exists and is available to the jail? Yeah it is, even tried installing it into the reference jail by hand to be sure (though it really should be installed if and when needed for the builds) Regards, -- Michelle Sullivan http://www.mhix.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: Ports tree gone unstable?
On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan wrote: > Kevin Oberman wrote: > >> On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan >> wrote: >> >> After a portsnap update it seems all my jails won't build the current tree >>> returning the following error: >>> >>> >> MOVED: sysutils/puppet renamed to sysutils/puppet38 >>> >> MOVED: textproc/rubygem-augeas renamed to >>> textproc/rubygem-ruby-augeas >>> >>> >> Computing deps for converters/libiconv >>> >> Computing deps for archivers/unzip >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >>> >> Computing deps for converters/p5-Encode >>> >> Computing deps for converters/p5-Convert-BinHex >>> >> Computing deps for converters/p5-Encode-Locale >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Computing deps for converters/p5-JSON-PP >>> >> Computing deps for converters/p5-JSON >>> >> Computing deps for converters/p5-JSON-XS >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >>> >> Computing deps for converters/p5-Text-Iconv >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Computing deps for databases/ip4r >>> >> Computing deps for databases/gdbm >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Computing deps for databases/p5-Bucardo >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >>> Terminated >>> Terminated >>> Terminated >>> Terminated >>> >> Cleaning up >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Computing deps for databases/p5-DBD-Pg >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Computing deps for databases/memcached >>> >> Error: Invalid port origin '/usr/local/bin/automake-1.15' not >>> found. >>> >> Umounting file systems >>> >>> Checked updating but don't see anything to suggest that port origins of >>> '/usr/local/bin/ccache' are normal.. >> >> It looks like you're building with Poudriere. I observed similar behavior, but not the exact message the other day. I don't remember what origin it was complaining about, but located a post (either on a mailing list or forums) recommending a `pkg install poudriere`. It did resolve the problem in this particular scenario. -- Take care Rick Miller ___ 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 tree gone unstable?
On 27 Apr, Rick Miller wrote:
> On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
> wrote:
>
>> Kevin Oberman wrote:
>>
>>> On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
>>> wrote:
>>>
>>> After a portsnap update it seems all my jails won't build the current tree
returning the following error:
>> MOVED: sysutils/puppet renamed to sysutils/puppet38
>> MOVED: textproc/rubygem-augeas renamed to
textproc/rubygem-ruby-augeas
>> Computing deps for converters/libiconv
>> Computing deps for archivers/unzip
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-Encode
>> Computing deps for converters/p5-Convert-BinHex
>> Computing deps for converters/p5-Encode-Locale
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-JSON-PP
>> Computing deps for converters/p5-JSON
>> Computing deps for converters/p5-JSON-XS
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-Text-Iconv
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/ip4r
>> Computing deps for databases/gdbm
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/p5-Bucardo
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
Terminated
Terminated
Terminated
Terminated
>> Cleaning up
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/p5-DBD-Pg
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/memcached
>> Error: Invalid port origin '/usr/local/bin/automake-1.15' not
found.
>> Umounting file systems
Checked updating but don't see anything to suggest that port origins of
'/usr/local/bin/ccache' are normal..
>>>
>>>
> It looks like you're building with Poudriere. I observed similar behavior,
> but not the exact message the other day. I don't remember what origin it
> was complaining about, but located a post (either on a mailing list or
> forums) recommending a `pkg install poudriere`. It did resolve the problem
> in this particular scenario.
This is probably caused by the recent change to globally drop
${PORTSDIR} from *_DEPENDS. The framework changes initially were done
in bsd.port.mk r399278, but the the actual removal of ${PORTSDIR} didn't
happen until r411970, r412342, ...
___
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 tree gone unstable?
Rick Miller wrote: On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan wrote: Kevin Oberman wrote: On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan wrote: After a portsnap update it seems all my jails won't build the current tree returning the following error: >> MOVED: sysutils/puppet renamed to sysutils/puppet38 >> MOVED: textproc/rubygem-augeas renamed to textproc/rubygem-ruby-augeas >> Computing deps for converters/libiconv >> Computing deps for archivers/unzip >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-Encode >> Computing deps for converters/p5-Convert-BinHex >> Computing deps for converters/p5-Encode-Locale >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-JSON-PP >> Computing deps for converters/p5-JSON >> Computing deps for converters/p5-JSON-XS >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-Text-Iconv >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/ip4r >> Computing deps for databases/gdbm >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/p5-Bucardo >> Error: Invalid port origin '/usr/local/bin/ccache' not found. Terminated Terminated Terminated Terminated >> Cleaning up >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/p5-DBD-Pg >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/memcached >> Error: Invalid port origin '/usr/local/bin/automake-1.15' not found. >> Umounting file systems Checked updating but don't see anything to suggest that port origins of '/usr/local/bin/ccache' are normal.. It looks like you're building with Poudriere. I am. I observed similar behavior, but not the exact message the other day. I don't remember what origin it was complaining about, but located a post (either on a mailing list or forums) recommending a `pkg install poudriere`. That wouldn't actually help as pourdiere is already installed on the host and I see no relevant reason why it would be correct to put it inside the reference jail. It did resolve the problem in this particular scenario. Regards, -- Michelle Sullivan http://www.mhix.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: Ports tree gone unstable?
Don Lewis wrote:
On 27 Apr, Rick Miller wrote:
On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
wrote:
Kevin Oberman wrote:
On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
wrote:
After a portsnap update it seems all my jails won't build the current tree
returning the following error:
>> MOVED: sysutils/puppet renamed to sysutils/puppet38
>> MOVED: textproc/rubygem-augeas renamed to
textproc/rubygem-ruby-augeas
>> Computing deps for converters/libiconv
>> Computing deps for archivers/unzip
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-Encode
>> Computing deps for converters/p5-Convert-BinHex
>> Computing deps for converters/p5-Encode-Locale
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-JSON-PP
>> Computing deps for converters/p5-JSON
>> Computing deps for converters/p5-JSON-XS
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-Text-Iconv
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/ip4r
>> Computing deps for databases/gdbm
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/p5-Bucardo
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
Terminated
Terminated
Terminated
Terminated
>> Cleaning up
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/p5-DBD-Pg
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/memcached
>> Error: Invalid port origin '/usr/local/bin/automake-1.15' not
found.
>> Umounting file systems
Checked updating but don't see anything to suggest that port origins of
'/usr/local/bin/ccache' are normal..
It looks like you're building with Poudriere. I observed similar behavior,
but not the exact message the other day. I don't remember what origin it
was complaining about, but located a post (either on a mailing list or
forums) recommending a `pkg install poudriere`. It did resolve the problem
in this particular scenario.
This is probably caused by the recent change to globally drop
${PORTSDIR} from *_DEPENDS. The framework changes initially were done
in bsd.port.mk r399278, but the the actual removal of ${PORTSDIR} didn't
happen until r411970, r412342, ...
Ok that sorta makes a bit more sense... however as this is a jail and
the tree is updated why did it break? (I have no local mods in the 'ng'
build tree - except an additional (local only) couple of ports which are
copied in manually after the portsnap update)...
Of course the nice thing is my non-ng tree is still working 100% - but
that would be because it didn't get the change... but again that's a
completely separate tree and the 2 are not associated with each other in
any way...
Regards,
--
Michelle Sullivan
http://www.mhix.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: Ports tree gone unstable?
On 27 Apr, Michelle Sullivan wrote: > Rick Miller wrote: >> On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan >> wrote: >> >>> Kevin Oberman wrote: >>> On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan wrote: After a portsnap update it seems all my jails won't build the current tree > returning the following error: > > >> MOVED: sysutils/puppet renamed to sysutils/puppet38 > >> MOVED: textproc/rubygem-augeas renamed to > textproc/rubygem-ruby-augeas > > >> Computing deps for converters/libiconv > >> Computing deps for archivers/unzip > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > > >> Computing deps for converters/p5-Encode > >> Computing deps for converters/p5-Convert-BinHex > >> Computing deps for converters/p5-Encode-Locale > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for converters/p5-JSON-PP > >> Computing deps for converters/p5-JSON > >> Computing deps for converters/p5-JSON-XS > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > > >> Computing deps for converters/p5-Text-Iconv > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/ip4r > >> Computing deps for databases/gdbm > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/p5-Bucardo > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > > Terminated > Terminated > Terminated > Terminated > >> Cleaning up > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/p5-DBD-Pg > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/memcached > >> Error: Invalid port origin '/usr/local/bin/automake-1.15' not > found. > >> Umounting file systems > > Checked updating but don't see anything to suggest that port origins of > '/usr/local/bin/ccache' are normal.. >> It looks like you're building with Poudriere. > > I am. > >> I observed similar behavior, >> but not the exact message the other day. I don't remember what origin it >> was complaining about, but located a post (either on a mailing list or >> forums) recommending a `pkg install poudriere`. > > That wouldn't actually help as pourdiere is already installed on the > host and I see no relevant reason why it would be correct to put it > inside the reference jail. Is the version on the host reasonably up to date? ___ 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 tree gone unstable?
Don Lewis wrote: On 27 Apr, Michelle Sullivan wrote: Rick Miller wrote: On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan wrote: Kevin Oberman wrote: On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan wrote: After a portsnap update it seems all my jails won't build the current tree returning the following error: >> MOVED: sysutils/puppet renamed to sysutils/puppet38 >> MOVED: textproc/rubygem-augeas renamed to textproc/rubygem-ruby-augeas >> Computing deps for converters/libiconv >> Computing deps for archivers/unzip >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-Encode >> Computing deps for converters/p5-Convert-BinHex >> Computing deps for converters/p5-Encode-Locale >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-JSON-PP >> Computing deps for converters/p5-JSON >> Computing deps for converters/p5-JSON-XS >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-Text-Iconv >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/ip4r >> Computing deps for databases/gdbm >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/p5-Bucardo >> Error: Invalid port origin '/usr/local/bin/ccache' not found. Terminated Terminated Terminated Terminated >> Cleaning up >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/p5-DBD-Pg >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/memcached >> Error: Invalid port origin '/usr/local/bin/automake-1.15' not found. >> Umounting file systems Checked updating but don't see anything to suggest that port origins of '/usr/local/bin/ccache' are normal.. It looks like you're building with Poudriere. I am. I observed similar behavior, but not the exact message the other day. I don't remember what origin it was complaining about, but located a post (either on a mailing list or forums) recommending a `pkg install poudriere`. That wouldn't actually help as pourdiere is already installed on the host and I see no relevant reason why it would be correct to put it inside the reference jail. Is the version on the host reasonably up to date? No/doubt it... Should there even be one on the host? -- Michelle Sullivan http://www.mhix.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: Ports tree gone unstable?
On 27 Apr, Michelle Sullivan wrote:
> Don Lewis wrote:
>> On 27 Apr, Rick Miller wrote:
>>> On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
>>> wrote:
>>>
Kevin Oberman wrote:
> On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
> wrote:
>
> After a portsnap update it seems all my jails won't build the current tree
>> returning the following error:
>>
>> >> MOVED: sysutils/puppet renamed to sysutils/puppet38
>> >> MOVED: textproc/rubygem-augeas renamed to
>> textproc/rubygem-ruby-augeas
>>
>> >> Computing deps for converters/libiconv
>> >> Computing deps for archivers/unzip
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>>
>> >> Computing deps for converters/p5-Encode
>> >> Computing deps for converters/p5-Convert-BinHex
>> >> Computing deps for converters/p5-Encode-Locale
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Computing deps for converters/p5-JSON-PP
>> >> Computing deps for converters/p5-JSON
>> >> Computing deps for converters/p5-JSON-XS
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>>
>> >> Computing deps for converters/p5-Text-Iconv
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Computing deps for databases/ip4r
>> >> Computing deps for databases/gdbm
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Computing deps for databases/p5-Bucardo
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>>
>> Terminated
>> Terminated
>> Terminated
>> Terminated
>> >> Cleaning up
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Computing deps for databases/p5-DBD-Pg
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Computing deps for databases/memcached
>> >> Error: Invalid port origin '/usr/local/bin/automake-1.15' not
>> found.
>> >> Umounting file systems
>>
>> Checked updating but don't see anything to suggest that port origins of
>> '/usr/local/bin/ccache' are normal..
>
>>> It looks like you're building with Poudriere. I observed similar behavior,
>>> but not the exact message the other day. I don't remember what origin it
>>> was complaining about, but located a post (either on a mailing list or
>>> forums) recommending a `pkg install poudriere`. It did resolve the problem
>>> in this particular scenario.
>> This is probably caused by the recent change to globally drop
>> ${PORTSDIR} from *_DEPENDS. The framework changes initially were done
>> in bsd.port.mk r399278, but the the actual removal of ${PORTSDIR} didn't
>> happen until r411970, r412342, ...
>>
> Ok that sorta makes a bit more sense... however as this is a jail and
> the tree is updated why did it break? (I have no local mods in the 'ng'
> build tree - except an additional (local only) couple of ports which are
> copied in manually after the portsnap update)...
>
> Of course the nice thing is my non-ng tree is still working 100% - but
> that would be because it didn't get the change... but again that's a
> completely separate tree and the 2 are not associated with each other in
> any way...
I was assuming that this was your non-ng tree where you have local
framework changes ...
Did you upgrade ports from something older than r411970 (Sun Mar 27
01:23:25 2016 UTC) to something more recent? If poudriere on your host
is seriously old, it might not cope with the framework change. It looks
like you need at least 3.1.9, which was released on Wed Oct 14 21:06:00
2015 UTC.
___
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 tree gone unstable?
On 27 Apr, Michelle Sullivan wrote: > Don Lewis wrote: >> On 27 Apr, Michelle Sullivan wrote: >>> Rick Miller wrote: On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan wrote: > Kevin Oberman wrote: > >> On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan >> wrote: >> >> After a portsnap update it seems all my jails won't build the current >> tree >>> returning the following error: >>> >>> >> MOVED: sysutils/puppet renamed to sysutils/puppet38 >>> >> MOVED: textproc/rubygem-augeas renamed to >>> textproc/rubygem-ruby-augeas >>> >>> >> Computing deps for converters/libiconv >>> >> Computing deps for archivers/unzip >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >>> >> Computing deps for converters/p5-Encode >>> >> Computing deps for converters/p5-Convert-BinHex >>> >> Computing deps for converters/p5-Encode-Locale >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Computing deps for converters/p5-JSON-PP >>> >> Computing deps for converters/p5-JSON >>> >> Computing deps for converters/p5-JSON-XS >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >>> >> Computing deps for converters/p5-Text-Iconv >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Computing deps for databases/ip4r >>> >> Computing deps for databases/gdbm >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Computing deps for databases/p5-Bucardo >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >>> Terminated >>> Terminated >>> Terminated >>> Terminated >>> >> Cleaning up >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Computing deps for databases/p5-DBD-Pg >>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >>> >> Computing deps for databases/memcached >>> >> Error: Invalid port origin '/usr/local/bin/automake-1.15' not >>> found. >>> >> Umounting file systems >>> >>> Checked updating but don't see anything to suggest that port origins of >>> '/usr/local/bin/ccache' are normal.. It looks like you're building with Poudriere. >>> I am. >>> I observed similar behavior, but not the exact message the other day. I don't remember what origin it was complaining about, but located a post (either on a mailing list or forums) recommending a `pkg install poudriere`. >>> That wouldn't actually help as pourdiere is already installed on the >>> host and I see no relevant reason why it would be correct to put it >>> inside the reference jail. >> Is the version on the host reasonably up to date? >> > > No/doubt it... Should there even be one on the host? It should be on the host (and not in the jail). ___ 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 tree gone unstable?
On Wed, Apr 27, 2016 at 1:25 PM, Michelle Sullivan wrote: > Rick Miller wrote: > >> On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan >> wrote: >> >> Kevin Oberman wrote: >>> >>> On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan wrote: After a portsnap update it seems all my jails won't build the current tree > returning the following error: > > >> MOVED: sysutils/puppet renamed to sysutils/puppet38 > >> MOVED: textproc/rubygem-augeas renamed to > textproc/rubygem-ruby-augeas > > >> Computing deps for converters/libiconv > >> Computing deps for archivers/unzip > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > > >> Computing deps for converters/p5-Encode > >> Computing deps for converters/p5-Convert-BinHex > >> Computing deps for converters/p5-Encode-Locale > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for converters/p5-JSON-PP > >> Computing deps for converters/p5-JSON > >> Computing deps for converters/p5-JSON-XS > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > > >> Computing deps for converters/p5-Text-Iconv > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/ip4r > >> Computing deps for databases/gdbm > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/p5-Bucardo > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > > Terminated > Terminated > Terminated > Terminated > >> Cleaning up > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/p5-DBD-Pg > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/memcached > >> Error: Invalid port origin '/usr/local/bin/automake-1.15' not > found. > >> Umounting file systems > > Checked updating but don't see anything to suggest that port origins of > '/usr/local/bin/ccache' are normal.. > It looks like you're building with Poudriere. >> > > I am. > > I observed similar behavior, >> but not the exact message the other day. I don't remember what origin it >> was complaining about, but located a post (either on a mailing list or >> forums) recommending a `pkg install poudriere`. >> > > That wouldn't actually help as pourdiere is already installed on the host > and I see no relevant reason why it would be correct to put it inside the > reference jail. I thought the same. The system was running Poudriere already, but after executing this on a private repo, it no longer failed. Admittedly, I moved on and didn't dig into it any deeper so I can't draw any correlation between your scenario and mine to determine if they are indeed related. Blech...unable to locate the post I referenced either. Sorry. -- Take care Rick Miller ___ 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 tree gone unstable?
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
On 27 Apr, Rick Miller wrote:
On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
wrote:
Kevin Oberman wrote:
On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
wrote:
After a portsnap update it seems all my jails won't build the current tree
returning the following error:
>> MOVED: sysutils/puppet renamed to sysutils/puppet38
>> MOVED: textproc/rubygem-augeas renamed to
textproc/rubygem-ruby-augeas
>> Computing deps for converters/libiconv
>> Computing deps for archivers/unzip
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-Encode
>> Computing deps for converters/p5-Convert-BinHex
>> Computing deps for converters/p5-Encode-Locale
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-JSON-PP
>> Computing deps for converters/p5-JSON
>> Computing deps for converters/p5-JSON-XS
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-Text-Iconv
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/ip4r
>> Computing deps for databases/gdbm
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/p5-Bucardo
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
Terminated
Terminated
Terminated
Terminated
>> Cleaning up
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/p5-DBD-Pg
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/memcached
>> Error: Invalid port origin '/usr/local/bin/automake-1.15' not
found.
>> Umounting file systems
Checked updating but don't see anything to suggest that port origins of
'/usr/local/bin/ccache' are normal..
It looks like you're building with Poudriere. I observed similar behavior,
but not the exact message the other day. I don't remember what origin it
was complaining about, but located a post (either on a mailing list or
forums) recommending a `pkg install poudriere`. It did resolve the problem
in this particular scenario.
This is probably caused by the recent change to globally drop
${PORTSDIR} from *_DEPENDS. The framework changes initially were done
in bsd.port.mk r399278, but the the actual removal of ${PORTSDIR} didn't
happen until r411970, r412342, ...
Ok that sorta makes a bit more sense... however as this is a jail and
the tree is updated why did it break? (I have no local mods in the 'ng'
build tree - except an additional (local only) couple of ports which are
copied in manually after the portsnap update)...
Of course the nice thing is my non-ng tree is still working 100% - but
that would be because it didn't get the change... but again that's a
completely separate tree and the 2 are not associated with each other in
any way...
I was assuming that this was your non-ng tree where you have local
framework changes ...
No, completely separate repo as the new trees are constantly breaking my
tree so I keep them entirely separate.
Did you upgrade ports from something older than r411970 (Sun Mar 27
01:23:25 2016 UTC)
It would have been around march I did the last build so yes probably
prior to Mar 27.
to something more recent?
To the latest.
If poudriere on your host
is seriously old, it might not cope with the framework change. It looks
like you need at least 3.1.9, which was released on Wed Oct 14 21:06:00
2015 UTC.
Yeah, 3.1.x changes the base OS without authority and breaks the entire
build system (can't build anything but the official tree in it) so it's
been deemed a security issue (because it "upgrades" the existing
repositories) and therefore cannot be installed or used on any of the
existing build servers.
Question is why would it be needed? Surely the tree is the tree in the
jail and has nothing to do with the host? or is it not a case of
everything is done in the jail, just the actual building is and
therefore I need new build servers for the NG tree.. Which basically
means I should just decide to fork or erase the whole system because I
can't "NG" right now and I can't actually continue to build in parallel
because of this breakage?
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-
Re: Ports tree gone unstable?
Don Lewis wrote: On 27 Apr, Michelle Sullivan wrote: Don Lewis wrote: On 27 Apr, Michelle Sullivan wrote: Rick Miller wrote: On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan wrote: Kevin Oberman wrote: On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan wrote: After a portsnap update it seems all my jails won't build the current tree returning the following error: >> MOVED: sysutils/puppet renamed to sysutils/puppet38 >> MOVED: textproc/rubygem-augeas renamed to textproc/rubygem-ruby-augeas >> Computing deps for converters/libiconv >> Computing deps for archivers/unzip >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-Encode >> Computing deps for converters/p5-Convert-BinHex >> Computing deps for converters/p5-Encode-Locale >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-JSON-PP >> Computing deps for converters/p5-JSON >> Computing deps for converters/p5-JSON-XS >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for converters/p5-Text-Iconv >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/ip4r >> Computing deps for databases/gdbm >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/p5-Bucardo >> Error: Invalid port origin '/usr/local/bin/ccache' not found. Terminated Terminated Terminated Terminated >> Cleaning up >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/p5-DBD-Pg >> Error: Invalid port origin '/usr/local/bin/ccache' not found. >> Computing deps for databases/memcached >> Error: Invalid port origin '/usr/local/bin/automake-1.15' not found. >> Umounting file systems Checked updating but don't see anything to suggest that port origins of '/usr/local/bin/ccache' are normal.. It looks like you're building with Poudriere. I am. I observed similar behavior, but not the exact message the other day. I don't remember what origin it was complaining about, but located a post (either on a mailing list or forums) recommending a `pkg install poudriere`. That wouldn't actually help as pourdiere is already installed on the host and I see no relevant reason why it would be correct to put it inside the reference jail. Is the version on the host reasonably up to date? No/doubt it... Should there even be one on the host? It should be on the host (and not in the jail). But then what's the point of multiple ports trees in pourdiere? If it relies on the host ports tree then it seems there is no point in the ability to have multiple ports trees...? Regards, -- Michelle Sullivan http://www.mhix.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: Ports tree gone unstable?
On 27 Apr, Michelle Sullivan wrote:
> Don Lewis wrote:
>> On 27 Apr, Michelle Sullivan wrote:
>>> Don Lewis wrote:
On 27 Apr, Rick Miller wrote:
> On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
> wrote:
>
>> Kevin Oberman wrote:
>>
>>> On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
>>> wrote:
>>>
>>> After a portsnap update it seems all my jails won't build the current
>>> tree
returning the following error:
>> MOVED: sysutils/puppet renamed to sysutils/puppet38
>> MOVED: textproc/rubygem-augeas renamed to
textproc/rubygem-ruby-augeas
>> Computing deps for converters/libiconv
>> Computing deps for archivers/unzip
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-Encode
>> Computing deps for converters/p5-Convert-BinHex
>> Computing deps for converters/p5-Encode-Locale
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-JSON-PP
>> Computing deps for converters/p5-JSON
>> Computing deps for converters/p5-JSON-XS
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-Text-Iconv
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/ip4r
>> Computing deps for databases/gdbm
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/p5-Bucardo
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
Terminated
Terminated
Terminated
Terminated
>> Cleaning up
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/p5-DBD-Pg
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/memcached
>> Error: Invalid port origin '/usr/local/bin/automake-1.15' not
found.
>> Umounting file systems
Checked updating but don't see anything to suggest that port origins of
'/usr/local/bin/ccache' are normal..
> It looks like you're building with Poudriere. I observed similar
> behavior,
> but not the exact message the other day. I don't remember what origin it
> was complaining about, but located a post (either on a mailing list or
> forums) recommending a `pkg install poudriere`. It did resolve the
> problem
> in this particular scenario.
This is probably caused by the recent change to globally drop
${PORTSDIR} from *_DEPENDS. The framework changes initially were done
in bsd.port.mk r399278, but the the actual removal of ${PORTSDIR} didn't
happen until r411970, r412342, ...
>>> Ok that sorta makes a bit more sense... however as this is a jail and
>>> the tree is updated why did it break? (I have no local mods in the 'ng'
>>> build tree - except an additional (local only) couple of ports which are
>>> copied in manually after the portsnap update)...
>>>
>>> Of course the nice thing is my non-ng tree is still working 100% - but
>>> that would be because it didn't get the change... but again that's a
>>> completely separate tree and the 2 are not associated with each other in
>>> any way...
>> I was assuming that this was your non-ng tree where you have local
>> framework changes ...
>
> No, completely separate repo as the new trees are constantly breaking my
> tree so I keep them entirely separate.
>>
>> Did you upgrade ports from something older than r411970 (Sun Mar 27
>> 01:23:25 2016 UTC)
>
> It would have been around march I did the last build so yes probably
> prior to Mar 27.
>
>> to something more recent?
> To the latest.
>> If poudriere on your host
>> is seriously old, it might not cope with the framework change. It looks
>> like you need at least 3.1.9, which was released on Wed Oct 14 21:06:00
>> 2015 UTC.
> Yeah, 3.1.x changes the base OS without authority and breaks the entire
> build system (can't build anything but the official tree in it) so it's
> been deemed a security issue (because it "upgrades" the existing
> repositories) and therefore cannot be installed or used on any of the
> existing build servers.
Sorry, t
Re: Ports tree gone unstable?
On 27 Apr, Michelle Sullivan wrote: > Don Lewis wrote: >> On 27 Apr, Michelle Sullivan wrote: >>> Don Lewis wrote: On 27 Apr, Michelle Sullivan wrote: > Rick Miller wrote: >> On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan >> wrote: >> >>> Kevin Oberman wrote: >>> On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan wrote: After a portsnap update it seems all my jails won't build the current tree > returning the following error: > > >> MOVED: sysutils/puppet renamed to sysutils/puppet38 > >> MOVED: textproc/rubygem-augeas renamed to > textproc/rubygem-ruby-augeas > > >> Computing deps for converters/libiconv > >> Computing deps for archivers/unzip > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > > >> Computing deps for converters/p5-Encode > >> Computing deps for converters/p5-Convert-BinHex > >> Computing deps for converters/p5-Encode-Locale > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for converters/p5-JSON-PP > >> Computing deps for converters/p5-JSON > >> Computing deps for converters/p5-JSON-XS > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > > >> Computing deps for converters/p5-Text-Iconv > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/ip4r > >> Computing deps for databases/gdbm > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/p5-Bucardo > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > > Terminated > Terminated > Terminated > Terminated > >> Cleaning up > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/p5-DBD-Pg > >> Error: Invalid port origin '/usr/local/bin/ccache' not found. > >> Computing deps for databases/memcached > >> Error: Invalid port origin '/usr/local/bin/automake-1.15' not > found. > >> Umounting file systems > > Checked updating but don't see anything to suggest that port origins > of > '/usr/local/bin/ccache' are normal.. >> It looks like you're building with Poudriere. > I am. > >> I observed similar behavior, >> but not the exact message the other day. I don't remember what origin it >> was complaining about, but located a post (either on a mailing list or >> forums) recommending a `pkg install poudriere`. > That wouldn't actually help as pourdiere is already installed on the > host and I see no relevant reason why it would be correct to put it > inside the reference jail. Is the version on the host reasonably up to date? >>> No/doubt it... Should there even be one on the host? >> It should be on the host (and not in the jail). >> > But then what's the point of multiple ports trees in pourdiere? If it > relies on the host ports tree then it seems there is no point in the > ability to have multiple ports trees...? Poudriere doesn't use the host ports tree unless you explicitly tell it to. The version of poudriere installed on the host just needs to be new enough to cope with the ports tree that you are trying to use for building the package set. It's basically just a big shell script that has to be able to parse the output of "make -V BUILD_DEPENDS", etc. (and a bunch of other stuff). ___ 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 tree gone unstable?
On 4/27/2016 8:06 AM, Michelle Sullivan wrote:
> After a portsnap update it seems all my jails won't build the current
> tree returning the following error:
>
> >> MOVED: sysutils/puppet renamed to sysutils/puppet38
> >> MOVED: textproc/rubygem-augeas renamed to
> textproc/rubygem-ruby-augeas
>
> >> Computing deps for converters/libiconv
> >> Computing deps for archivers/unzip
> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
Your poudriere is too old. This is due to the removal of ${PORTSDIR} in
dependencies. We put that off for several months (I think 6+) after the
Poudriere fix came out for it.
--
Regards,
Bryan Drewery
signature.asc
Description: OpenPGP digital signature
Re: Ports tree gone unstable?
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
On 27 Apr, Rick Miller wrote:
On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
wrote:
Kevin Oberman wrote:
On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
wrote:
After a portsnap update it seems all my jails won't build the current tree
returning the following error:
>> MOVED: sysutils/puppet renamed to sysutils/puppet38
>> MOVED: textproc/rubygem-augeas renamed to
textproc/rubygem-ruby-augeas
>> Computing deps for converters/libiconv
>> Computing deps for archivers/unzip
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-Encode
>> Computing deps for converters/p5-Convert-BinHex
>> Computing deps for converters/p5-Encode-Locale
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-JSON-PP
>> Computing deps for converters/p5-JSON
>> Computing deps for converters/p5-JSON-XS
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-Text-Iconv
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/ip4r
>> Computing deps for databases/gdbm
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/p5-Bucardo
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
Terminated
Terminated
Terminated
Terminated
>> Cleaning up
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/p5-DBD-Pg
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/memcached
>> Error: Invalid port origin '/usr/local/bin/automake-1.15' not
found.
>> Umounting file systems
Checked updating but don't see anything to suggest that port origins of
'/usr/local/bin/ccache' are normal..
It looks like you're building with Poudriere. I observed similar behavior,
but not the exact message the other day. I don't remember what origin it
was complaining about, but located a post (either on a mailing list or
forums) recommending a `pkg install poudriere`. It did resolve the problem
in this particular scenario.
This is probably caused by the recent change to globally drop
${PORTSDIR} from *_DEPENDS. The framework changes initially were done
in bsd.port.mk r399278, but the the actual removal of ${PORTSDIR} didn't
happen until r411970, r412342, ...
Ok that sorta makes a bit more sense... however as this is a jail and
the tree is updated why did it break? (I have no local mods in the 'ng'
build tree - except an additional (local only) couple of ports which are
copied in manually after the portsnap update)...
Of course the nice thing is my non-ng tree is still working 100% - but
that would be because it didn't get the change... but again that's a
completely separate tree and the 2 are not associated with each other in
any way...
I was assuming that this was your non-ng tree where you have local
framework changes ...
No, completely separate repo as the new trees are constantly breaking my
tree so I keep them entirely separate.
Did you upgrade ports from something older than r411970 (Sun Mar 27
01:23:25 2016 UTC)
It would have been around march I did the last build so yes probably
prior to Mar 27.
to something more recent?
To the latest.
If poudriere on your host
is seriously old, it might not cope with the framework change. It looks
like you need at least 3.1.9, which was released on Wed Oct 14 21:06:00
2015 UTC.
Yeah, 3.1.x changes the base OS without authority and breaks the entire
build system (can't build anything but the official tree in it) so it's
been deemed a security issue (because it "upgrades" the existing
repositories) and therefore cannot be installed or used on any of the
existing build servers.
Sorry, this is all from memory ... my poudriere machine will be offline
for several more hours so I can't use it as a reference.
Poudriere shouldn't be changing anything in the base OS. It probably
creates some temp files under /tmp and puts the package repositories
that I builds and the log files under its own directories under
/var/tmp.
Unfortunately the first thing that 3.1.[012]? did was install all the
pkg stuff and change the pkg_add repo into a pkg repo... or something
like it, which broke everything horribly.. it was a long time ago so no
idea the specifics now... but it (3.1.x) was put on a 'not suitable for
us
Re: Ports tree gone unstable?
On 27 Apr, Michelle Sullivan wrote:
> Don Lewis wrote:
>> On 27 Apr, Michelle Sullivan wrote:
>>> Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
> Don Lewis wrote:
>> On 27 Apr, Rick Miller wrote:
>>> On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
>>> wrote:
>>>
Kevin Oberman wrote:
> On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
>
> wrote:
>
> After a portsnap update it seems all my jails won't build the current
> tree
>> returning the following error:
>>
>> >> MOVED: sysutils/puppet renamed to sysutils/puppet38
>> >> MOVED: textproc/rubygem-augeas renamed to
>> textproc/rubygem-ruby-augeas
>>
>> >> Computing deps for converters/libiconv
>> >> Computing deps for archivers/unzip
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>>
>> >> Computing deps for converters/p5-Encode
>> >> Computing deps for converters/p5-Convert-BinHex
>> >> Computing deps for converters/p5-Encode-Locale
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Computing deps for converters/p5-JSON-PP
>> >> Computing deps for converters/p5-JSON
>> >> Computing deps for converters/p5-JSON-XS
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>>
>> >> Computing deps for converters/p5-Text-Iconv
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Computing deps for databases/ip4r
>> >> Computing deps for databases/gdbm
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Computing deps for databases/p5-Bucardo
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>>
>> Terminated
>> Terminated
>> Terminated
>> Terminated
>> >> Cleaning up
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Computing deps for databases/p5-DBD-Pg
>> >> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> >> Computing deps for databases/memcached
>> >> Error: Invalid port origin '/usr/local/bin/automake-1.15' not
>> found.
>> >> Umounting file systems
>>
>> Checked updating but don't see anything to suggest that port origins
>> of
>> '/usr/local/bin/ccache' are normal..
>>> It looks like you're building with Poudriere. I observed similar
>>> behavior,
>>> but not the exact message the other day. I don't remember what origin
>>> it
>>> was complaining about, but located a post (either on a mailing list or
>>> forums) recommending a `pkg install poudriere`. It did resolve the
>>> problem
>>> in this particular scenario.
>> This is probably caused by the recent change to globally drop
>> ${PORTSDIR} from *_DEPENDS. The framework changes initially were done
>> in bsd.port.mk r399278, but the the actual removal of ${PORTSDIR} didn't
>> happen until r411970, r412342, ...
>>
> Ok that sorta makes a bit more sense... however as this is a jail and
> the tree is updated why did it break? (I have no local mods in the 'ng'
> build tree - except an additional (local only) couple of ports which are
> copied in manually after the portsnap update)...
>
> Of course the nice thing is my non-ng tree is still working 100% - but
> that would be because it didn't get the change... but again that's a
> completely separate tree and the 2 are not associated with each other in
> any way...
I was assuming that this was your non-ng tree where you have local
framework changes ...
>>> No, completely separate repo as the new trees are constantly breaking my
>>> tree so I keep them entirely separate.
Did you upgrade ports from something older than r411970 (Sun Mar 27
01:23:25 2016 UTC)
>>> It would have been around march I did the last build so yes probably
>>> prior to Mar 27.
>>>
to something more recent?
>>> To the latest.
If poudriere on your host
is seriously old, it might not cope with the framework change. It looks
like you need at least 3.1.9, which was released on Wed Oct 14 21:06:00
2015 UTC.
>>> Yeah, 3.1.x changes the base OS without authorit
Re: Ports tree gone unstable?
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
On 27 Apr, Rick Miller wrote:
On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
wrote:
Kevin Oberman wrote:
On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
wrote:
After a portsnap update it seems all my jails won't build the current tree
returning the following error:
>> MOVED: sysutils/puppet renamed to sysutils/puppet38
>> MOVED: textproc/rubygem-augeas renamed to
textproc/rubygem-ruby-augeas
>> Computing deps for converters/libiconv
>> Computing deps for archivers/unzip
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-Encode
>> Computing deps for converters/p5-Convert-BinHex
>> Computing deps for converters/p5-Encode-Locale
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-JSON-PP
>> Computing deps for converters/p5-JSON
>> Computing deps for converters/p5-JSON-XS
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for converters/p5-Text-Iconv
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/ip4r
>> Computing deps for databases/gdbm
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/p5-Bucardo
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
Terminated
Terminated
Terminated
Terminated
>> Cleaning up
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/p5-DBD-Pg
>> Error: Invalid port origin '/usr/local/bin/ccache' not found.
>> Computing deps for databases/memcached
>> Error: Invalid port origin '/usr/local/bin/automake-1.15' not
found.
>> Umounting file systems
Checked updating but don't see anything to suggest that port origins of
'/usr/local/bin/ccache' are normal..
It looks like you're building with Poudriere. I observed similar behavior,
but not the exact message the other day. I don't remember what origin it
was complaining about, but located a post (either on a mailing list or
forums) recommending a `pkg install poudriere`. It did resolve the problem
in this particular scenario.
This is probably caused by the recent change to globally drop
${PORTSDIR} from *_DEPENDS. The framework changes initially were done
in bsd.port.mk r399278, but the the actual removal of ${PORTSDIR} didn't
happen until r411970, r412342, ...
Ok that sorta makes a bit more sense... however as this is a jail and
the tree is updated why did it break? (I have no local mods in the 'ng'
build tree - except an additional (local only) couple of ports which are
copied in manually after the portsnap update)...
Of course the nice thing is my non-ng tree is still working 100% - but
that would be because it didn't get the change... but again that's a
completely separate tree and the 2 are not associated with each other in
any way...
I was assuming that this was your non-ng tree where you have local
framework changes ...
No, completely separate repo as the new trees are constantly breaking my
tree so I keep them entirely separate.
Did you upgrade ports from something older than r411970 (Sun Mar 27
01:23:25 2016 UTC)
It would have been around march I did the last build so yes probably
prior to Mar 27.
to something more recent?
To the latest.
If poudriere on your host
is seriously old, it might not cope with the framework change. It looks
like you need at least 3.1.9, which was released on Wed Oct 14 21:06:00
2015 UTC.
Yeah, 3.1.x changes the base OS without authority and breaks the entire
build system (can't build anything but the official tree in it) so it's
been deemed a security issue (because it "upgrades" the existing
repositories) and therefore cannot be installed or used on any of the
existing build servers.
Sorry, this is all from memory ... my poudriere machine will be offline
for several more hours so I can't use it as a reference.
Poudriere shouldn't be changing anything in the base OS. It probably
creates some temp files under /tmp and puts the package repositories
that I builds and the log files under its own directories under
/var/tmp.
Unfortunately the first thing that 3.1.[012]? did was install all the
pkg stuff and change the pkg_add repo into a pkg repo... or something
like it, which broke everything horribly.. it was a long time ago so no
idea the specifics now
[no subject]
Sent from my Verizon 4G LTE Droid ___ 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 tree gone unstable?
On 28 Apr, Michelle Sullivan wrote:
> Don Lewis wrote:
>> On 27 Apr, Michelle Sullivan wrote:
>>> Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
> Don Lewis wrote:
>> On 27 Apr, Michelle Sullivan wrote:
>>> Don Lewis wrote:
On 27 Apr, Rick Miller wrote:
> On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
>
> wrote:
>
>> Kevin Oberman wrote:
>>
>>> On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
>>>
>>> wrote:
>>>
>>> After a portsnap update it seems all my jails won't build the
>>> current tree
returning the following error:
>> MOVED: sysutils/puppet renamed to sysutils/puppet38
>> MOVED: textproc/rubygem-augeas renamed to
textproc/rubygem-ruby-augeas
>> Computing deps for converters/libiconv
>> Computing deps for archivers/unzip
>> Error: Invalid port origin '/usr/local/bin/ccache' not
found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not
found.
>> Computing deps for converters/p5-Encode
>> Computing deps for converters/p5-Convert-BinHex
>> Computing deps for converters/p5-Encode-Locale
>> Error: Invalid port origin '/usr/local/bin/ccache' not
found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not
found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not
found.
>> Computing deps for converters/p5-JSON-PP
>> Computing deps for converters/p5-JSON
>> Computing deps for converters/p5-JSON-XS
>> Error: Invalid port origin '/usr/local/bin/ccache' not
found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not
found.
>> Error: Invalid port origin '/usr/local/bin/ccache' not
found.
>> Computing deps for converters/p5-Text-Iconv
>> Error: Invalid port origin '/usr/local/bin/ccache' not
found.
>> Computing deps for databases/ip4r
>> Computing deps for databases/gdbm
>> Error: Invalid port origin '/usr/local/bin/ccache' not
found.
>> Computing deps for databases/p5-Bucardo
>> Error: Invalid port origin '/usr/local/bin/ccache' not
found.
Terminated
Terminated
Terminated
Terminated
>> Cleaning up
>> Error: Invalid port origin '/usr/local/bin/ccache' not
found.
>> Computing deps for databases/p5-DBD-Pg
>> Error: Invalid port origin '/usr/local/bin/ccache' not
found.
>> Computing deps for databases/memcached
>> Error: Invalid port origin '/usr/local/bin/automake-1.15'
not
found.
>> Umounting file systems
Checked updating but don't see anything to suggest that port
origins of
'/usr/local/bin/ccache' are normal..
> It looks like you're building with Poudriere. I observed similar
> behavior,
> but not the exact message the other day. I don't remember what
> origin it
> was complaining about, but located a post (either on a mailing list or
> forums) recommending a `pkg install poudriere`. It did resolve the
> problem
> in this particular scenario.
This is probably caused by the recent change to globally drop
${PORTSDIR} from *_DEPENDS. The framework changes initially were done
in bsd.port.mk r399278, but the the actual removal of ${PORTSDIR}
didn't
happen until r411970, r412342, ...
>>> Ok that sorta makes a bit more sense... however as this is a jail and
>>> the tree is updated why did it break? (I have no local mods in the 'ng'
>>> build tree - except an additional (local only) couple of ports which are
>>> copied in manually after the portsnap update)...
>>>
>>> Of course the nice thing is my non-ng tree is still working 100% - but
>>> that would be because it didn't get the change... but again that's a
>>> completely separate tree and the 2 are not associated with each other in
>>> any way...
>> I was assuming that this was your non-ng tree where you have local
>> framework changes ...
> No, completely separate repo as the new trees are constantly breaking my
> tree so I keep them entirely separate.
>> Did you upgrade ports from something old
Reviving deleted port
This relates to ftp/rexx-curl. This was deleted after failing to build with the latest version of curl. I didn't notice for a while (I was going through a period when I couldn't update my ports tree). It is no longer in the ports tree at all. The problem turned out to be just an uninitialised variable! I have made some other fixes related to the new curl. QUESTION: Do I submit this as a 'new' port? Or is there some mechanism for a deleted port? (I am willing to take over maintainership) -- Bob ___ 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: Reviving deleted port
Hi! > This relates to ftp/rexx-curl. > > This was deleted after failing to build with the latest version of > curl. I didn't notice for a while (I was going through a period when I > couldn't update my ports tree). It is no longer in the ports tree at > all. > > The problem turned out to be just an uninitialised variable! I have > made some other fixes related to the new curl. Very nice! > QUESTION: Do I submit this as a 'new' port? Or is there some mechanism > for a deleted port? Please submit it and mention to revive the old port with some changes. > (I am willing to take over maintainership) That's necessary for 'new' or 'revived' ports. -- p...@opsec.eu+49 171 3101372 4 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: Ports tree gone unstable?
On 28 Apr, Michelle Sullivan wrote: > Don Lewis wrote: >> I'd thought that poudriere was using the host copy of pkg to do the >> final part of the respository build, but since poudriere doesn't list >> pkg as a dependency, that appears not to be the case. It looks like >> poudriere is running pkg (from the repository being constructed) in the >> jail for that. > > Yeah.. except something around the time went about "upgrading" the OS to > use pkg as well... which screwed the OS... fortunately I caught the > first VM it tried to do it to and was able to limit the damage just to > that VM so the rebuild was minimum. How were you upgrading ports when this happened. I ask because the old pkg_* tools didn't have the equivalent of "pkg upgrade". I'm guessing that you probably used "portupgrade -P" or "portmaster -P" as a wrapper around the pkg_* tools, and I think that requires a copy of the ports tree on the client machines even though binary packages are being used. If that's the situation, I think what probably happened is that when up updated to a version of the ports tree after support for old-style packages was turned off, poudriere rebuilt the repository with new-style packages. Then when you ran portupgrade or portmaster on the client with the same version of the ports tree, the framework then told portmaster/portupgrade to not look for WITH_PKGNG=yes in /etc/make.conf and just to go ahead and use pkg to upgrade the packages. Since the database of installed packages hadn't been upgraded with pkg2ng, chaos ensued. At the time of this transition, I was still using portupgrade to build everything from source. Before I switched to pkgNG, I was having problems with database corruption because the old package tools didn't really handle running out of disk space during an upgrade. I only upgraded packages infrequently because the process was so painful. It would take two or three days to do an upgrade on my desktop and I'd have to monitor it around the clock. If portupgrade ran into an error or stopped to ask a question just after I went to sleep, then I'd lose many hours of potential build time. Because of the infrequent upgrades I would have to deal with all of the intervening special cases in UPDATING that accumulated between upgrades, and the portupgrade -fr and -a options didn't interoperate well, so I ended up having to build some ports multiple times. If things crashed, then I'd have to run portupgrade -rf again, rebuilding a lot of things unnecessarily since there was no way of doing a restart. A classic cause of that would happen if portupgrade decided to rebuild gdm, in which case it would stop gdm before removing the the old version and restart it after installing the new version. Unfortunately, stopping gdm would kill Xorg and thus the terminal window where portupgrade was running. Eventually things got to the point that I could no longer tolerate the extended downtime of my primary desktop machine, so I started building binary packages using portupgrade -p on a faster headless machine. The builds still took a long time, but the final upgrade on my desktop using "pkg upgrade" was *much* faster. Building the packages with portupgrade was still flakey and eventually broke when the ports tree was converted to staging. At that point I bit the bullet and converted to poudriere and life was so much better. Not only did that eliminate a lot of manual intervention to build the packages, but the paralled builds sped things up a lot. Even though poudriere isn't especially efficient about deciding what needs to be rebuilt, the build times for my package set went from several days to under 12 hours, and the latter includes a number of huge ports that I never used to build. ___ 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"
