On Mon, 8 Mar 1999, Maarten Boekhold wrote:
> [Note: this is a repost, since nobody responded to it, yet I find it
> hard to believe that nobody knows the answer to my question.]
>
> Hi,
>
> Yesterday I wondered how much MBs I'd have to download to upgrade my
> hamm
> system (plus *some* slink
> So, does this mean I'll have to go into dselect and see if these
> packages are placed on hold? I wonder how this happens, cos for sure I
yip
> never did this myself, and I can't remember ever having had serious
> problems with dpkg etc. which might have automagically marked these
> packages a
[EMAIL PROTECTED] wrote:
>
> > This showed numerous packages as being 'kept back':
>
> Packages are held back when you choose Hold in dselect. When there are
> dependancy/conflict errors apt tells you.
So, does this mean I'll have to go into dselect and see if these
packages are placed on hold
> This showed numerous packages as being 'kept back':
Packages are held back when you choose Hold in dselect. When there are
dependancy/conflict errors apt tells you.
Regards
Sarel Botha
[Note: this is a repost, since nobody responded to it, yet I find it
hard to believe that nobody knows the answer to my question.]
Hi,
Yesterday I wondered how much MBs I'd have to download to upgrade my
hamm
system (plus *some* slink stuff in there) to slink, so I set my
sources.list
and did 'ap
Hi,
Yesterday I wondered how much MBs I'd have to download to upgrade my
hamm
system (plus *some* slink stuff in there) to slink, so I set my
sources.list
and did 'apt-get update' + 'apt-get upgrade' (and answered 'no' ;).
This showed numerous packages as being 'kept back':
The following package
6 matches
Mail list logo