NetBSD Problem Report #53542

From  Mon Aug 20 08:13:44 2018
Return-Path: <>
Received: from ( [])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "", Issuer " CA" (not verified))
	by (Postfix) with ESMTPS id 197EF7A14F
	for <>; Mon, 20 Aug 2018 08:13:44 +0000 (UTC)
Message-Id: <>
Date: Mon, 20 Aug 2018 10:13:40 +0200 (CEST)
Subject: pkgin misleading(?) error message
X-Send-Pr-Version: 3.95

>Number:         53542
>Category:       pkg
>Synopsis:       pkgin misleading(?) error message
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    jperkin
>State:          feedback
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 20 08:15:00 +0000 2018
>Last-Modified:  Mon Apr 20 10:43:02 +0000 2020
>Release:        NetBSD 7.1_STABLE
	I try...
Architecture: i386_
Machine: i386
	I'm doing a pkgsrc upgrade of a 7.1 host using the 7.0_2018Q2
	packages on using "pkgin".

	The first problem which I've mentioned elsewhere is that as
	part of the latest rebuild & upload, apache 2.4 got upgraded
	from 2.4.33nb1 to 2.4.34.  However, the pkg_summary files
	which are in the same directory still refers to 2.4.33nb1,
	which cannot be found.  We should probably take steps to
	reduce the chances of this problem re-occurring.

	So I thought "fine", let's manually remove apache 2.4 on the
	local host and manually reinstall it afterwards to cross this

	The next hurdle was that pkgin wanted to upgrade pkgin itself,
	but the build result directory doesn't contain pkgin, while
	pkg_summary refers to pkgin-0.11.3.  Again, I thought "fine",
	lets' manually build pkgin from source and install and use
	that, which got me pkgin 0.11.4.

	Doing "pkgin -y fug" it seems that the new pkgin somehow
	disagrees with whatever the old package had left behind,
	causing what I think are nonsense error messages:

# pkgin -y fug
calculating dependencies...done.
pkg_info: can't find package `n/cache/apr-util-1.6.1nb2.tgz'
pkg_info: can't find package `n/cache/freetype2-2.9.1nb1.tgz'
pkg_info: can't find package `n/cache/glib2-2.56.1nb1.tgz'
pkg_info: can't find package `n/cache/harfbuzz-1.8.1.tgz'
pkg_info: can't find package `n/cache/icu-61.1.tgz'
pkg_info: can't find package `n/cache/libgpg-error-1.31.tgz'
pkg_info: can't find package `n/cache/libunistring-0.9.10.tgz'
pkg_info: can't find package `n/cache/libxml2-2.9.8nb1.tgz'

	Try to upgrade a i386 7.1-running host to pkgsrc-2018Q2 using

	Sorry, don't know.



Responsible-Changed-From-To: pkg-manager->jperkin
Responsible-Changed-When: Mon, 20 Aug 2018 08:19:32 +0000
Over to maintainer

State-Changed-From-To: open->feedback
State-Changed-When: Mon, 20 Apr 2020 10:43:02 +0000
I'm guessing this is caused by the call to pkg_info in actions.c where
we are trying to calculate the BUILD_DATE of the packages in question.
However the path looks wrong, is your repositories.conf definitely
pointing at a fully-qualified path?  There have been a few changes since
in this area so also would be good to know if you've ever hit this since
with newer versions.


NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.46 2020/01/03 16:35:01 leot Exp $
$NetBSD:,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2020 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.