signify error when installing ports on -current

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

signify error when installing ports on -current

Matthias Schmidt
Hi,

today I wanted to upgrade my local ports because of the recent libc
bump.  Turns out the ports build system cannot install packages any
longer and fails with a signify error.  I only upgrade the two ports
I use whevener there is a library version bump, so it definitely worked
at that time (IIRC it was libssl or so).

Here is the error.  I cleaned /usr/ports/packages, however, no changes.

$ cd /usr/ports/sysutils/tarsnap
$ doas make install
`/usr/ports/pobj/tarsnap-1.0.39/fake-amd64/.fake_done' is up to date.
===>  Building package for tarsnap-1.0.39
Create /usr/ports/packages/amd64/all/tarsnap-1.0.39.tgz
Creating package tarsnap-1.0.39
===>  Installing tarsnap-1.0.39 from /usr/ports/packages/amd64/all/
quirks-3.153 signed on 2019-05-17T15:16:11Z
file:/usr/ports/packages/amd64/all/tarsnap-1.0.39.tgz: unsigned package
(signify(1) doesn't see old-style signatures)
Can't find /usr/ports/packages/amd64/all/tarsnap-1.0.39.tgz
Couldn't install tarsnap-1.0.39
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2043
'/var/db/pkg/tarsnap-1.0.39/+CONTENTS': @/usr/bin/env -i
PKG_TMPDIR=/var/tmp...)
*** Error 1 in /usr/ports/sysutils/tarsnap
(/usr/ports/infrastructure/mk/bsd.port.mk:2466 'install')

Completely different port I never used before:

$ cd /usr/ports/sysutils/safecat
$ make
[...]
$ doas make install
===>  Faking installation for safecat-1.13p0
/usr/ports/pobj/safecat-1.13/bin/install -c -s -m 755
/usr/ports/pobj/safecat-1.13/safecat-1.13/safecat
/usr/ports/pobj/safecat-1.13/fake-amd64/usr/local/bin/safecat
/usr/ports/pobj/safecat-1.13/bin/install -c -m 755
/usr/ports/pobj/safecat-1.13/safecat-1.13/maildir
/usr/ports/pobj/safecat-1.13/fake-amd64/usr/local/bin/maildir
/usr/ports/pobj/safecat-1.13/bin/install -c -m 644
/usr/ports/pobj/safecat-1.13/safecat-1.13/safecat.1
/usr/ports/pobj/safecat-1.13/fake-amd64/usr/local/man/man1/
/usr/ports/pobj/safecat-1.13/bin/install -c -m 644
/usr/ports/pobj/safecat-1.13/safecat-1.13/maildir.1
/usr/ports/pobj/safecat-1.13/fake-amd64/usr/local/man/man1/
===>  Building package for safecat-1.13p0
Create /usr/ports/packages/amd64/all/safecat-1.13p0.tgz
Creating package safecat-1.13p0
Link to /usr/ports/packages/amd64/ftp/safecat-1.13p0.tgz
===>  Verifying specs: c
===>  found c.95.1
===>  Installing safecat-1.13p0 from /usr/ports/packages/amd64/all/
quirks-3.153 signed on 2019-05-17T15:16:11Z
file:/usr/ports/packages/amd64/all/safecat-1.13p0.tgz: unsigned package
(signify(1) doesn't see old-style signatures)
Can't find /usr/ports/packages/amd64/all/safecat-1.13p0.tgz
Couldn't install safecat-1.13p0
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2043
'/var/db/pkg/safecat-1.13p0/+CONTENTS': @/usr/bin/env -i
PKG_TMPDIR=/var/tmp...)
*** Error 1 in /usr/ports/sysutils/safecat
(/usr/ports/infrastructure/mk/bsd.port.mk:2466 'install')

I run -current from (GENERIC.MP) #18: Mon May 13 19:17:43 MDT 2019

Cheers

        Matthias

Reply | Threaded
Open this post in threaded view
|

Re: signify error when installing ports on -current

Marc Espie-2
On Sun, May 19, 2019 at 06:25:03PM +0200, Matthias Schmidt wrote:
> Hi,
>
> today I wanted to upgrade my local ports because of the recent libc
> bump.  Turns out the ports build system cannot install packages any
> longer and fails with a signify error.  I only upgrade the two ports
> I use whevener there is a library version bump, so it definitely worked
> at that time (IIRC it was libssl or so).

You're not passing the env variable TRUSTED_PKG_PATH through doas.

Reply | Threaded
Open this post in threaded view
|

Re: signify error when installing ports on -current

Matthias Schmidt
Hi,

* Marc Espie wrote:

> On Sun, May 19, 2019 at 06:25:03PM +0200, Matthias Schmidt wrote:
> > Hi,
> >
> > today I wanted to upgrade my local ports because of the recent libc
> > bump.  Turns out the ports build system cannot install packages any
> > longer and fails with a signify error.  I only upgrade the two ports
> > I use whevener there is a library version bump, so it definitely worked
> > at that time (IIRC it was libssl or so).
>
> You're not passing the env variable TRUSTED_PKG_PATH through doas.

Thanks a lot, that solved my problem!  Has this been changed in the last
month or why am I hitting this issue now?  I never recall fiddling
around with the variable...

Cheers

        Matthias