Tuesday, May 05, 2020

neomutt-20200501: not an update patch

I understand openbsd is near release and this is
not an attempt to send an update patch. I was facing
bug #2145 and it is fixed in the newest release. To
test it I simply changed 'GH_TAGNAME=20200501'. Build
and the fake installation was successfully and there
were no changes (aside from COPYRIGHT.md file) in the
PLIST.

'env FLAVOR=sasl make package'
(env FLAVOR=sasl was used for all intermediate commands)
gives following error

'/usr/portsdir/pobj/neomutt-20200501-sasl/fake-amd64-sasl/.fake_done' is up
to date.
===> Building package for neomutt-20200501-sasl
Create /usr/portsdir/packages/amd64/all/neomutt-20200501-sasl.tgz
Creating package neomutt-20200501-sasl
Creating package debug-neomutt-20200501-sasl
checking dependencies|mail/neomutt,sasl
Error: Dependency neomutt-20200501-sasl doesn't match FULLPKGNAME:
neomutt-20200320-sasl
checksumming...
pkg_create: can't continue
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2113
'/usr/portsdir/packages/amd64/all/neomutt-20200501-sasl.tgz': @trap "cd
/usr...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2594
'_internal-package': @case X${_DEPENDS_CACHE} in X)
_DEPENDS_CACHE=$(sudo -...)
*** Error 2 in /usr/ports/mystuff/mail/neomutt
(/usr/ports/infrastructure/mk/bsd.port.mk:2573 'package':
@lock=neomutt-20200501-sasl; expor...)
ttps://man.openbsd.org/pkg_add.1#snap

I don't understand how the ports system knows the name of the old
release? (Check FULLPKGNAME above) I never built neomutt through ports.
I checked all the files in 'mail/neomutt' there is no mention of it.
I got rid of the currently installed version 'neomutt-2020320-sasl'
(even though I didn't think it would make a difference) and tried again
same error occurs. Help me out?

No comments:

Post a Comment