sci-ml/modelscope
ModelScope: bring the notion of Model-as-a-Service to life
Screenshots
View
Download
BrowseChangeLog
commit 530df07c6bc5c6bee04acd5f0d1e67876562236e
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Aug 5 12:33:35 2026 +0200
sci-ml/modelscope: drop 1.38.1
commit e76650b3befe40263200a35b69278254abbc57fb
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Aug 5 12:33:30 2026 +0200
sci-ml/modelscope: add 1.39.1
Bump the modelscope-hub floor to 0.2.0 to match the release's requirements/hub.txt.
commit bc39991a7150143b571edb2db7948a8cf8335ace
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Jul 29 10:16:21 2026 +0200
sci-ml/modelscope: drop 1.38.0
commit 8a462037101e6efb480fcdda18a681b35efb3c73
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Jul 29 10:16:08 2026 +0200
sci-ml/modelscope: add 1.39.0
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 1bb9f43f07a30aace891c85caded1f64c7cdc553
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jul 7 00:47:42 2026 +0200
sci-ml/modelscope: add 1.38.1
commit fca26e71af9c63150c4bf229516c5a9aab7d4880
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Jul 4 14:13:27 2026 +0200
sci-ml/modelscope: new package, add 1.38.0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Aug 5 12:33:35 2026 +0200
sci-ml/modelscope: drop 1.38.1
commit e76650b3befe40263200a35b69278254abbc57fb
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Aug 5 12:33:30 2026 +0200
sci-ml/modelscope: add 1.39.1
Bump the modelscope-hub floor to 0.2.0 to match the release's requirements/hub.txt.
commit bc39991a7150143b571edb2db7948a8cf8335ace
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Jul 29 10:16:21 2026 +0200
sci-ml/modelscope: drop 1.38.0
commit 8a462037101e6efb480fcdda18a681b35efb3c73
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Jul 29 10:16:08 2026 +0200
sci-ml/modelscope: add 1.39.0
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 1bb9f43f07a30aace891c85caded1f64c7cdc553
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jul 7 00:47:42 2026 +0200
sci-ml/modelscope: add 1.38.1
commit fca26e71af9c63150c4bf229516c5a9aab7d4880
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Jul 4 14:13:27 2026 +0200
sci-ml/modelscope: new package, add 1.38.0