commit a2fa6232d1be48152d3c4668c9c8727e9325ea20
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Wed Jun 17 10:54:33 2026 -0700

Revert "tgbugs-meta/kg-release-meta: vbump to drop ipykernel for pypy3_11"

This reverts commit f8a2c2aec14f54359724ac84da144145a77e671c.

commit fecbbe5b5dfcfd50c5b8a0d5eef31a2cb03724d1
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Wed Jun 17 10:54:27 2026 -0700

Revert "tgbugs-meta/kg-release-meta: redigest"

This reverts commit 8b2d86c5841a69e20acbfbf22d33f257c3285c9f.

commit 8b2d86c5841a69e20acbfbf22d33f257c3285c9f
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Wed Jun 17 10:35:10 2026 -0700

tgbugs-meta/kg-release-meta: redigest

commit f8a2c2aec14f54359724ac84da144145a77e671c
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Wed Jun 17 10:33:31 2026 -0700

tgbugs-meta/kg-release-meta: vbump to drop ipykernel for pypy3_11

we'll see if this works, it is a bit of an experiment

commit 9e67bb61f562b2cf4a001390822486fe454e2162
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Sun Nov 23 22:24:52 2025 -0800

tgbugs-meta/kg-release-meta: depend on emacs-pkgs-min-meta

commit 9cb8a14ca3e77375aff1e5bfef917dfa85fad3b2
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Tue Apr 22 17:19:42 2025 -0700

tgbugs-meta: drop x86 and arm, add HOMEPAGE

commit 16984e347df06a812ae3d4da887efbab58b97b01
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Tue Apr 22 00:21:13 2025 -0700

tgbugs-meta: added category for meta packages

I considered a bunch of different names for this category,
but as soon as I started naming the individual ebuilds I
realized that every single one needed to be prefixed with
tgbugs- to avoid potential collisions with other user meta
packages, yes this means that the number of cateogires for
user meta packages wind up proliferating, maybe the package
manager spec could be updated to mitigate the proliferation
but for now it seems like the best solution.

these come from the various world- specifications in
https://github.com/tgbugs/dockerfiles/blob/master/source.org
and represent various environments that we want to be able to
reproduce and more importantly continually test for issues

don't miss the stupid hack of referring to sed at its full path
to use it at the top level to strip comments out of RDEPEND so
that comments can live inline in the RDEPEND section without
causing portage to get angry, this allows ebuilds to contain
additional documentation about deps in line for anyone trying
to use them as a reference