[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#7093: marked as done (dselect: hyperjump into conflict screen is poor UI design)

Your message dated Sun, 10 Oct 1999 02:14:10 -0400
with message-id <19991010021410.E18835@lappy.djj.state.va.us>
and subject line some dpkg bug maintainence with permission from wichert
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

Received: (at submit) by bugs.debian.org; 4 Feb 1997 03:42:28 +0000
Received: (qmail 11006 invoked from network); 4 Feb 1997 03:42:26 -0000
Received: from gigan.extern.ucsd.edu (root@
  by master.debian.org with SMTP; 4 Feb 1997 03:42:26 -0000
Received: from gigan (gobbel@localhost [])
	by gigan.extern.ucsd.edu (8.8.5/8.8.5) with SMTP id TAA01781;
	Mon, 3 Feb 1997 19:36:19 -0800
Sender: gobbel@cogsci.ucsd.edu
Message-ID: <32F6AEB2.373C102@cogsci.ucsd.edu>
Date: Mon, 03 Feb 1997 19:36:18 -0800
From: Randy Gobbel <gobbel@cogsci.ucsd.edu>
Organization: Cognitive Science Dept., UCSD
X-Mailer: Mozilla 3.01Gold (X11; U; Linux 2.0.27 i686)
MIME-Version: 1.0
To: submit@bugs.debian.org
Subject: dselect: hyperjump into conflict screen is poor UI design
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Package: dpkg

There is no reason for dselect to jump straight into the conflict
resolution screen as soon as the user types "+" (or whatever).  This is
jarring, confusing, and not even the best way to deal with the
situation.  Much better would be to put some sort of flag on the screen
saying "conflicts".  Oftentimes, I *know* that package X requires
package Y, but package Y is just farther down in the list.  If dselect
wouldn't be so #$* hyper, I would get to the required package, mark it,
and maybe I wouldn't have to see the hated conflict screen at all.

Bottom line: dselect should only put up the conflict screen at the end
of the "select" session.  It should deal with all conflicts then, and
optionally allow the user to go back to "select" mode at that point if
need be.  I think this would go a long way toward easing Debian users'
trauma in using dselect.

Received: (at 1037-done) by bugs.debian.org; 10 Oct 1999 06:12:48 +0000
Received: (qmail 18194 invoked from network); 10 Oct 1999 06:12:46 -0000
Received: from ppp28.ts1-3.newportnews.visi.net (HELO lappy.djj.state.va.us) (
  by master.debian.org with SMTP; 10 Oct 1999 06:12:46 -0000
Received: from bmc by lappy.djj.state.va.us with local (Exim 3.03 #1 (Debian))
	id 11aCFG-00038m-00; Sun, 10 Oct 1999 02:14:10 -0400
Date: Sun, 10 Oct 1999 02:14:10 -0400
From: Ben Collins <bcollins@debian.org>
To: 1685-done@bugs.debian.org, 16217-done@bugs.debian.org,
	10263-done@bugs.debian.org, 4074-done@bugs.debian.org,
Subject: some dpkg bug maintainence with permission from wichert
Message-ID: <19991010021410.E18835@lappy.djj.state.va.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0pre2i

1685: dpkg-split command line parsing.
  My take on this, the options expected aren't in a compatible format,
  so it can't be made GNU style. Also the man page shows that the
  complained about format is expected. IMO, if it's documented as such,
  then it should be acceptible. GNU is not the endall argument format.

16217: prompting for clearing avail on updates in dselect
  dselect doesn't seem to do this anymore

10263: segfaults on upgrade
  Very old bug concerning libc5->libc6 upgrades. I don't think we have any
  way to really reproduce it, plus the reports show that the cause was
  possibly found from some dependencies, but the original poster never
  responded back.

4074: conffile's left behind
  Not a current problem with dpkg it seems

1037: dselect help screen
  Ian said he would fix this in the report when he released the C version of
  dpkg, that seems to have occured (bug report is vague on what the actual bug
  is, and attempts at clarifying have failed).

Ben....more to come

Reply to: