Re: Killing some old packages

On Sat, Oct 11, 2025 at 3:31 AM Dan Mahoney (Gushi)
<[email protected]> wrote:
>
> On Fri, 10 Oct 2025, Gleb Popov wrote:
>
> > On Fri, Oct 10, 2025 at 3:54 AM Dan Mahoney (ports) <[email protected]> wrote:
> >>
> >> Hey there folks,
> >>
> >> We have a repo that has packages in it from no-longer launchable or no-longer-existing jails/ports trees.  (Jails going back to release-8-eol, when we needed to build packages for systems we couldn't update due to lack of remote hands and lack of disk space/failing hardware/layer9 issues).  IYKYK.
> >
> > How did you end up with such a repo?
>
> So, as mantioned, these were old from when we had machines out in the
> field that we couldn't upgrade, (but for which I might need a more current
> version of a piece of software), had failing raid cards, had disks that
> were too small, etc.
>
> So, I'm now stick with packages from where I:
>
> * Had ports trees that were deleted/renamed (like 2017Q3), and packages
> are only deleted when you remove a jail, not when you delete a ports tree.
>
> * Had jails that got too old to start so I can no longer prune them.

There should be no such thing as "jail too old to start", unless
you're running a custom kernel without COMPAT_* options.

Anyways,

> Here's a partial ls of my packages dir:
>
> freebsd:10:x86:32-2017Q3
> ...

these look like repositores dirs, so it should be safe to just remove them.