On Tue, Mar 17, 2015 at 08:54:04PM +0000, Stuart Henderson wrote: > On 2015/03/17 21:07, Markus Lude wrote: > > Hello Marc, > > > > pkg_add seems to have some problem here with comparing signatures. I run > > -current on sparc64. > > > > For example I build gtar from ports after libiconv update. Strangely the > > gtar package is not updated: > > > > $ sudo pkg_add -u -D unsigned gtar > > $ sudo pkg_add -u -D unsigned -vvv gtar > > Update candidates: gtar-1.28p1 -> gtar-1.28p1 > > Comparing full signature for gtar-1.28p1 > > "gtar-1.28p1,@bzip2-1.0.6p1,@gettext-0.19.4,@libiconv-1.14p2,@xz-5.2.0,c.78.1,iconv.6.0,intl.6.0" > > vs. > > "gtar-1.28p1,@bzip2-1.0.6p1,@gettext-0.19.4,@libiconv-1.14p1,@xz-5.2.0,c.78.1,iconv.6.0,intl.6.0":equal > > No change in gtar-1.28p1 > > $ > > > > The libiconv versions here differ, but the signatures were "equal"? > > This seems misleading. > > > > Further investigation shows, that all files in both packages seems the > > same according to the @sha entries. Maybe thats why the package isn't > > updated. > > > > Maybe you could shed some light on this? > > > > Regards, > > Markus > > > > This is expected, it's the effect of -DSHORTENED. > > Date: 2015/03/09 11:09:00 > Author: espie > Branch: HEAD > Tag: (none) > Log: > make -DSHORTENED the default: don't update unless there is an actual > change in dependencies: shared library versions, and explicit version > requirements in dependencies. > as discussed with aja@ before the lock. > > Members: > OpenBSD/PkgAdd.pm:1.83->1.84 > OpenBSD/Signature.pm:1.16->1.17
Hi, somehow I missed this. Unfortunately the out-of-date script has not much use any more with this. I still use(d) it. Regards, Markus
