[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#890984: marked as done (ITP: golang-github-containerd-btrfs -- Btrfs bindings for Go)



Your message dated Wed, 21 Feb 2018 21:02:02 +0700
with message-id <d85fa0d1-5cf0-ca4b-0db8-c76e359a7508@collabora.com>
and subject line 
has caused the Debian Bug report #890984,
regarding ITP: golang-github-containerd-btrfs -- Btrfs bindings for Go
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
890984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890984
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Arnaud Rebillout <arnaud.rebillout@collabora.com>

* Package name    : golang-github-containerd-btrfs
  Version         : 0.0~git20171005.72c0a35-1
  Upstream Author : containerd
* URL             : https://github.com/containerd/btrfs
* License         : Apache-2.0
  Programming Lang: Go
  Description     : Btrfs bindings for Go

 Native Go bindings for btrfs.
 .
 Status
 .
 These are in the early stages. We will try to maintain stability, but please
 vendor if you are relying on these directly.
 .
 Contribute
 .
 This package may not cover all the use cases for btrfs. If something you need
 is missing, please don't hesitate to submit a PR.  .  Note that due to struct
 alignment issues, this isn't yet fully native.  Preferrably, this could be
 resolved, so contributions in this direction are greatly appreciated.

----

- why is this package useful/relevant?

It is a dependency of containerd.

- how do you plan to maintain it?

I plan to maintain it within the golang packaging team.

--- End Message ---
--- Begin Message ---
duplicate of #890989, my mistake

--- End Message ---

Reply to: