|Summary:||app-portage/gs-pypi - database not being autogenerated|
|Product:||Gentoo Linux||Reporter:||Bearcat M. Şándor <bearcatsandor>|
|Component:||Overlays||Assignee:||Brian Dolbec <dolsen>|
|Severity:||normal||CC:||bearcatsandor, layman, lebedev.vasya, treecleaner|
|Whiteboard:||Pending removal: 2018-12-11|
|Package list:||Runtime testing required:||---|
Description Bearcat M. Şándor 2017-01-29 21:38:42 UTC
The files that gs-pypi provides are very outdated. For instance, Mopidy is at version 1.1.1, whereas the version on pypi.org is at 2.1.0. It appears that the repository at https://github.com/jauhien/gs-pypi-db/ is not being updated and it's a year old. In the bug filed at https://github.com/jauhien/gs-pypi/issues/10 it's suggested to do the dbupdate by hand, but this brings down all of the package data and that essencially does what is strongly reccomended against on the gs-pypi man page. Can we have the ebuild just by-pass the git repo that is no longer maintained and perform this local dbupdate but have it read the packages list that have been put into /etc/g-sorcery/g-sorcery.cfg. Or is gs-pypi dead and we should just make regular ebuilds for the things that we want?
Comment 1 Benda Xu 2017-09-15 06:18:23 UTC
Thank you for your report. I can reproduce this bug.
Comment 2 Bazz 2018-01-11 14:51:27 UTC
I'm getting the exact same problem.
Comment 3 Michał Górny 2018-12-11 13:35:52 UTC
Removing wrt #659414.