openSUSE:Slowroll:Build:1

https://en.opensuse.org/openSUSE:Slowroll area for building and openQA testing https://download.opensuse.org/repositories/openSUSE:/Slowroll:/Build:/1/standard/ openSUSE:Slowroll

Slowroll

https://en.opensuse.org/openSUSE:Slowroll = a derivative codestream of openSUSE:Factory that uses automated rules to limit the rate of change to the codebase Release manager: bmwiedemann https://www.zq1.de/~bernhard/linux/opensuse/slowroll/slowroll-vs-tumbleweed-updates.svg https://download.opensuse.org/update/slowroll/repo/oss/ openSUSE:Slowroll:Base:1

staging area for new Base snapshot from Tumbleweed

Before a version bump, I collect i586 and bootstrap binaries here. These are missing in released Tumbleweed snapshots, but are needed for building packages. Also binaries required for DVD builds, because product-builder cannot use those from download-on-demand (dod) https://download.opensuse.org/repositories/openSUSE:/Slowroll:/Base:/1/standard/ openSUSE:Tumbleweed

Tumbleweed

Tumbleweed is the openSUSE Rolling Release This OBS Project represents the content of the currently published snapshot. The newer repository for next publish can be found in openSUSE:Factory standard repository. https://download.opensuse.org/repositories/openSUSE:/Tumbleweed/slowroll/ dyff

Diff tool for YAML files, and sometimes JSON

A diff tool for YAML files, and sometimes JSON. dyff is inspired by the way the old BOSH v1 deployment output reported changes from one version to another by only showing the parts of a YAML file that change. Each difference is referenced by its location in the YAML document by using either the Spruce dot-style syntax (some.path.in.the.file) or go-patch path syntax (/some/name=path/in/the/id=file). The output report aims to be as compact as possible to give a clear and simple overview of the change. Similar to the standard diff tool, it follows the principle of describing the change by going from the from input file to the target to input file. Input files can be local files (filesystem path), remote files (URI), or the standard input stream (using -). All orders of keys in hashes are preserved during processing and output to the terminal, most notably in the sub-commands to convert YAML to JSON and vice versa.