From Newsgroup: muc.lists.freebsd.ports

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.
Is it likely to break anything if we just "rm" those packages or is there some internal state table that needs cleaning up?
Also, is there any trick to making it so I can still get those jails to launch in poudriere?--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports


--3yZWSxSKENDLYNMc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thursday, 9 October 2025 at 17:53:32 -0700, Dan Mahoney (ports) wrote:

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.

Maybe I misunderstand, especially since you don't mention specific
ports, but age or lack of support are not adequate reasons to remove a
port. Cases in point:

graphics/xv This hasn't been updated for years, but it Just Works.
I would be sad to see it go away.

x11/xtset Last updated in the last millennium. I use it
constantly.

Is it likely to break anything if we just "rm" those packages or is
there some internal state table that needs cleaning up?

Removing either of those ports would break things for me.

Greg
--
Sent from my desktop computer.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

--3yZWSxSKENDLYNMc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQSaG4ICvM64RvkvCawi5vKQUHpCIwUCaOiRuwAKCRAi5vKQUHpC I5sOAJ9/3LOa0AeCmjVO6uYgW0feoCwm6wCcC78PxXWqvCsYq6BBpSo/CWqYrsY=
=NVuF
-----END PGP SIGNATURE-----

--3yZWSxSKENDLYNMc--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports


--9uz0AfUK3qDXy4eL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Dan Mahoney (ports) wrote in <0E6F01CA-6AD3-42CE-96BE-81016174344A@gushi.or= g>:

We have a repo that has packages in it from no-longer launchable or no-longer-existing jails/ports trees. [...]
=20
Is it likely to break anything if we just "rm" those packages or is
there some internal state table that needs cleaning up?

after deleting packages from a repository, you should re-run pkg-repo(8)
to remove the stale metadata in the repository metadata files.

--9uz0AfUK3qDXy4eL
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCaOiTpgAKCRD1nT63mIK/ YH6cAP0b+AfBwzaUpWvKd7zB1cAQwM1h4ddfInAtfEllmCEcQQEAqXmygHLc92tp yUeT62lKjZBH1/+BlZFYLBnUE1J4GQo=
=9h+E
-----END PGP SIGNATURE-----

--9uz0AfUK3qDXy4eL--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Fri, Oct 10, 2025 at 3:54rC>AM Dan Mahoney (ports) <freebsd@gushi.org> 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? If you're using poudriere to
build it, then you'll end up with a separate repo for each
(jail,ports) pair you have used. When you remove a jail, you also have
to remove the corresponding repos without any fear.
And whenever you run poudriere bulk on your (jail,ports) combination,
it removes all the stale packages, so you can't possibly end up with
ancient packages in the repo.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Sat, Oct 11, 2025 at 3:31rC>AM Dan Mahoney (Gushi)
<danm@prime.gushi.org> wrote:

On Fri, 10 Oct 2025, Gleb Popov wrote:

On Fri, Oct 10, 2025 at 3:54rC>AM Dan Mahoney (ports) <freebsd@gushi.org> 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.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Fri, 10 Oct 2025, Greg 'groggy' Lehey wrote:

graphics/xv This hasn't been updated for years, but it Just Works.
I would be sad to see it go away.

Yup; I use it a lot for basic image manipulation (GIMP is just too heavy).

-- Dave


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Mon, Oct 13, 2025 at 06:32:44AM +1100, Dave Horsfall wrote:

graphics/xv This hasn't been updated for years, but it Just Works.
I would be sad to see it go away.

Yup; I use it a lot for basic image manipulation (GIMP is just too heavy).

Have you looked at ImageMagick? It can do that, and is current and
maintained. It knows some newer image storage formats that xv doesn't
(eg webp, heic).

<https://imagemagick.org/>
graphics/ImageMagick7


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2