ruby-ffaker 2.20.0-1 source package in Ubuntu
Changelog
ruby-ffaker (2.20.0-1) unstable; urgency=medium
* Team upload.
* New upstream release.
* d/control (Standards-Version): Bump to 4.6.0.
* d/copyright (Copyright): Update.
* d/ruby-ffaker.docs: Add missing docs.
* d/patches/0001-Fix-TestLoremFR-tests.patch: Removed patch applied upstream.
* d/patches/0003-Test-with-github-action-ruby-3-468.patch: Ditto.
* d/patches/0002-Disable-image-test-requiring-network-access.patch: Rename to
d/patches/Disable-image-test-requiring-network-access.patch.
* d/patches/Don-t-require-lib-for-tests.patch: Add patch.
- Don't rely on lib to fix autopkgtest runs.
* d/patches/series: Remove above patch.
* d/upstream/metadata: Update URLs.
-- Daniel Leidert <email address hidden> Sat, 20 Nov 2021 12:52:35 +0100
Upload details
- Uploaded by:
- Debian Ruby Extras Maintainers
- Uploaded to:
- Sid
- Original maintainer:
- Debian Ruby Extras Maintainers
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Noble | release | universe | misc | |
| Mantic | release | universe | misc | |
| Lunar | release | universe | misc | |
| Jammy | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| ruby-ffaker_2.20.0-1.dsc | 2.0 KiB | 579090cd679f185cad383bebed6d682ed6a75400fd15ee75d11cb0a11d5d9a54 |
| ruby-ffaker_2.20.0.orig.tar.gz | 464.1 KiB | 6acdbfaf96a295061c7f44c1e473645d61f0d7c0b99c89bb1a24c3dc7820c329 |
| ruby-ffaker_2.20.0-1.debian.tar.xz | 3.8 KiB | 4e5771721c2e0a0e93845cc0c2073e94cd31d29cec4f0a04a0c04022e8c012c2 |
Available diffs
- diff from 2.13.0-3 to 2.20.0-1 (176.3 KiB)
No changes file available.
Binary packages built by this source
- ruby-ffaker: ffaker generates dummy data
ffaker is a fork of faker, and was initially written in an effort to speed up
a slow spec suite. Since those days faker has also been rewritten and the
"speed" factor is probably irrelevant now. Bear in mind, if your spec suite
is slow, chances are the generation of random data will probably not account
for much of the run time.
