On Sun, Aug 01, 2021 at 10:32:55AM +1000, terryc wrote:
> On Sat, 31 Jul 2021 16:03:53 -0400
> Hendrik Boom <hendrik@???> wrote:
>
> > I'm practicing upgrades on my spare laptop, getting ready for doing
> > my server upgrade from ascii to beowulf..
> >
> > They are both running ascii.
> >
> > Starting, of course, by making the ascii up to date still as ascii,
> > before I try tye upgrade to beowulf.
> >
> > Having trouble doing even this innocuous act.
> >
> > I tried starting by using interactive aptitude to just update and
> > upgrade.
> >
> > Only to discover that *every* package that might be upgraded was
> > "held", and could therefore not be upgraded even though newer
> > packages were available.
> >
> > What could be causing this? Or rather, how should I go about trying
> > to track down the origin of these holds/this mass hold?
> >
> > 55 packagesin the list of packages held back.
> > and
> > 282 packages being "automatically held in their current state".
>
> Could they require a "dist-upgrade"
> IME, that usually deals with held packages.

I'll try that.

But I would like to get some idea why all the
apparently upgradable packages are held. I certainly don't
remember asking anything to be held.

-- hendrik

>
> >
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng