Date: Wed, 27 Apr 2016 20:00:23 +0200 From: Michelle Sullivan <michelle@sorbs.net> To: Don Lewis <truckman@FreeBSD.org> Cc: ports@freebsd.org, vmiller@hostileadmin.com, rkoberman@gmail.com Subject: Re: Ports tree gone unstable? Message-ID: <5720FE37.2040309@sorbs.net> In-Reply-To: <201604271742.u3RHgd6M003815@gw.catspoiler.org> References: <201604271742.u3RHgd6M003815@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <michelle@sorbs.net>
>>>> wrote:
>>>>
>>>>> Kevin Oberman wrote:
>>>>>
>>>>>> On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan <michelle@sorbs.net>
>>>>>> 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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5720FE37.2040309>