Hi, > I am incrementing version of a component in the Userland consolidation > and I am filling an RTI to get it integrated into the SRU gate. > > Since this change only increments the version of the component, > I am looking for a definite answer on what to put into the list > of binary deliverables (its the "Binary Delivery" section in the RTI).
I filled some time ago 7069662 Userland is missing tools/process to track changes in proto areas I can see the priority was lowered and I missed it. I'm changing the priority to 1, because it is really showstopper for sustaining. Also I'm ccing [email protected]. Guessing by bugs owned by you, is it proftpd? If yes, there is not much deliverables, so I would list all files as a temporary workaround. If you have some time to investigate, I wrote a script which can convert the pkg repository userland creates to proto area. So we can try build old and new version, create proto area from both and try to run wsdiff. But it's limited to regular files only. For example: /net/ssaesrv.us.oracle.com/export/groups/IDR/s11-idr/scripts/production/helpers/pkg2proto.pl file:///builds/vm156888/userland/i386/repo proto Please add service request to the CR. Sorry I don't have better news ... -- Vlad _______________________________________________ userland-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/userland-discuss
