app-office/fava
Web interface for the Beancount plain-text accounting system
Screenshots
View
Download
BrowseChangeLog
commit 14a4c7272696d3ac33381f7567793c8cd35c31df
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 10:34:04 2026 +0200
app-office/fava: declare the setuptools build dependency, revbump
Upstream's build-system.requires names setuptools >= 80 and the ebuild
never declared it. Nothing else supplied it either:
DISTUTILS_USE_PEP517=standalone hits an empty case in distutils-r1, so
unlike every other backend value it contributes no build dependency,
and setuptools reached the build only through setuptools-scm's own
>=dev-python/setuptools-64.
That leaves an effective floor of 64 against upstream's 80, and
::gentoo still carries an installable setuptools-79.0.1 next to 82.0.1
and 83.0.0, so the too-old case is reachable rather than theoretical.
Both shipped versions declare the same requirement and both are fixed.
Upstream's Babel <3 upper bound is deliberately not mirrored; 2.18.0 is
the only babel in the tree, so the cap cannot bind.
commit d26e488d095396a8343a1053601f18f59982a8df
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 10:04:12 2026 +0200
*/*: drop dead Python targets from PYTHON_COMPAT
139 ebuilds across 65 packages still listed python3_10, python3_11 or
python3_13t. None of the three is a supported implementation any more:
gentoo's python-utils-r1 sets _PYTHON_ALL_IMPLS to python3_ plus
python3_t, and everything older falls into the branch commented
"implementations deprecated prior to EAPI 9 are fatal".
Inert today, which is why nothing caught it. Targets outside
_PYTHON_ALL_IMPLS are silently dropped rather than rejected, so they
never became USE flags and never produced a dependency atom -- an ebuild
declaring python3_ was only ever offering 12, 13 and 14.
Two reasons to clean them up anyway. The eclass branch they land in
dies for any EAPI other than 7 or 8, so all 139 are waiting to break on
the first EAPI 9 bump. And pkgcheck's OldPythonCompat is a git-scoped
check that only inspects ebuilds touched in a commit range, so it never
reports these on a full-tree scan and would instead fire on whichever
unrelated commit next touches one of them.
No revbump, because nothing observable changes. Verified on a sample
spanning every transformation shape that the python USE flags portage
offers are byte-identical before and after, and that a pkgcheck run
over all 65 packages returns a set-identical list of findings.
The eight python2_7 ebuilds are deliberately untouched: that target is
also absent from _PYTHON_ALL_IMPLS, but they reach it through the
_PYTHON_ALLOW_PY27 hatch in the overlay's forked python-utils-r1_py2.
commit 5f01e4eb7bd90bc7c0c97df4a94fe304f1662c7a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 18 10:36:01 2026 +0200
app-office/fava: Keyword 1.30.14 for ~arm64
commit 2e442c36dd5119a100a83f15ebce604b9fcb627b
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Jun 17 00:57:07 2026 +0200
app-office/fava: Keyword 1.30.13 for ~arm64
Pure-Python (PEP517), architecture-independent.
commit 753cfd692ce74d49d5c0259d6ee4509b8d851eb1
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 18 07:43:21 2026 +0200
app-office/fava: add 1.30.14
commit 39ddd240bbf1a925f70d83936a1c66dfb9315c15
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 2 19:17:14 2026 +0200
app-office/fava: new package, add 1.30.13
Web UI for Beancount. The standalone backend compiles .po catalogues via
Babel; the JS bundle and .mo files ship pre-built, so the npm frontend step
is neutralised in src_prepare. beanquery held <0.3; the excel extra is
dropped (pyexcel not in ::gentoo).
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 10:34:04 2026 +0200
app-office/fava: declare the setuptools build dependency, revbump
Upstream's build-system.requires names setuptools >= 80 and the ebuild
never declared it. Nothing else supplied it either:
DISTUTILS_USE_PEP517=standalone hits an empty case in distutils-r1, so
unlike every other backend value it contributes no build dependency,
and setuptools reached the build only through setuptools-scm's own
>=dev-python/setuptools-64.
That leaves an effective floor of 64 against upstream's 80, and
::gentoo still carries an installable setuptools-79.0.1 next to 82.0.1
and 83.0.0, so the too-old case is reachable rather than theoretical.
Both shipped versions declare the same requirement and both are fixed.
Upstream's Babel <3 upper bound is deliberately not mirrored; 2.18.0 is
the only babel in the tree, so the cap cannot bind.
commit d26e488d095396a8343a1053601f18f59982a8df
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 10:04:12 2026 +0200
*/*: drop dead Python targets from PYTHON_COMPAT
139 ebuilds across 65 packages still listed python3_10, python3_11 or
python3_13t. None of the three is a supported implementation any more:
gentoo's python-utils-r1 sets _PYTHON_ALL_IMPLS to python3_ plus
python3_t, and everything older falls into the branch commented
"implementations deprecated prior to EAPI 9 are fatal".
Inert today, which is why nothing caught it. Targets outside
_PYTHON_ALL_IMPLS are silently dropped rather than rejected, so they
never became USE flags and never produced a dependency atom -- an ebuild
declaring python3_ was only ever offering 12, 13 and 14.
Two reasons to clean them up anyway. The eclass branch they land in
dies for any EAPI other than 7 or 8, so all 139 are waiting to break on
the first EAPI 9 bump. And pkgcheck's OldPythonCompat is a git-scoped
check that only inspects ebuilds touched in a commit range, so it never
reports these on a full-tree scan and would instead fire on whichever
unrelated commit next touches one of them.
No revbump, because nothing observable changes. Verified on a sample
spanning every transformation shape that the python USE flags portage
offers are byte-identical before and after, and that a pkgcheck run
over all 65 packages returns a set-identical list of findings.
The eight python2_7 ebuilds are deliberately untouched: that target is
also absent from _PYTHON_ALL_IMPLS, but they reach it through the
_PYTHON_ALLOW_PY27 hatch in the overlay's forked python-utils-r1_py2.
commit 5f01e4eb7bd90bc7c0c97df4a94fe304f1662c7a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 18 10:36:01 2026 +0200
app-office/fava: Keyword 1.30.14 for ~arm64
commit 2e442c36dd5119a100a83f15ebce604b9fcb627b
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Jun 17 00:57:07 2026 +0200
app-office/fava: Keyword 1.30.13 for ~arm64
Pure-Python (PEP517), architecture-independent.
commit 753cfd692ce74d49d5c0259d6ee4509b8d851eb1
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 18 07:43:21 2026 +0200
app-office/fava: add 1.30.14
commit 39ddd240bbf1a925f70d83936a1c66dfb9315c15
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 2 19:17:14 2026 +0200
app-office/fava: new package, add 1.30.13
Web UI for Beancount. The standalone backend compiles .po catalogues via
Babel; the JS bundle and .mo files ship pre-built, so the npm frontend step
is neutralised in src_prepare. beanquery held <0.3; the excel extra is
dropped (pyexcel not in ::gentoo).