Re: Non-understood advice - was Re: dist-upgrade from sarge to etch - package
- To: email@example.com
- Subject: Re: Non-understood advice - was Re: dist-upgrade from sarge to etch - package
- From: Daniel Burrows <firstname.lastname@example.org>
- Date: Fri, 08 Feb 2008 18:40:09 -0800
- Message-id: <20080209024009.GA11848@alpaca>
- In-reply-to: <email@example.com>
- References: <20080204180815.GB25142@pc0197> <firstname.lastname@example.org> <20080205175408.GA2054@pc0197> <email@example.com> <firstname.lastname@example.org>
On Fri, Feb 08, 2008 at 08:54:02PM +0000, Felix Karpfen <email@example.com> was heard to say:
> On Wed, 06 Feb 2008 20:34:14 +0000, Felix Karpfen wrote:
> They failed to address my misunderstanding and the fault was mine.
> My concern arose not from the absence of "vuescan" (which - as pointed
> out - is a monolithic binary package) but the presence of many dozens
> of packages that were *not* non-Debian packages.
> The concern arose from the fact that - following the upgrade
> instructions to the letter - I recollect running a command that
> identified non-Debian packages as part of the upgrade to Etch and *the
> command gave the expected output*. But, alas, I can no longer find
> what that command was.
I'm now completely confused. The problem is just that you want to
find the command that you ran before? Am I understanding correctly?