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

Changelog

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

  [ Debian Janitor ]
  * Remove constraints unnecessary since buster (oldstable)

 -- Jelmer Vernooij <email address hidden>  Wed, 16 Nov 2022 09:58:06 +0000

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
Mantic release universe misc
Lunar release universe misc

Builds

Lunar: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
golang-gopkg-yaml.v3_3.0.1-3.dsc 2.1 KiB ad42942a8bbe2908e33cc4740a3b68207d39d9a5af141908d00a2df3b7106cae
golang-gopkg-yaml.v3_3.0.1.orig.tar.gz 89.0 KiB cf05411540d3e6ef8f1fd88434b34f94cedaceb540329031d80e23b74540c4e5
golang-gopkg-yaml.v3_3.0.1-3.debian.tar.xz 4.4 KiB 18446874819470a623a6a9c34c6efc129640e34a25dce355a72ad9e3d45dbc7d

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.