For the dependencies, I'd probably suggest attempting to parse
https://github.com/moby/moby/blob/v24.0.9/vendor.mod into a list of
versioned Depends: directly, since those aren't likely to be bumped
upstream "willy nilly" (and IMO that would make it easier to determine
which things need to be packaged and/or which packaged things might need to
be updated in Debian or used from vendor/).

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


On Thu, 16 May 2024 at 17:33, Reinhard Tartler <siret...@gmail.com> wrote:

> Hi,
>
> copying everyone currently listed as co-maintainer of the docker.io
> package in Debian.
>
> I've decided to give this thing a stab. It seems Debian currently ships
> the same minor upstream version of docker.io 20.10 as we had in unstable,
> and more and more packages (such as podman) require significantly newer
> versions  of docker. This is starting to do a serious disservice to our
> users.
>
> My current work in progress lives in
> https://salsa.debian.org/go-team/packages/docker/-/tree/siretart/docker24?ref_type=heads.
> So far, I've:
>
> - identified that libnetwork got merged into gh:moby/moby, so I've removed
> references from the packaging
> - tried to follow README.source as much as possible
> - identified vendored sources and updated the Files-Excluded fields and
> debian/copyright as appropriate
> - refreshed patches against the new upstream version
> - identified circular dependencies and chose vendored versions to unbreak
> them.
>
> What I would appreciate help with:
>
> - reviewing what I've done. This is a very complex package that is done in
> a style that I'm not used to work with
> - help getting it to build (it currently doesn't, I suspect because at
> least some dependencies in debian are too old. I guess using vendored
> copies is the most expedient way to go about this?
> - update debian/copyright for new code additions
> - identify and drop unnecessary dependencies from debian/control.
>
> Thank you so much for your support and assistance!
>
> -rt
>
>
> --
> regards,
>     Reinhard
>

Reply via email to