On 18/08/2012 6:25 AM, Alan Coopersmith wrote:
> On 08/17/12 10:03 AM, [email protected] wrote:
>> Alan Coopersmith <[email protected]> wrote:
>>
>>> On 08/17/12 09:25 AM, [email protected] wrote:
>>>> BTW: the IPS meta data was also in an inconstsient state but IPS silently 
>>>> ignores missing files....so the package creation did not abort. Did you 
>>>> fix 
>>>> that for Illumos?
>>> That bug does not occur for anyone but your distro, so it must be something
>>> you broke on your end.   IPS in all other distros refuses to build packages
>>> if it can't find all the files needed for the package, as otherwise it would
>>> be quite insane.
>> This is a really strange claim - given the fact that I did not change 
>> related 
>> software. It is obvious that this behavior is caused by the IPS delivered by 
>> Sun/Oracle.
> Then either I'm misunderstanding you, or you're misunderstanding some failure
> you saw - because I've had to fix or help others fix dozens of broken builds
> where developer error caused a file not to be built and IPS publication 
> aborted
> and refused to build the packages.
>
> It's easy to reproduce the case I'm claiming is what everyone else sees:
>
> % cat test-manifest.p5m
> set name=pkg.fmri [email protected]
> set name=pkg.summary value="Test of package system"
> file group=bin mode=0755 owner=root path=bin/foo
> file group=bin mode=0755 owner=root path=bin/bar
>
> % mkdir proto
> % mkdir proto/bin
> % touch proto/bin/foo
>
> % pkgrepo create repo
> % pkgrepo set -s repo publisher/prefix=test-pub
> % pkgsend -s repo publish -d proto test-manifest.p5m
> pkgsend: Action payload '/bin/bar' was not found in any of the provided 
> locations:
> proto
> % touch proto/bin/bar
> % pkgsend -s repo publish -d proto test-manifest.p5m
> pkg://test-pub/[email protected],5.11:20120817T201847Z
> PUBLISHED
>
> Though most build systems like ON will actually fail earlier than that, when
> "pkgdepend generate" can't find the files to gather dependencies from.
>

Even if both files were present, the above manifest will also fail the 
mogrify(?)
step of the build with an obscure error. The cause is simple: the 'file" 
contents
of the manifest must appear in the order in which they would appear if passed
through "sort".

I haven't filed (or searched for) a bug on that because when I looked deeper
into the python script, it became clear that the code that generated the error
actually had no idea about what actually failed, only that something had..

Darren



-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com

Reply via email to