[ale] ? about Debian pks held back in upgrade

[Jim Seymour]

On Sat, Jan 03, 2004 at 07:51:22PM -0500, James Sumners wrote:
> Err, it can also mean a broken package or a package with broken dependencies.
> Your best bet is to check http://bugs.debian.org/<package_name> for more
> information before manually installing a package that is being kept back.
> Generally, it is being kept back for a good reason.
> 
> On Sat, 3 Jan 2004 15:06:23 -0500
> Jason Day <jasonday at worldnet.att.net> wrote:
> 
> > On Sat, Jan 03, 2004 at 02:17:24PM -0500, Jim Seymour wrote:
> > > I think I've read this one before but can't remember the answer.  When 
> > > you do a "apt-get update" and then your "apt-get upgrade" you 
> > > sometimes see several packages marked as "kept back".  I think these are 
> > > packages that are broken.  Is that correct?  Also if that is the case 
> > 
> > No, they're not broken, but their dependencies have changed such that
> > APT cannot upgrade them without your help.  To see why a particular
> > package has been kept back, just apt-get install the package in
> > question.  APT will probably complain about a new dependency that must
> > be installed, or conflicting dependencies, but it's usually not a big
> > deal to fix.
> > 
> > Alternatively, you could try "apt-get -u dist-upgrade", which will do a
> > more intelligent and "deeper" dependency resolution.

Thanks Folks,
	I will check for bug reports and see what I can come up with.  
At this point I have 15 packages being held back.

Later,

Jim Seymour
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature