golang-github-hashicorp-errwrap 1.1.0-1 source package in Ubuntu
Changelog
golang-github-hashicorp-errwrap (1.1.0-1) unstable; urgency=medium
* Team upload.
[ Debian Janitor ]
* Bump debhelper from old 11 to 12.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Apply multi-arch hints.
+ golang-github-hashicorp-errwrap-dev: Add Multi-Arch: foreign.
[ Shengjing Zhu ]
* Update uscan watch file to version 4
* New upstream version 1.1.0
* Update Section to golang
* Bump debhelper-compat to 13
* Update Standards-Version to 4.5.1 (no changes)
* Add Rules-Requires-Root
* Use /usr/share/common-licenses/MPL-2.0 in copyright
-- Shengjing Zhu <email address hidden> Sun, 31 Jan 2021 01:30:41 +0800
Upload details
- Uploaded by:
- Debian Go Packaging Team
- Uploaded to:
- Sid
- Original maintainer:
- Debian Go Packaging Team
- Architectures:
- all
- Section:
- golang
- Urgency:
- Medium Urgency
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| golang-github-hashicorp-errwrap_1.1.0-1.dsc | 1.7 KiB | 9202574b09e1a86276ea6d7c31be1d4061c81cc1f6b79fa5ff5726db4a0b41bc |
| golang-github-hashicorp-errwrap_1.1.0.orig.tar.gz | 8.4 KiB | 0d73891a7a179e50a142ac8832db97b17c792d29ae205b0e6aeedde4c43d51a4 |
| golang-github-hashicorp-errwrap_1.1.0-1.debian.tar.xz | 3.0 KiB | faacd64e8aef2bb9a25ad22521a03f25f541f0e79f3fa58133bbfc25a068ef39 |
Available diffs
- diff from 1.0.0-1.1 to 1.1.0-1 (7.5 KiB)
No changes file available.
Binary packages built by this source
- golang-github-hashicorp-errwrap-dev: Errwrap is a Go (golang) library for wrapping and querying errors
errwrap is a package for Go that formalizes the pattern of wrapping errors and
checking if an error contains another error.
.
There is a common pattern in Go of taking a returned error value and then
wrapping it (such as with fmt.Errorf) before returning it. The problem with
this pattern is that you completely lose the original error structure.
.
Arguably the correct approach is that you should make a custom structure
implementing the error interface, and have the original error as a field on
that structure, such as this example. This is a good approach, but you have to
know the entire chain of possible rewrapping that happens, when you might just
care about one.
.
errwrap formalizes this pattern (it doesn't matter what approach you use above)
by giving a single interface for wrapping errors, checking if a specific error
is wrapped, and extracting that error.
.
This package contains the source.
