[pkg-go] Bug#923722: golang-github-appc-cni: Please upgrade to new upstream 0.7.0-alpha1
Cirujano Cuesta, Silvano
silvano.cirujano-cuesta at siemens.com
Wed Jun 12 10:15:39 BST 2019
Hi Reinhard,
On Mon, 2019-03-04 at 07:20 -0500, Reinhard Tartler wrote:
> Package: golang-github-appc-cni
> Severity: wishlist
>
> Hi,
>
> Please update to new upstream version of 0.7.0-alpha1. I need it as a
> build dependency of http://github.com/containers/buildah
By now you could try to get 0.7.1, released a couple of hours ago:
https://github.com/containernetworking/cni/releases/tag/v0.7.1
>
> In fact, I've done so locally, and would be happy to upload it as a Team
> Upload. I was running into issues while doing so. Unlike the git
> repositories created by the dh-make-golang tool, the git repository on
> salsa at
> https://salsa.debian.org/go-team/packages/golang-github-appc-cni does
> not include full sources in the packaging branch. I am unfamiliar with
> that workflow and it is inconsistent with how the vast majority of the
> packages in the golang team are handled. I therefore decided to start
> off from a 'dgit clone' created repository.
>
> Dimtry, I wonder what your thoughts on this issue are. Would you be OK
> with switching the workflow? If not, could you please upload
> 0.7.0-alpha1 to experimental soon? Alternatively, I could upload the
> package that I have locally to experimental, and leave updating salsa to
> you (or someone else) whenever time permits.
>
> What does the rest of the team think about competing git repository
> workflows within the team? At least to me, this seems undesireable
> because it prompts convesations like this (which I really don't enjoy
> having).
I'm also puzzled why this packaging.
Just my 2 cents, although I'm not part of the team, but having a look at
some packages needed for containers.
>
> Best,
> -rt
>
A different, but related question. Are there any known efforts to package the reference plugins?
BR,
Silvano
More information about the Pkg-go-maintainers
mailing list