NetBSD Problem Report #51417
From firstname.lastname@example.org Wed Aug 17 07:36:06 2016
Received: from mail.netbsd.org (mail.netbsd.org [18.104.22.168])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
by mollari.NetBSD.org (Postfix) with ESMTPS id 0A7D37A266
for <gnats-bugs@gnats.NetBSD.org>; Wed, 17 Aug 2016 07:36:06 +0000 (UTC)
Date: Wed, 17 Aug 2016 09:35:59 +0200 (CEST)
Subject: pkgin should put all interaction up-front
>Synopsis: pkgin should put all interaction up-front
>Arrival-Date: Wed Aug 17 07:40:00 +0000 2016
>Last-Modified: Wed Aug 17 07:56:42 +0000 2016
>Release: NetBSD 7.0
System: NetBSD smistad.uninett.no 7.0 NetBSD 7.0 (GENERIC.201509250726Z) amd64
pkgin can in at least two cases ask interactive questions at
... "inconvenient times":
1) During "pkgin fug" it may have done lots of downloads
before it discovers that the package repository doesn't
have either the "xv" program nor the "adobe-flash-plugin"
package (e.g. when one of the dependencies is going to be
pkgin will then abort the download, and at that point
forcing the operator to manually remove the package
(possibly after pkg_tarup) before re-doing "pkgin fug".
Instead, pkgin should discover this up-front before
starting the download phase, and possibly refuse to proceed
before the problem is fixed as suggested above.
This so that the operator can do away with all the
interaction up front and then proceed to let pkgin complete
the task on its own without the need for further
2) During a "pkgin fug", when upgrading to a new pkgsrc
branch, it's likely that the pkg_install package will need
to be upgraded. However, pkgin insists on an
interactively-given permission for upgrading this package,
and insists on that interaction before upgrading this
particular package, which, it appears, is always the first
package to be upgraded (if it will be upgraded).
This happens after a long phase of non-interaction
(download of new packages and removal of all packages which
will be upgraded). Somehow pkgin appears to consider
pkg_install a "special" packge that it needs special
permission to upgrade (why?!?).
Meanwhile the system keeps sitting there with possibly
precious few packages installed, probably in a state of
strictly reduced functionality compared to what the
I would primarily suggest that the interactive promt for
upgrading pkg_install be abolished altogether (what happens
if you say "no"? Does it abort the whole upgrade?).
Alternatively if the prompt is retained, I would suggest
that the question be asked *before* the download of the new
packages is started, so that it happens at a time when the
operator has attention.
Ref. description above.
Suggested fixes of behaviour given above. No code, though...
Responsible-Changed-When: Wed, 17 Aug 2016 07:56:42 +0000
Emile, can you please give a look? (over to MAINTAINER)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2014
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.