ruby-yajl 1.2.0-3build3 source package in Ubuntu

Changelog

ruby-yajl (1.2.0-3build3) xenial; urgency=medium

  * No-change rebuild to add ruby2.3 support.

 -- Matthias Klose <email address hidden>  Sun, 13 Mar 2016 12:37:10 +0000

Upload details

Uploaded by:
Matthias Klose
Uploaded to:
Xenial
Original maintainer:
Debian Ruby Extras Maintainers
Architectures:
any
Section:
ruby
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
ruby-yajl_1.2.0.orig.tar.gz 559.2 KiB 7fb3bc618ba191b3b7d476dcb9bac74c9a97e7d93cbdcf76471f1d28e9be5abc
ruby-yajl_1.2.0-3build3.debian.tar.xz 5.1 KiB 841e42a679942fc29fdfeb397d1b0b436ace18a1ceb5f84f7c4428631fbe00eb
ruby-yajl_1.2.0-3build3.dsc 2.1 KiB 3fe2be186cc65f4f09bcc79e8ba15db039408ecad72c4d488f00172ce32e7684

Available diffs

View changes file

Binary packages built by this source

ruby-yajl: Ruby interface to Yajl, a JSON stream-based parser library

 Supported features include,
 .
 JSON parsing and encoding directly to and from an IO stream
 (file, socket, etc) or String. Compressed stream parsing and
 encoding supported for Bzip2, Gzip and Deflate.
 .
 Parse and encode *multiple* JSON objects to and from streams or strings
 continuously.
 .
 JSON gem compatibility API - allows yajl-ruby to be used as a drop-in
 replacement for the JSON gem
 .
 Basic HTTP client (only GET requests supported for now) which parses JSON
 directly off the response body *as it's being received*

ruby-yajl-dbgsym: debug symbols for package ruby-yajl

 Supported features include,
 .
 JSON parsing and encoding directly to and from an IO stream
 (file, socket, etc) or String. Compressed stream parsing and
 encoding supported for Bzip2, Gzip and Deflate.
 .
 Parse and encode *multiple* JSON objects to and from streams or strings
 continuously.
 .
 JSON gem compatibility API - allows yajl-ruby to be used as a drop-in
 replacement for the JSON gem
 .
 Basic HTTP client (only GET requests supported for now) which parses JSON
 directly off the response body *as it's being received*