Re: git for armv7

From: bob prohaska <>
Date: Thu, 04 May 2023 02:32:12 UTC
On Wed, May 03, 2023 at 12:38:58PM -0700, Mark Millard wrote:
> bob prohaska <> wrote on
> Date: Wed, 03 May 2023 18:43:09 UTC :
> > Don't the package servers keep an old package until
> > a new one is successfully built to supercede it?
> That would work only if each package was independent
> of all the others. Otherwise it could be doing things
> like mixing an older git package with more recent
> package(s) that provide, for example:
> /usr/local/lib/
> /usr/local/lib/
> Such combinations need not be compatible with each
> other. So, generally, far more older material
> would have needed to be kept around and version
> matched with the git download. Everything else
> dependent on those 2 libraries would also have
> to be dealt with as well. That might involve more
> libraries and more programs. Such handling is
> a mess and is resource intensive. It is not done.
> The old git package stuck around until the
> distribution of the packages from the first
> failure to build libunwind made it to the
> download servers.

Ahh, that makes sense. Old packages have too
much baggage 8-) for the public servers. 

What happens in the case of a local poudriere
repository? If it once builds a package, which
subseqently fails, is the successful build

The origins of my particular fiasco are still
a mystery. It looks as if I somehow uninstalled
git, along with its man pages. No idea how.
At this point there's no compelling necessity
to fix the faulty -current host. I'll wait. 

Thanks very much for writing!

bob prohaska