Comment 5 for bug 75332

On Tue, May 07, 2002 at 12:10:38AM -0400, Faheem Mitha <email address hidden> was heard to say:
>
>
> On Sat, 4 May 2002, Daniel Burrows wrote:
>
> > On Sat, May 04, 2002 at 12:17:32AM -0400, Faheem Mitha <email address hidden> was heard to say:
> > > b) that if you put a package (say foo) on hold in the traditional way,
> > > # echo "foo hold" | dpkg --set-selections
> > > this is completely ignored by aptitude.
> >
> > Could you give me a reproducible test case? This has always worked
> > for me.
>
> That is strange. I get this behaviour with every package I tried. Ok, here
> is an example of a run (with vim).
>
> Chrestomanci:~# dpkg --get-selections | grep vim
> vim hold

  hm, it seems that this is broken for when you use the command-line; the
interactive UI picks it up just fine. Why this should be, I don't know;
it's probably a side effect of the way the command-line initializes the
backend (it doesn't select as many things automatically, so that things like
single-package installs work)

  Daniel

--
/-------------------- Daniel Burrows <email address hidden> -------------------\
| "But what *does* kill me bloody well leaves me dead!" |
| -- Terry Pratchett, _Carpe Jugulum_ |
\-- Does your computer have Super Cow Powers? ------- http://www.debian.org --/