As is standard golang practice, dependency ABIs were changed within a single git revision without any version bump (if any version existed at all). This situation will produce build failures from any attempt to update the package. In fact, I believe a number of dependencies have already been auto-removed from Debian because of build failures.
You're argument that gogs would be better is 1) based on absolutely nothing but your own personal opinion, 2) completely and utterly irrelevant, and 3) continues proving how little you care about the DFSG. If I had continued pursuing gogs and stopped at the same point, gogs would be in exactly the same situation, facing the same problems. I did not continue packaging gogs because the owner would not accept patches/requests to fix these problems. Of course, this wouldn't be an issue for the gogs packages you (Piccoro) have created because you are in no way concerned about DFSG, CVEs, or reproducibility. (I say this after having looked at the packages you created.) As things currently sit, the gitea package and subsequent dependencies have been orphaned. My opinion is that gitea does not belong in the debian archives. Gogs has proven to be a substantially lesser candidate. In order for this bug to be resolved, someone will have to adopt the package. -- Michael Lustfield _______________________________________________ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers