Hello, Missatge de Dmitry Smirnov <only...@debian.org> del dia dc., 12 de set. 2018 a les 2:29: > > On Wednesday, 12 September 2018 4:01:24 AM AEST Héctor Orón Martínez wrote: > > Since `docker.io` reached testing, could you please consider backporting > > it to stable?
> No, please... Maintaining Docker is an enormous time sink. I doubt backports > will ever happen and certainly I don't want to be involved. The whole point to bring back `docker.io` package to Debian was to provide something usable in stable. > I'm contemplating orphaning Docker and the only reason I'm still looking > after it is because I think it is strategically important for Debian success. I think so too, please keep up the good work, I am willing to help (note I collaborated with Arnaud Rebillout) for docker.io to be back again in Debian. > I don't like Docker. It is very sloppy, bloated, over engineered with > selfish, uncooperative fork-obsessed upstream who refuses to adopt good > versioning practices making our work very difficult. I agree, but it is key package for Debian and it's users. > Recently I've switched all my containers to _rkt_ and I'm very happy about > that. I have never used rkt > Whoever needs Docker can install it straight from "testing" since Docker is > statically linked. I can't justify the effort required to maintain the > official backport. Hopefully we (Arnaud and I, and maybe other people can join a docker-team) can help on that. > > What kind of work would be needed to ease the path to provide such > > backport? > > Man time required to backport hundreds of dependency libraries and even more > time to maintain all those, resolve complicated transitions, build/test > failures and tight versioning. Team of several people working full time for > months - that's what it will take. If we embedded in the package most of the vendoring, would that help on its future maintenance? I know that might be a bit controversial however I think it might be the only way to keep docker.io in the distribution going further ahead. > We are nowhere near the point where it would be safe to backport a monster > package like Docker. First, I'd like to suggest having a real team > maintaining Docker, not just myself. I've already invested too much time into > Docker at the great personal cost and expense of other worthy projects/ > packages. I'm not going to stick much longer... Your involvement has been key to give latest push and unblock latest issues, it was great to find you managed to actually get docker.io uploaded back to Debian. Thanks for that and all the hard work. I am also pretty short time, however I'll try to be helpful going forward. > Besides just keeping Docker in testing is a challenge due to build/test > failures routinely exposed by CI. Docker dependency tree is very big and > surface for problems is enormous. Are you using Gitlab provided CI/CD features to track that? I'd need to get up to speed with those. > I wholeheartedly recommend using _rkt_ instead and it looks like rkt would be > actually possible to backport. I would need to look at that, however, that's a different package. Regards, -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
