Bug#730508: marked as done (RFP: golang-tar-dev -- Fork of the upstream Go tar archive with PAX header support)
Your message dated Mon, 15 Apr 2019 19:40:06 +0200 (CEST)
with message-id <alpine.DEB.2.20.1904151939410.30564@jupiter.server.alteholz.net>
and subject line closing this bug
has caused the Debian Bug report #730508,
regarding RFP: golang-tar-dev -- Fork of the upstream Go tar archive with PAX header support
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.)
--
730508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730508
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Jonathan Dray <jonathan.dray@gmail.com>
* Package name : golang-tar-dev
Version : 0.0~gite5ea6bb-1
Upstream Author : The Go Authors, Dotcloud
* URL : https://github.com/dotcloud/tar
* License : BSD-3-clause
Programming Lang: Go
Description : Fork of the upstream Go tar archive with PAX header support
The Go tar lib implements access to tar archives.
It aims to cover most of the variations, including those produced by
GNU and BSD tars.
This is a fork that adds PAX header support.
A pull request was created to merge modifications upstream
@see: https://codereview.appspot.com/12561043/
.
This package contains the source.
--- End Message ---
--- Begin Message ---
- To: 730508-done@bugs.debian.org
- Subject: closing this bug
- From: Thorsten Alteholz <debian@alteholz.de>
- Date: Mon, 15 Apr 2019 19:40:06 +0200 (CEST)
- Message-id: <alpine.DEB.2.20.1904151939410.30564@jupiter.server.alteholz.net>
As mentioned by Tianon, this bug is no longer required, so I am closing it manually now.
Thorsten
--- End Message ---
Reply to: