Hello Oleg, Am Sat, Feb 22, 2025 at 09:28:45AM +0000 schrieb Sharlatan Hellseher: > Upstream has last time activity in 2019 > <https://gitlab.com/ambrevar/demlo>, as for me, it's more dead project > than alive :-). > Question to the team: Demplo holds a bunch of quite old, never updated > in upstream list of Golang dependencies, do we have any common sense > practice to clean up dormant-never-updated projects?
notice that upstream was also the packager; there is a certain probability that the package has never been used by anyone else. Independently of this, we tend to keep unmaintained software as long as it compiles; I would argue that if updating the dependencies breaks the compilation, it does not compile any more. So my conclusion would be that this package can be removed. There is a deprecation policy in the manual: https://guix.gnu.org/manual/devel/en/html_node/Deprecation-Policy.html "Packages whose upstream developers have declared as having reached “end of life” or being unmaintained may be removed; likewise, packages that have been failing to build for two months or more may be removed." To comply with the requirements literally, one would need to remove the outdated dependencies first, then wait two months and declare the package as not having been built. I think this is a bit silly and would argue that we have reached this point - the software is not "declared (...) unmaintained", but it is unmaintained. "If the package being removed is a “leaf” (no other packages depend on it), it may be removed after a one-month review period of the patch removing it" So I would suggest to send this patch to the issue tracker, maybe cc-ing the packager, and see what happens during the month. Andreas
