golang-gopkg-yaml.v3 3.0.1-2 source package in Ubuntu

Changelog

golang-gopkg-yaml.v3 (3.0.1-2) unstable; urgency=medium

  [ Debian Janitor ]
  * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse.

 -- Jelmer Vernooij <email address hidden>  Mon, 17 Oct 2022 15:25:10 +0100

Upload details

Uploaded by:
Debian Go Packaging Team
Uploaded to:
Sid
Original maintainer:
Debian Go Packaging Team
Architectures:
all
Section:
golang
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Lunar: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
golang-gopkg-yaml.v3_3.0.1-2.dsc 2.1 KiB e72ea9f3ad33da3aecd096cdb465183a8c6e639b8e8d73decd4f97de29b0f9b2
golang-gopkg-yaml.v3_3.0.1.orig.tar.gz 89.0 KiB cf05411540d3e6ef8f1fd88434b34f94cedaceb540329031d80e23b74540c4e5
golang-gopkg-yaml.v3_3.0.1-2.debian.tar.xz 4.4 KiB e2dc909f20313bc08f3b1f89d9ad2a98dcc73c545ace0f9d33cf523cdf3849ed

Available diffs

No changes file available.

Binary packages built by this source

golang-gopkg-yaml.v3-dev: YAML support for the Go language

 The yaml package enables Go programs to very comfortably encode and decode
 YAML values. It was developed within Canonical as part of the juju project,
 and is based on a pure Go port of the well-known libyaml C library to parse
 and generate YAML data quickly and reliably.
 .
 The yaml package supports most of YAML 1.2, but preserves some behavior from
 1.1 for backwards compatibility.
 .
 Specifically, as of v3 of the yaml package:
 .
  * YAML 1.1 bools (yes/no, on/off) are supported as long as they are being
    decoded into a typed bool value. Otherwise they behave as a string.
    Booleans in YAML 1.2 are true/false only.
  * Octals encode and decode as 0777 per YAML 1.1, rather than 0o777 as
    specified in YAML 1.2, because most parsers still use the old format.
    Octals in the 0o777 format are supported though, so new files work.
  * Does not support base-60 floats. These are gone from YAML 1.2, and were
    actually never supported by this package as it's clearly a poor choice.
 .
 and offers backwards compatibility with YAML 1.1 in some cases. 1.2,
 including support for anchors, tags, map merging, etc. Multi-document
 unmarshalling is not yet implemented, and base-60 floats from YAML 1.1 are
 purposefully not supported since they're a poor design and are gone in YAML
 1.2.