Bug#1022798: duplication of library vs updating dependencies
On Wed, Oct 26, 2022 at 10:45 PM Jeffrey Cliff <jeffrey.cliff@gmail.com> wrote:
>
> "duplicate the source."
>
> it is one thing that could be done
>
> the other way is for the packages that are staled by this upgrade of
> golang-goprotobuf-dev (which is what this appears to be, in a separate
> package) to be updated
>
> would that not be the way these kinds of upgrades would normally
> occur, insated of just accepting the go ecosystem's needless
> duplication of libraries?
>
> was there any discussion that lead to this duplication of this library
> as a way out of this particular dependency hell somewhere?
>
https://lists.debian.org/debian-go/2020/07/msg00006.html
https://lists.debian.org/debian-go/2021/08/msg00061.html
https://lists.debian.org/debian-go/2022/06/msg00070.html
Well, one thread per year from 2020.
tl,dr
Because some important packages can't be migrated to the new version,
and removing that would mean removing all the container tools like
containerd/docker/podman.
--
Shengjing Zhu
Reply to: