Bug#898689: ITP: golang-github-ostreedev-ostree-go -- Golang bindings for httt://github.com/ostreedev/ostree
Currently ostree-go, commit d0388bd (master HEAD today) fails some tests:
=== RUN TestCommitTreeSuccess
--- FAIL: TestCommitTreeSuccess (0.11s)
commit_test.go:108: failed to tar populated dir: read
/tmp/otbuiltin-test-179055475/commit1: is a directory
=== RUN TestCommitTreeParentSuccess
--- FAIL: TestCommitTreeParentSuccess (0.05s)
commit_test.go:169: failed to tar populated dir: read
/tmp/otbuiltin-test-662857270/commit1: is a directory
My first intention was package all skopeo dependencies, then skopeo,
then upload all packages.
Sadly, it showed very ambitious and I can't had the time to do it.
If i remember well, the version from 'Sjoerd Simons' pass all the tests.
About the ITP, if help, i can update the version to the one used by
skopeo (currently 56f3a63,
exclude the failing tests.
I never had upload a package to debian, maybe you can do it from the
repository if time is pressing.
On Wed, Jan 9, 2019 at 11:58 AM Alexandre Viau <email@example.com> wrote:
> On 2019-01-09 6:54 a.m., Reinhard Tartler wrote:
> > Hi Juan,
> > are you still working on this ITP? I was looking at skopeo as well,
> > and stumpled upon this ITP. I noticed that you created a repository on
> > salsa:
> > https://salsa.debian.org/go-team/packages/golang-github-ostreedev-ostree-go
> > This package never got uploaded.
> > However, I also noticed that there is another packaging repo in salsa,
> > which contains a similar package that did get uploaded:
> > https://salsa.debian.org/go-team/packages/golang-github-sjoerdsimons-ostree-go
> > https://tracker.debian.org/pkg/golang-github-sjoerdsimons-ostree-go
> > I wonder what the relationship between these two are. It seems that the
> > sjoerdsimons
> > version does declare it satisfies the import of the
> > github:ostreedev/ostree-go repo,
> > which makes me believe it is a fork.
> Looking at the upstream website will show you that yes it is a fork.
> (forked from ostreedev/ostree).
> > If this is the case, can we consider this ITP abandoned and close it?
> You need the package for skopeo but you want to close the ITP? I don't
> understand what is your end goal here.
> Unless the package is not needed in Debian anymore, we wouldn't close
> ITPs if they were abandoned. Instead, we would change them into RFPs.
> If you want to take over the ITP, the thing to do would be to assign it
> to you.
> Alexandre Viau