# packages

pkgId: 3c4608c38fde5cdf07572d8a53441ecf5f9058889c8e82f0f0ea6df2732b3002
name: cjdns-tools
arch: noarch
version: 20.2
epoch: 0
release: 5.fc29
summary: Nodejs tools for cjdns
url: http://hyperboria.net/
rpm_license: GPLv3 and MIT and BSD and ISC
rpm_group: System Environment/Base
rpm_buildhost: melissa.gathman.org
rpm_sourcerpm: cjdns-20.2-5.fc29.src.rpm
location_href: cjdns-tools-20.2-5.fc29.noarch.rpm
checksum_type: sha256
description:
  Nodejs tools for cjdns. Highlights:
  peerStats          show current peer status
  cjdnslog           display cjdroute log
  cjdns-traceroute   trace route to cjdns IP
  sessionStats       show current crypto sessions


pkgId: 35dafe937f604532e0a8120408343c26bc58733283cfd5e87e78a7c4265c10c6
name: gathman-release
arch: noarch
version: 0.7
epoch: 0
release: 1.fc29
summary: Gathman Repository
rpm_license: BSD
rpm_vendor: Stuart D. Gathman <stuart@gathman.org>
rpm_group: System Environment/Base
rpm_buildhost: melissa.gathman.org
rpm_sourcerpm: gathman-release-0.7-1.fc29.src.rpm
rpm_packager: Stuart D. Gathman <stuart@gathman.org>
location_href: gathman-release-0.7-1.fc29.noarch.rpm
checksum_type: sha256
description:
  Gathman release file. This package contains yum configuration for the
  Gathman RPM Repository, as well as the public GPG keys used to sign packages.


pkgId: 166a6c377ae34b370f90591d69ccf7fac8f7697ab2e750fbe423e3a4e5f1184f
name: lbatofile
arch: noarch
version: 0.3
epoch: 0
release: 1.fc29
summary: Map LBA to file
url: https://github.com/sdgathman/lbatofile
rpm_license: GPL2+
rpm_group: Applications/System
rpm_buildhost: melissa.gathman.org
rpm_sourcerpm: lbatofile-0.3-1.fc29.src.rpm
location_href: lbatofile-0.3-1.fc29.noarch.rpm
checksum_type: sha256
description:
  When you have a bad sector on storage media, modern drives will repair the
  sector when you write to it. However, you would like to know what file is
  damaged by the missing data. In many cases, the bad sector will be in free
  space. Or the file is one that you can delete and restore from elsewhere.
  lbatofile.py will "drill down" starting from any block device and LBA within
  that block device (which is usually a whole disk), and invoke linux utilities
  to interpret the partition tables, LVM metadata, or filesystems containing the
  LBA.


