# packages

pkgId: c484afacc4651d32211e028d8edeb16d7bdba98c2c0d6df17cbbdde68b13e5d4
name: WalletWasabi
arch: src
version: 1.1.12.2
epoch: 0
release: 17.fc33
summary: An open-source, non-custodial, privacy-focused Bitcoin wallet
url: https://github.com/zkSNACKs/WalletWasabi
rpm_license: MIT
rpm_group: Applications/Financial
rpm_buildhost: qubes-chroot
location_href: packages/WalletWasabi-1.1.12.2-17.fc33.src.rpm
checksum_type: sha256
description:
  Wasabi is an open-source, non-custodial, privacy-focused Bitcoin wallet for Desktop, that implements trustless CoinJoin.


pkgId: 12670bce36b6f2c9eb53297e3c73d03af169772dbffa2506bcd6f037f24f936d
name: airsonic
arch: noarch
version: 10.6.2
epoch: 0
release: 24.fc33
summary: A music media server
url: https://github.com/airsonic/airsonic
rpm_license: GPLv3
rpm_group: Applications/Multimedia
rpm_buildhost: qubes-chroot
rpm_sourcerpm: airsonic-10.6.2-24.fc33.src.rpm
location_href: packages/airsonic-10.6.2-24.fc33.noarch.rpm
checksum_type: sha256
description:
  Airsonic is a multimedia server that transcodes media and plays it back in a browser or in a mobile device.


pkgId: 1b0b319a03567f0dacf624489cd870dc99c569e9092ffcbc1b8e80938902bd48
name: airsonic-advanced
arch: noarch
version: 11.0.0.20210210200712
epoch: 1
release: 12.fc33
summary: A music media server
url: https://github.com/airsonic-advanced/airsonic-advanced
rpm_license: GPLv3
rpm_group: Applications/Multimedia
rpm_buildhost: qubes-chroot
rpm_sourcerpm: airsonic-advanced-11.0.0.20210210200712-12.fc33.src.rpm
location_href: packages/airsonic-advanced-11.0.0.20210210200712-12.fc33.noarch.rpm
checksum_type: sha256
description:
  Airsonic is a multimedia server that transcodes media and plays it back in a browser or in a mobile device.
  Airsonic Advanced is the next generation of Airsonic.


pkgId: ab68d77d5d5154dee4da9ed36a766db7c000ed0fd0fc2ed68da385e793d6835a
name: alertmanager
arch: src
version: 0.21.0
epoch: 0
release: 3.fc33
summary: Prometheus Alertmanager.
url: https://github.com/prometheus/alertmanager
rpm_license: ASL 2.0
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
location_href: packages/alertmanager-0.21.0-3.fc33.src.rpm
checksum_type: sha256
description:
  The Alertmanager handles alerts sent by client applications such as the
  Prometheus server. It takes care of deduplicating, grouping, and routing them to
  the correct receiver integration such as email, PagerDuty, or OpsGenie. It also
  takes care of silencing and inhibition of alerts.


pkgId: f43b678d5e938bb0fef75ec95d5a876382457a2f4584ff62c20d4c1cff853a68
name: alertmanager_matrix
arch: src
version: 0.0.10
epoch: 0
release: 13.fc33
url: https://github.com/Rudd-O/alertmanager_matrix
rpm_license: EUPLv1.2
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot.local
location_href: packages/alertmanager_matrix-0.0.10-13.fc33.src.rpm
checksum_type: sha256
summary:
  Service for sending alerts from the Alertmanager webhook to a Matrix room and managing Alertmanager.

description:
  Service for sending alerts from the Alertmanager webhook to a Matrix room
  and managing Alertmanager.

  Please see README.md enclosed in the package for instructions on how to use
  this software.


pkgId: 51d811de6a7692ce35c0a3490079a269647b05712dc03ea75e6cf46924986371
name: cec-dbus-bridge
arch: src
version: 0.0.6
epoch: 0
release: 10.fc33
summary: A daemon to expose CEC functionality on the D-Bus session bus
url: https://github.com/Rudd-O/cec-dbus-bridge
rpm_license: GPL
rpm_group: System administration tools
rpm_buildhost: jenkins-chroot
location_href: packages/cec-dbus-bridge-0.0.6-10.fc33.src.rpm
checksum_type: sha256
description:
  cec-dbus-bridge allows you to control devices connected via HDMI through
  the CEC functionality exposed over D-Bus by it.


pkgId: 96af50959e66bdee05b24eaaa380a009d4964dced3116703e2ef0a1a777e4f96
name: diod
arch: src
version: 1.0.24.1
epoch: 0
release: 1.fc33
summary: I/O forwarding server for 9P.
url: http://github.com/chaos/diod
rpm_license: GPL
rpm_group: Applications/System
rpm_buildhost: jenkins-chroot.local
location_href: packages/diod-1.0.24.1-1.fc33.src.rpm
checksum_type: sha256
description:
  diod is a 9P server used in combination with the kernel v9fs file
  system for I/O forwarding on Linux clusters.


pkgId: cc302a3abaf7a43b775b327b83ead9e5368780067b8985b71620b620170e633c
name: diod-debuginfo
arch: x86_64
version: 1.0.24.1
epoch: 0
release: 1.fc33
summary: Debug information for package diod
url: http://github.com/chaos/diod
rpm_license: GPL
rpm_group: Development/Debug
rpm_buildhost: jenkins-chroot.local
rpm_sourcerpm: diod-1.0.24.1-1.fc33.src.rpm
location_href: packages/diod-debuginfo-1.0.24.1-1.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package diod.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 41135070220c93ca1b7921509e854050b3c2a9df18d99b92ecd69dd44773f302
name: diod-debugsource
arch: x86_64
version: 1.0.24.1
epoch: 0
release: 1.fc33
summary: Debug sources for package diod
url: http://github.com/chaos/diod
rpm_license: GPL
rpm_group: Development/Debug
rpm_buildhost: jenkins-chroot.local
rpm_sourcerpm: diod-1.0.24.1-1.fc33.src.rpm
location_href: packages/diod-debugsource-1.0.24.1-1.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug sources for package diod.
  Debug sources are useful when developing applications that use this
  package or when debugging this package.


pkgId: 577be4ac12e77900787075fb6a8b540031954a0664f6f9a45207bdff197d844b
name: diod-utils-debuginfo
arch: x86_64
version: 1.0.24.1
epoch: 0
release: 1.fc33
summary: Debug information for package diod-utils
url: http://github.com/chaos/diod
rpm_license: GPL
rpm_group: Development/Debug
rpm_buildhost: jenkins-chroot.local
rpm_sourcerpm: diod-1.0.24.1-1.fc33.src.rpm
location_href: packages/diod-utils-debuginfo-1.0.24.1-1.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package diod-utils.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: c48556ac589ed69f451ef701e339f4b69bfc6558a3ccb14a9ed063d98a985981
name: ebpf_exporter
arch: src
version: 1.2.2.4
epoch: 0
release: 19.fc33
summary: Prometheus exporter for custom eBPF metrics
url: https://github.com/Rudd-O/ebpf_exporter
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
location_href: packages/ebpf_exporter-1.2.2.4-19.fc33.src.rpm
checksum_type: sha256
description:
  Prometheus exporter for custom eBPF metrics.

  Motivation of this exporter is to allow you to write eBPF code and export
  metrics that are not otherwise accessible from the Linux kernel.

  eBPF was described by Ingo Molnár as:

      One of the more interesting features in this cycle is the ability
      to attach eBPF programs (user-defined, sandboxed bytecode executed
      by the kernel) to kprobes. This allows user-defined instrumentation
      on a live kernel image that can never crash, hang or interfere with
      the kernel negatively.

  An easy way of thinking about this exporter is bcc tools as prometheus metrics.


pkgId: 4b1aaba56395284582fa862a638af6212fa04a3fd45fc2019f20e0f84c609a2f
name: fava
arch: noarch
version: 1.16
epoch: 0
release: 12.fc33
summary: Web interface for the accounting tool Beancount.
url: https://beancount.github.io/fava/
rpm_license: MIT
rpm_vendor: Jakob Schnitzer <mail@jakobschnitzer.de>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: fava-1.16-12.fc33.src.rpm
location_href: packages/fava-1.16-12.fc33.noarch.rpm
checksum_type: sha256
description:
  .. image:: https://badges.gitter.im/beancount/fava.svg
     :alt: Join the chat at https://gitter.im/beancount/fava
     :target: https://gitter.im/beancount/fava
  .. image:: https://img.shields.io/pypi/l/fava.svg
     :target: https://pypi.python.org/pypi/fava
  .. image:: https://img.shields.io/pypi/v/fava.svg
     :target: https://pypi.python.org/pypi/fava
  .. image:: https://img.shields.io/travis/beancount/fava.svg
     :target: https://travis-ci.org/beancount/fava?branch=master

  Fava is a web interface for the double-entry bookkeeping software `Beancount
  <http://furius.ca/beancount/>`__ with a focus on features and usability.

  Check out the online `demo <https://fava.pythonanywhere.com>`__ and learn more
  about Fava on the `website <https://beancount.github.io/fava/>`__.

  The `Getting Started
  <https://beancount.github.io/fava/usage.html>`__ guide details the installation
  and how to get started with Beancount.  If you are already familiar with
  Beancount, you can get started with Fava::

      pip3 install fava
      fava ledger.beancount

  and visit the web interface at `http://localhost:5000
  <http://localhost:5000>`__.

  If you want to hack on Fava or run a development version, see the
  `Development <https://beancount.github.io/fava/development.html>`__ page on the
  website for details. Contributions are very welcome!

  .. image:: https://i.imgbox.com/rfb9I7Zw.png
      :alt: Fava Screenshot
      :width: 100%
      :align: center
      :target: https://fava.pythonanywhere.com


pkgId: e61cdc4521cf3689e99d1909a4cbdec025d9d4c097fa772fa634312baedf88d7
name: fava
arch: noarch
version: 1.20.1
epoch: 0
release: 10.fc33
summary: Web interface for the accounting tool Beancount.
url: https://beancount.github.io/fava/
rpm_license: MIT
rpm_vendor: Jakob Schnitzer <mail@jakobschnitzer.de>
rpm_group: Development/Libraries
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: fava-1.20.1-10.fc33.src.rpm
location_href: packages/fava-1.20.1-10.fc33.noarch.rpm
checksum_type: sha256
description:
  .. image:: https://badges.gitter.im/beancount/fava.svg
     :alt: Join the chat at https://gitter.im/beancount/fava
     :target: https://gitter.im/beancount/fava
  .. image:: https://img.shields.io/pypi/l/fava.svg
     :target: https://pypi.python.org/pypi/fava
  .. image:: https://img.shields.io/pypi/v/fava.svg
     :target: https://pypi.python.org/pypi/fava

  Fava is a web interface for the double-entry bookkeeping software `Beancount
  <http://furius.ca/beancount/>`__ with a focus on features and usability.

  Check out the online `demo <https://fava.pythonanywhere.com>`__ and learn more
  about Fava on the `website <https://beancount.github.io/fava/>`__.

  The `Getting Started
  <https://beancount.github.io/fava/usage.html>`__ guide details the installation
  and how to get started with Beancount.  If you are already familiar with
  Beancount, you can get started with Fava::

      pip3 install fava
      fava ledger.beancount

  and visit the web interface at `http://localhost:5000
  <http://localhost:5000>`__.

  If you want to hack on Fava or run a development version, see the
  `Development <https://beancount.github.io/fava/development.html>`__ page on the
  website for details. Contributions are very welcome!

  .. image:: https://i.imgbox.com/rfb9I7Zw.png
      :alt: Fava Screenshot
      :width: 100%
      :align: center
      :target: https://fava.pythonanywhere.com


pkgId: fccd3446d788ade243b8984b041c61f1c4fa3e3ed58636d880273052216cf722
name: git-remote-qubes
arch: noarch
version: 0.0.11
epoch: 0
release: 1.fc33
summary: Inter-VM git push and pull for Qubes OS AppVMs and StandaloneVMs
url: https://github.com/Rudd-O/git-remote-qubes
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: git-remote-qubes-0.0.11-1.fc33.src.rpm
location_href: packages/git-remote-qubes-0.0.11-1.fc33.noarch.rpm
checksum_type: sha256
description:
  This package lets you setup Git servers on your Qubes OS VMs.
  You are meant to install this package on TemplateVMs that are the templates
  for AppVMs where you want to either serve git repos from, or push/pull git
  repos from, as well as StandaloneVMs where you wish to do the same things.


pkgId: 2deea73d155fe027b50de6390c9f983b91468a9cf9c50675c57f957bdba92adc
name: git-remote-qubes-dom0
arch: noarch
version: 0.0.11
epoch: 0
release: 1.fc33
summary: Policy package for Qubes OS dom0s that arbitrates git-remote-qubes
url: https://github.com/Rudd-O/git-remote-qubes
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: git-remote-qubes-0.0.11-1.fc33.src.rpm
location_href: packages/git-remote-qubes-dom0-0.0.11-1.fc33.noarch.rpm
checksum_type: sha256
description:
  This package contains the Qubes OS execution policy for the git-remote-qubes package.
  You are meant to install this package on the dom0 of the machine where you
  have VMs that have the git-remote-qubes package installed.


pkgId: 1e72dde68a8e86992d98e0ef0b8c4250182da6904fd9f645c03dab676223004e
name: kodi-wol-starter
arch: noarch
version: 0.0.4
epoch: 0
release: 5.fc33
summary: A demo client for wol-monitor that starts Kodi when a WOL packet is received.
url: https://github.com/Rudd-O/wol-monitor
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: wol-monitor-0.0.4-5.fc33.src.rpm
location_href: packages/kodi-wol-starter-0.0.4-5.fc33.noarch.rpm
checksum_type: sha256
description:
  This is a demo client for wol-monitor that starts Kodi (if it is not running)
  when a Wake-on-LAN packet is received.  It is set to autostart in your user
  session when you log into your desktop.


pkgId: 988ec20145c9bd68ed9c35cf42e2b2a0651c67e7d7ff9ae77c584c4353d149cb
name: libnvpair3
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc33
summary: Solaris name-value library for Linux
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: System Environment/Kernel
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc33.src.rpm
location_href: packages/libnvpair3-2.0.0-0.142.38686cb9a.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package contains routines for packing and unpacking name-value
  pairs.  This functionality is used to portably transport data across
  process boundaries, between kernel and user space, and can be used
  to write self describing data structures on disk.


pkgId: 0118bc9e04fbeeb94c078254c1a98a601e8590d19cb49acf169d04173f851fc9
name: libnvpair3-debuginfo
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc33
summary: Debug information for package libnvpair3
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc33.src.rpm
location_href: packages/libnvpair3-debuginfo-2.0.0-0.142.38686cb9a.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libnvpair3.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: bff8abce960b5968507a48f4df03452368c2bc27c90a0f31c25cb0392a8af950
name: libuutil3
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc33
summary: Solaris userland utility library for Linux
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: System Environment/Kernel
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc33.src.rpm
location_href: packages/libuutil3-2.0.0-0.142.38686cb9a.fc33.x86_64.rpm
checksum_type: sha256
description:
  This library provides a variety of compatibility functions for OpenZFS:
   * libspl: The Solaris Porting Layer userland library, which provides APIs
     that make it possible to run Solaris user code in a Linux environment
     with relatively minimal modification.
   * libavl: The Adelson-Velskii Landis balanced binary tree manipulation
     library.
   * libefi: The Extensible Firmware Interface library for GUID disk
     partitioning.
   * libshare: NFS, SMB, and iSCSI service integration for ZFS.


pkgId: 64468aeb3e315c8173fc6bf62c8205d488eee17568036c4ac7c8313de1ea3998
name: libuutil3-debuginfo
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc33
summary: Debug information for package libuutil3
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc33.src.rpm
location_href: packages/libuutil3-debuginfo-2.0.0-0.142.38686cb9a.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libuutil3.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 2407844b79ade88868368760ea56098a00721fd49fac25566b271767744d0930
name: libzfs4-debuginfo
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc33
summary: Debug information for package libzfs4
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc33.src.rpm
location_href: packages/libzfs4-debuginfo-2.0.0-0.142.38686cb9a.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libzfs4.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: db347064bb3abed8a42c38cb41bfd229668b06ff7f78269c94d8b4e37d034ddc
name: libzfs4-devel
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc33
summary: Development headers
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: System Environment/Kernel
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc33.src.rpm
location_href: packages/libzfs4-devel-2.0.0-0.142.38686cb9a.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package contains the header files needed for building additional
  applications against the ZFS libraries.


pkgId: 2fbe00b57c1c7cfe54a21e03eb3b39b867a6df5b091d960aca73b6998eddfc9c
name: libzpool4-debuginfo
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc33
summary: Debug information for package libzpool4
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc33.src.rpm
location_href: packages/libzpool4-debuginfo-2.0.0-0.142.38686cb9a.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libzpool4.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: da50f11e22344d886f20384f6dc021c6497c1691f1d90a38973741b1ff75905d
name: musictoolbox
arch: noarch
version: 0.0.47
epoch: 0
release: 1.fc33
summary: A set of utilities to help you groom your music collection
url: http://github.com/Rudd-O/musictoolbox
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: musictoolbox-0.0.47-1.fc33.src.rpm
location_href: packages/musictoolbox-0.0.47-1.fc33.noarch.rpm
checksum_type: sha256
description:
  Music toolbox
  =============

  This is a small toolbox of utilities written in Python 2 that help users groom their music collection.

  What's in the box
  -----------------

  `syncplaylists` takes a number of file lists / playlists in the command line,
  and a destination directory, then synchronizes all the songs in the playlists
  to the destination directory, with optional modifications to the files and their
  names as they are copied to the destination directory.  `syncplaylists` preserves
  your music collection's directory structure.

  `syncplaylists` requires a simple INI file in your home directory (name it
  `.syncplaylists.ini`) which must say how you want things to be transcoded:
  ::

      
      [transcoding]
      mp3=copy
      m4a=copy
      ogg=copy
      flac=copy
      *=mp3
      opus=copy

  Once you've created the INI file, here's the quickstart version of how you
  actually *use* the tool:

  ```
  [user@laptop ~/Music]$ syncplaylists -vd Playlists/*.m3u /mnt/usbdrive/Music/
  ```

  That will copy all songs listed in all M3U playlists within your
  `~/Music/Playlists` folder directly into `/mnt/usbdrive/Music`, preserving
  the directory structure you have.

  Run `syncplaylists --help` or see `get_parser()` in file `synccli.py` for more
  information.

  `genplaylist` generates playlists.  Run `genplaylist --help` or see
  `get_parser()` in file `genplaylist` for more information.

  Requirements
  ------------

  This is a non-exhaustive list of requirements for most of these utilities to work:

    - python-setuptools
    - ffmpeg
    - python-mutagen
    - mp3gain
    - madplay
    - mplayer
    - mppenc
    - vorbis-tools
    - flac


pkgId: b0ca630a160320c2687183e392aac8692ccbfc5093f90302c5e58fdd1c883481
name: needs-restart
arch: noarch
version: 0.0.9
epoch: 0
release: 1.fc33
summary: A program to discover services that need restarting
url: http://github.com/Rudd-O/needs-restart
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: needs-restart-0.0.9-1.fc33.src.rpm
location_href: packages/needs-restart-0.0.9-1.fc33.noarch.rpm
checksum_type: sha256
description:
  The needs-restart program
  =========================

  This is a brief program that helps you detect which services on your
  system need to be restarted after an upgrade or redeploy of your
  software.

  Here is some example output:

      [root@machine root]# needs-restart
      * unit: (no unit)
        * PID: 1
          command: /usr/lib/systemd/systemd --switched-root --system...
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
      * unit: systemd-journald.service
        * PID: 257
          command: /usr/lib/systemd/systemd-journald
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
      * unit: systemd-udevd.service
        * PID: 281
          command: /usr/lib/systemd/systemd-udevd
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
      * unit: auditd.service
        * PID: 318
          command: /sbin/auditd -n
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
      * unit: icecast.service
        * PID: 336
          command: /usr/bin/icecast -c /etc/icecast.xml
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
          * /usr/lib64/libnss3.so changed inode from 3183 to 4236
          * /usr/lib64/libsmime3.so changed inode from 17534 to 4257
          * /usr/lib64/libssl3.so changed inode from 17535 to 4259
      * unit: systemd-logind.service
        * PID: 340
          command: /usr/lib/systemd/systemd-logind
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
      * unit: dbus.service
        * PID: 343
          command: /usr/bin/dbus-daemon --system --address=systemd: ...
          * /usr/lib64/libelf-0.163.so changed inode from 109 to 6302
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
          * /usr/lib64/libdw-0.163.so changed inode from 17296 to 17286

  Here is some example output in bare mode (`-b`):

      [root@machine root]# needs-restart -b
      systemd-journald.service
      systemd-udevd.service
      auditd.service
      icecast.service
      systemd-logind.service
      dbus.service

  Features and options
  --------------------

  The online help explains:

      [user@machine needs-restart]$ ./needs-restart --help
      usage: needs-restart [-h] [-b] [-s] [-i PATH_PREFIX]

      Show services in need of restart and processes keeping files open that were
      deleted or updated since they were opened by those processes.

      optional arguments:
        -h, --help      show this help message and exit
        -b              bare form – only list the units that need restarting
        -s              only list system units – ignore user and session ones
        -i PATH_PREFIX  ignore deleted / modified mmap()ed path(s) starting with
                        this prefix; you can specify this parameter multiple times

  Building and installing
  -----------------------

  You can run this program directly from the directory you cloned it into.

  You can also install it as an RPM.  Simply type the following command
  in the directory you cloned it into:

      python setup.py bdist_rpm

  Source RPM and installable architecture-independent RPM will appear in
  `dist/`.  You can install the architecture-independent RPM on your system now.


pkgId: 82d4ee450a3d1f59379679be3d0e0c2797a7ddc9d94f1192259b007306d5f8a8
name: node_exporter
arch: src
version: 1.0.1
epoch: 0
release: 50.fc33
summary: Prometheus exporter for machine metrics, written in Go with pluggable metric collectors.
url: https://github.com/prometheus/node_exporter
rpm_license: ASL 2.0
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
location_href: packages/node_exporter-1.0.1-50.fc33.src.rpm
checksum_type: sha256
description:
  Prometheus exporter for hardware and OS metrics exposed by *NIX kernels,
  written in Go with pluggable metric collectors.


pkgId: f086cff592c9e2e3dbc64d64955f465780a0cbedd6f36b68e18567197512c322
name: organizer
arch: noarch
version: 0.0.12
epoch: 0
release: 1.fc33
summary: A tool to assist in organizing media files
url: http://github.com/Rudd-O/organizer
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: organizer-0.0.12-1.fc33.src.rpm
location_href: packages/organizer-0.0.12-1.fc33.noarch.rpm
checksum_type: sha256
description:
  Organizer
  =========

  The organizer will help you sort your media files in folders easily
  and conveniently.

  With this program installed on your home computer, all you need to do is
  simply start your file manager, select the files to organize with a right
  click, then select Organize media files from the Open with... menu.  You
  can also run the program `organizer` from the command line, specifying
  the paths to the files you want to organize as arguments to the program.

  Optionally, if the program `takeown` is installed, the organizer will
  automatically attempt to take ownership of the files prior to organizing
  them.  This saves you an extra work step.


pkgId: 370b5becdf04b0f6856bf795f6ab2eadf1a095c7bc0391eb72194cf7a8b04ef8
name: prometheus-qubes-proxy
arch: src
version: 0.0.3.2
epoch: 0
release: 1.fc33
summary: Proxy the outside world into Prometheus exporters running on your Qubes OS VMs
url: https://github.com/Rudd-O/prometheus-qubes-proxy
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot
location_href: packages/prometheus-qubes-proxy-0.0.3.2-1.fc33.src.rpm
checksum_type: sha256
description:
  This package lets your Prometheus server contact Prometheus exporters running
  in your Qubes OS VMs.

  Install this package on your VM / VM template in order to allow the outside world
  to contact Prometheus Qubes proxy.  Then install the prometheus-qubes-proxy-service package on
  the VM / VM templates where you'll run the exporter you wish to scrape.


pkgId: 970a5e17d572b366269a7d8a981fe0270366eb7ac13a1a4097e161cc76b24f48
name: prometheus-qubes-proxy-dom0
arch: x86_64
version: 0.0.3.2
epoch: 0
release: 1.fc33
summary: This component installs the default-deny proxy policy to dom0.
url: https://github.com/Rudd-O/prometheus-qubes-proxy
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: prometheus-qubes-proxy-0.0.3.2-1.fc33.src.rpm
location_href: packages/prometheus-qubes-proxy-dom0-0.0.3.2-1.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package installs the default deny-all policy for ruddo.PrometheusProxy to
  your dom0.

  Install this package on your dom0 and then adjust the policy file to suit your
  specific requirements.


pkgId: a958e1c1c746048c20e4fe48c8e77604f444b0181de040c3aab0e2c416dcabb5
name: prometheus-qubes-proxy-service
arch: x86_64
version: 0.0.3.2
epoch: 0
release: 1.fc33
summary: This component lets the Prometheus Qubes proxy talk to a VM.
url: https://github.com/Rudd-O/prometheus-qubes-proxy
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: prometheus-qubes-proxy-0.0.3.2-1.fc33.src.rpm
location_href: packages/prometheus-qubes-proxy-service-0.0.3.2-1.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package installs the necessary component for Prometheus Qubes proxy to talk
  to a Prometheus exporter run in a VM.

  Install this package on your VM / VM template in order to allow Prometheus Qubes
  proxy to talk to any exporters running on said VM / on any VMs derived from that
  VM template.

  Requires: curl
  Requires: bash


pkgId: eccd9ad9004a5bfcb17b4e07615fd4e64b948aaabf2c9c561548c739bf18d0e6
name: prometheus2
arch: src
version: 2.22.1
epoch: 0
release: 1.fc33
summary: The Prometheus 2.x monitoring system and time series database.
url: https://prometheus.io
rpm_license: ASL 2.0
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
location_href: packages/prometheus2-2.22.1-1.fc33.src.rpm
checksum_type: sha256
description:
  Prometheus is a systems and service monitoring system. It collects metrics from
  configured targets at given intervals, evaluates rule expressions, displays the
  results, and can trigger alerts if some condition is observed to be true.


pkgId: 21202e58d7c25ab20f7c3f8eefb6cbc1b45ecee158a1297bc9375d34855ab09f
name: pypipackage-to-srpm
arch: noarch
version: 0.0.27
epoch: 0
release: 1.fc33
summary: Automate the creation of source and binary RPM packages out of source packages downloaded from PyPI
url: http://github.com/Rudd-O/pypipackage-to-srpm
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: jenkins-chroot.local
rpm_sourcerpm: pypipackage-to-srpm-0.0.27-1.fc33.src.rpm
location_href: packages/pypipackage-to-srpm-0.0.27-1.fc33.noarch.rpm
checksum_type: sha256
description:
  Formula for turning Python PyPI packages into sane RPMs.



  Your Fedora or CentOS system where you'll run this will need these
  packages installed before using this program:

  * `python-mock`


pkgId: 64120ca797394f19605bb3a866d5478ef580f07ed971dee95bd97dda24bdca21
name: python3-beancount
arch: src
version: 2.3.3
epoch: 0
release: 10.fc33
summary: Command-line Double-Entry Accounting
url: http://furius.ca/beancount
rpm_license: GNU GPLv2 only
rpm_vendor: Martin Blais <blais@furius.ca>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
location_href: packages/python3-beancount-2.3.3-10.fc33.src.rpm
checksum_type: sha256
description:
        A double-entry accounting system that uses text files as input.

        Beancount defines a simple data format or "language" that lets you define
        financial transaction records in a text file, load them in memory and
        generate and export a variety of reports, such as balance sheets or income
        statements. It also provides a client with an SQL-like query language to
        filter and aggregate financial data, and a web interface which renders
        those reports to HTML. Finally, it provides the scaffolding required to
        automate the conversion of external data into one's input file in
        Beancount syntax.


pkgId: 1bbc25e3cc5d2dfda2f4f6b93769a3b6b0cfcace71a52627e3f8fbbaf8ff81c1
name: python3-beancount-debuginfo
arch: x86_64
version: 2.3.3
epoch: 0
release: 10.fc33
summary: Debug information for package python3-beancount
url: http://furius.ca/beancount
rpm_license: GNU GPLv2 only
rpm_vendor: Martin Blais <blais@furius.ca>
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-beancount-2.3.3-10.fc33.src.rpm
location_href: packages/python3-beancount-debuginfo-2.3.3-10.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package python3-beancount.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 8f8cb476e5b999f03c4f09cb891358c2987de61b3c92e8ef3f2655a4706d0105
name: python3-beancount-debugsource
arch: x86_64
version: 2.3.3
epoch: 0
release: 10.fc33
summary: Debug sources for package python3-beancount
url: http://furius.ca/beancount
rpm_license: GNU GPLv2 only
rpm_vendor: Martin Blais <blais@furius.ca>
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-beancount-2.3.3-10.fc33.src.rpm
location_href: packages/python3-beancount-debugsource-2.3.3-10.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug sources for package python3-beancount.
  Debug sources are useful when developing applications that use this
  package or when debugging this package.


pkgId: 82eb227c91a08e2f16678cbe91e7aee5438de10ab14b3a745404f66e8cc6c119
name: python3-beanprice
arch: noarch
version: 1.2.0
epoch: 0
release: 8.fc33
summary: Price quotes fetcher for Beancount
url: http://github.com/beancount/beanprice
rpm_license: GNU GPLv2 only
rpm_vendor: Martin Blais <blais@furius.ca>
rpm_group: Development/Libraries
rpm_buildhost: jenkins-chroot.local
rpm_sourcerpm: python3-beanprice-1.2.0-8.fc33.src.rpm
location_href: packages/python3-beanprice-1.2.0-8.fc33.noarch.rpm
checksum_type: sha256
description:
        A script to fetch market data prices from various sources on the internet
        and render them for plain text accounting price syntax (and Beancount).


pkgId: 0f5d5c8cf5a03f4f3c89823e94c33c14a48d8906e28096c91a9e01fb2a72674c
name: python3-yahoo-finance
arch: noarch
version: 1.4.0
epoch: 0
release: 11.fc33
summary: Python module to get stock data from Yahoo! Finance
url: https://github.com/lukaszbanasiak/yahoo-finance
rpm_license: MIT
rpm_vendor: Lukasz Banasiak <lukasz@banasiak.me>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-yahoo-finance-1.4.0-11.fc33.src.rpm
location_href: packages/python3-yahoo-finance-1.4.0-11.fc33.noarch.rpm
checksum_type: sha256
description:
  =============
  yahoo-finance
  =============

  Python module to get stock data from Yahoo! Finance

  .. image:: https://travis-ci.org/lukaszbanasiak/yahoo-finance.svg?branch=master
      :target: https://travis-ci.org/lukaszbanasiak/yahoo-finance

  Yahoo! Finance backend is http://datatables.org/. If this service is down or
  has network problems you will receive errors from group YQL*,
  eg. ``YQLQueryError``.

  You can monitor this service via https://www.datatables.org/healthchecker/

  More details https://github.com/lukaszbanasiak/yahoo-finance/issues/44

  Install
  -------

  From PyPI with pip:

  .. code:: bash

      $ pip install yahoo-finance

  From development repo (requires git)

  .. code:: bash

      $ git clone git://github.com/lukaszbanasiak/yahoo-finance.git
      $ cd yahoo-finance
      $ python setup.py install

  Usage examples
  --------------

  Get shares data
  ^^^^^^^^^^^^^^^

  Example: Yahoo! Inc. (``YHOO``)

  .. code:: python

      >>> from yahoo_finance import Share
      >>> yahoo = Share('YHOO')
      >>> print yahoo.get_open()
      '36.60'
      >>> print yahoo.get_price()
      '36.84'
      >>> print yahoo.get_trade_datetime()
      '2014-02-05 20:50:00 UTC+0000'

  Refresh data from market

  .. code:: python

      >>> yahoo.refresh()
      >>> print yahoo.get_price()
      '36.87'
      >>> print yahoo.get_trade_datetime()
      '2014-02-05 21:00:00 UTC+0000'

  Historical data

  .. code:: python

      >>> print yahoo.get_historical('2014-04-25', '2014-04-29')
      [{u'Volume': u'28720000', u'Symbol': u'YHOO', u'Adj_Close': u'35.83', u'High': u'35.89', u'Low': u'34.12', u'Date': u'2014-04-29', u'Close': u'35.83', u'Open': u'34.37'}, {u'Volume': u'30422000', u'Symbol': u'YHOO', u'Adj_Close': u'33.99', u'High': u'35.00', u'Low': u'33.65', u'Date': u'2014-04-28', u'Close': u'33.99', u'Open': u'34.67'}, {u'Volume': u'19391100', u'Symbol': u'YHOO', u'Adj_Close': u'34.48', u'High': u'35.10', u'Low': u'34.29', u'Date': u'2014-04-25', u'Close': u'34.48', u'Open': u'35.03'}]

  More readable output :)

  .. code:: python

      >>> from pprint import pprint
      >>> pprint(yahoo.get_historical('2014-04-25', '2014-04-29'))
      [{u'Adj_Close': u'35.83',
        u'Close': u'35.83',
        u'Date': u'2014-04-29',
        u'High': u'35.89',
        u'Low': u'34.12',
        u'Open': u'34.37',
        u'Symbol': u'YHOO',
        u'Volume': u'28720000'},
       {u'Adj_Close': u'33.99',
        u'Close': u'33.99',
        u'Date': u'2014-04-28',
        u'High': u'35.00',
        u'Low': u'33.65',
        u'Open': u'34.67',
        u'Symbol': u'YHOO',
        u'Volume': u'30422000'},
       {u'Adj_Close': u'34.48',
        u'Close': u'34.48',
        u'Date': u'2014-04-25',
        u'High': u'35.10',
        u'Low': u'34.29',
        u'Open': u'35.03',
        u'Symbol': u'YHOO',
        u'Volume': u'19391100'}]

  Available methods

  - ``get_price()``
  - ``get_change()``
  - ``get_percent_change()``
  - ``get_volume()``
  - ``get_prev_close()``
  - ``get_open()``
  - ``get_avg_daily_volume()``
  - ``get_stock_exchange()``
  - ``get_market_cap()``
  - ``get_book_value()``
  - ``get_ebitda()``
  - ``get_dividend_share()``
  - ``get_dividend_yield()``
  - ``get_earnings_share()``
  - ``get_days_high()``
  - ``get_days_low()``
  - ``get_year_high()``
  - ``get_year_low()``
  - ``get_50day_moving_avg()``
  - ``get_200day_moving_avg()``
  - ``get_price_earnings_ratio()``
  - ``get_price_earnings_growth_ratio()``
  - ``get_price_sales()``
  - ``get_price_book()``
  - ``get_short_ratio()``
  - ``get_trade_datetime()``
  - ``get_historical(start_date, end_date)``
  - ``get_info()``
  - ``get_name()``
  - ``refresh()``
  - ``get_percent_change_from_year_high()``
  - ``get_percent_change_from_year_low()``
  - ``get_change_from_year_low()``
  - ``get_change_from_year_high()``
  - ``get_percent_change_from_200_day_moving_average()``
  - ``get_change_from_200_day_moving_average()``
  - ``get_percent_change_from_50_day_moving_average()``
  - ``get_change_from_50_day_moving_average()``
  - ``get_EPS_estimate_next_quarter()``
  - ``get_EPS_estimate_next_year()``
  - ``get_ex_dividend_date()``
  - ``get_EPS_estimate_current_year()``
  - ``get_price_EPS_estimate_next_year()``
  - ``get_price_EPS_estimate_current_year()``
  - ``get_one_yr_target_price()``
  - ``get_change_percent_change()``
  - ``get_dividend_pay_date()``
  - ``get_currency()``
  - ``get_last_trade_with_time()``
  - ``get_days_range()``
  - ``get_year_range()``



  Get currency data
  ^^^^^^^^^^^^^^^^^

  Example: EUR/PLN (``EURPLN=X``)

  .. code:: python

      >>> from yahoo_finance import Currency
      >>> eur_pln = Currency('EURPLN')
      >>> print eur_pln.get_bid()
      '4.2007'
      >>> print eur_pln.get_ask()
      '4.2091'
      >>> print eur_pln.get_rate()
      '4.2049'
      >>> print eur_pln.get_trade_datetime()
      '2014-03-05 11:23:00 UTC+0000'

  Refresh data from market

  .. code:: python

      >>> eur_pln.refresh()
      >>> print eur_pln.get_rate()
      '4.2052'
      >>> print eur_pln.get_trade_datetime()
      '2014-03-05 11:27:00 UTC+0000'

  Avalible methods

  - ``get_bid()``
  - ``get_ask()``
  - ``get_rate()``
  - ``get_trade_datetime()``
  - ``refresh()``

  Requirements
  ------------

  See ``requirements.txt``


pkgId: c531566c927945f983b8e9fbbc2a58322912319ed63f3d98bb9b1f4fb6184bb8
name: qubes-arbitrary-network-topology
arch: noarch
version: 0.0.19
epoch: 0
release: 1.fc33
summary: Turn your Qubes OS into an arbitrary network topology host
url: https://github.com/Rudd-O/qubes-arbitrary-network-topology
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: qubes-arbitrary-network-topology-0.0.19-1.fc33.src.rpm
location_href: packages/qubes-arbitrary-network-topology-0.0.19-1.fc33.noarch.rpm
checksum_type: sha256
description:
  This package lets you create arbitrary network topologies in your
  Qubes OS system.  Install this in the TemplateVM of your AppVMs
  that will participate of the network topology.  Then install the
  companion qubes-core-admin-addon-arbitrary-network-topology package
  in your dom0.

  Please see README.md enclosed in the package for instructions on how to use
  this software.


pkgId: ca3c532e83dfcd75dd10005261d6fcc4e9df828a34c0b9a3bc8cfb93bed4babc
name: qubes-core-admin-addon-arbitrary-network-topology
arch: noarch
version: 0.0.19
epoch: 0
release: 1.fc33
summary: dom0 administrative extension for Qubes arbitrary network topology
url: https://github.com/Rudd-O/qubes-arbitrary-network-topology
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: qubes-arbitrary-network-topology-0.0.19-1.fc33.src.rpm
location_href: packages/qubes-core-admin-addon-arbitrary-network-topology-0.0.19-1.fc33.noarch.rpm
checksum_type: sha256
description:
  This package lets you create arbitrary network topologies in your
  Qubes OS system.  Install this in your dom0.  Then install the
  companion qubes-arbitrary-network-topology package in the TemplateVM
  of your AppVMs that will participate of the network topology.

  Please see README.md enclosed in the package for instructions on how to use
  this software.


pkgId: 9d21706967c16a8b2c5ed07a4adb98c8bb7613bd0f0193f2774c60416cc38ddd
name: qubes-core-admin-addon-network-server
arch: noarch
version: 0.0.13
epoch: 0
release: 22.fc33
summary: dom0 administrative extension for Qubes network server
url: https://github.com/Rudd-O/qubes-network-server
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: qubes-network-server-0.0.13-22.fc33.src.rpm
location_href: packages/qubes-core-admin-addon-network-server-0.0.13-22.fc33.noarch.rpm
checksum_type: sha256
description:
  This package lets you turn your Qubes OS into a network server.  Install this
  in your dom0.  Then install the companion qubes-network-server package in the
  TemplateVM of your NetVM.

  Please see README.md enclosed in the package for instructions on how to use
  this software.


pkgId: 62ae38f283b008a3840b07d465fb9a2725a6d28d28f0dbfbe2ee9365f089764e
name: qubes-network-server
arch: noarch
version: 0.0.13
epoch: 0
release: 22.fc33
summary: Turn your Qubes OS into a network server
url: https://github.com/Rudd-O/qubes-network-server
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: qubes-network-server-0.0.13-22.fc33.src.rpm
location_href: packages/qubes-network-server-0.0.13-22.fc33.noarch.rpm
checksum_type: sha256
description:
  This package lets you turn your Qubes OS into a network server.  Install this
  in the TemplateVM of your NetVM.  Then install the companion
  qubes-core-admin-addon-network-server package in your dom0.

  Please see README.md enclosed in the package for instructions on how to use
  this software.


pkgId: c44bafa9d18cda8b866155a8b5f9137b77744678e32a2ec071e0216d8fc2eb72
name: qubes-pass
arch: noarch
version: 0.0.21
epoch: 0
release: 18.fc33
summary: Inter-VM pass password management for Qubes OS AppVMs and StandaloneVMs
url: https://github.com/Rudd-O/qubes-pass
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: qubes-pass-0.0.21-18.fc33.src.rpm
location_href: packages/qubes-pass-0.0.21-18.fc33.noarch.rpm
checksum_type: sha256
description:
  This package lets you setup a safe password management VM and then
  manage the password store remotely from other VMs.  You are meant to
  install this package on the VM or template where you want to access
  and manage your password store.


pkgId: 28c1d75f1735d35fe7479f3e0e7f4a6bae674d8fe1ec75cb83dabee2c8d1577b
name: qubes-pass-dom0
arch: noarch
version: 0.0.21
epoch: 0
release: 18.fc33
summary: Policy package for Qubes OS dom0s that arbitrates qubes-pass
url: https://github.com/Rudd-O/qubes-pass
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: qubes-pass-0.0.21-18.fc33.src.rpm
location_href: packages/qubes-pass-dom0-0.0.21-18.fc33.noarch.rpm
checksum_type: sha256
description:
  This package contains the Qubes OS execution policy for the qubes-pass package.
  You are meant to install this package on the dom0 of the machine where you
  have VMs that have the qubes-pass package installed.


pkgId: d7abf278096d25b4169180d383bd5b64714130e6e90267deac859a44cec6683f
name: qubes-pass-service
arch: noarch
version: 0.0.21
epoch: 0
release: 18.fc33
summary: Service package for Qubes OS dom0s that services qubes-pass
url: https://github.com/Rudd-O/qubes-pass
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: qubes-pass-0.0.21-18.fc33.src.rpm
location_href: packages/qubes-pass-service-0.0.21-18.fc33.noarch.rpm
checksum_type: sha256
description:
  This package lets you serve a safe password store to other VMs.
  You are meant to install this package on the VM or template where
  you want to keep your password store safe.


pkgId: 96e97932a56eab27935e656330a48d64eed5c7da33c1f7acdde3b500abcf604a
name: run-in-gui
arch: noarch
version: 0.0.9
epoch: 0
release: 1.fc33
summary: Tools to run (possibly graphical) programs in logged-in user sessions on modern Linux distributions
url: http://github.com/Rudd-O/run-in-gui
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: run-in-gui-0.0.9-1.fc33.src.rpm
location_href: packages/run-in-gui-0.0.9-1.fc33.noarch.rpm
checksum_type: sha256
description:
  Run in GUI (run-in-gui)
  ============================

  | Donate to support this free software |
  |:------------------------------------:|
  | <img width="164" height="164" title="" alt="" src="doc/bitcoin.png" /> |
  | [1DmVQkuY1zjP6ZiPi1QJgSowHtR8afBDMS](bitcoin:1DmVQkuY1zjP6ZiPi1QJgSowHtR8afBDMS) |

  This project contains two programs that assist you in executing programs
  in a separate desktop session (defined by the environment variables of any
  program executing in that session), and then switching to the session in
  real-time as the program executes.  It's useful to start GUI programs from
  cron that need a graphical display and/or audio access.

  Why is this necessary?
  ----------------------

  Lots of people ask me why this is useful, or some other variant of the same
  question, such as "Can't I just `DISPLAY=:0` in my crontab?"

  Well, because of the way that Linux has evolved, nowadays it's very hard to
  get certain computer programs to do things that were trivial in the past.
  Lots of GUI programs now depend on a wide array of session daemons and
  other services, such as:

  * X11 authentication,
  * D-Bus,
  * KWallet,
  * GnuPG agents,
  * SSH agents,
  * KIO services,
  * PulseAudio.

  These services are normally set up properly at the start of (and solely
  in the context of) your GUI session, but entirely unavailable for use in
  crontabs and other non-GUI shells, nominally disassociated with your
  desktop session.

  For example: getting your music player to play a list of songs to wake you
  up -- unless you're running the program straight from a terminal in your
  desktop session's GUI, it won't actually work; either the program just
  won't run, or the audio will be corked.

  How this works
  --------------

  So what we do in `run-in-gui` is simple: ''we cheat'' by stealing the
  necessary information from other programs running in your desktop session,
  and using it to recreate an environment in which we run your program.

  Caveat: of course, this program ''still'' requires you to be logged in. If
  your session isn't active, `run-in-gui` will take the liberty to switch to
  your inactive session, activating -- but, if locked, not unlocking -- it,
  and then running your program.

  Tools included in this set
  --------------------------

  This package contains several tools:

  1. `run-in-env-of`: a tool that runs the command of your choice in the
      environment of the PID of your choice.  If run as root, it can
     `setuid()` to the user and group of that PID.
  2. `run-in-gui`: a tool that sorts out a desktop session you're running
     then uses run-in-env-of to execute the command on your choice under
     that desktop session.  Prior to the execution of that program, it
     switches to the selected desktop session, to enable hardware access
     to devices that would otherwise be blocked (e.g. audio).

  What you need to have before using this package
  -----------------------------------------------

  * Python 2.7 on your local machine
  * `loginctl` fully operational
  * `/proc` mounted

  Installation
  ------------

  You will need to install this package on your local machine.

  You can install this package directly from PyPI using pip::

      pip install run-in-gui

  If you are on an RPM-based distribution, build an RPM from the source package
  and install the resulting RPM::

      python setup.py bdist_rpm

  Otherwise, just use the standard Python installation system::

      python setup.py install

  You can also run it directly from the unpacked source directory::

      export PYTHONPATH="$PWD"/src
      ./<program> <parameters>

  Usage
  -----

  Say, for example, you want to run Amarok from a crontab, but you want Amarok
  to start on your logged-in desktop session.  No problem: you can stick this
  into your crontab:

      20 4 * * * /usr/local/run-in-gui/bin/run-in-gui amarok -p Toke\ up.m3u

  As you can see, at exactly 4:20 AM, Amarok will be executed in your desktop
  session, and will start playing the playlist `Toke up.m3u` in your home
  directory.

  You can also do the exact same thing from an `at` job:

      echo /path/to/run-in-gui amarok -p Matanga.m3u | at 5:45

  If, for some reason, the program won't start, check your mail folder in
  `/var/mail/$USERNAME`, where cron traditionally deposits crontab output.


pkgId: 8021afbd6d317191e254deaf4b4ce8c8ab810ed8958d5ebf3a5d9809d7b0716d
name: seedboxtools
arch: noarch
version: 1.4.10
epoch: 0
release: 1.fc33
summary: A tool to automate downloading finished torrents from a seedbox
url: http://github.com/Rudd-O/seedboxtools
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: seedboxtools-1.4.10-1.fc33.src.rpm
location_href: packages/seedboxtools-1.4.10-1.fc33.noarch.rpm
checksum_type: sha256
description:
  Seedbox tools (seedboxtools)
  ============================

  | Donate to support this free software |
  |:------------------------------------:|
  | <img width="164" height="164" title="" alt="" src="doc/bitcoin.png" /> |
  | [12cXnYY3wabbPmLpS7ZgACh4mBawrXdndk](bitcoin:12cXnYY3wabbPmLpS7ZgACh4mBawrXdndk) |

  The seedbox tools will help you download all those Linux ISOs that you
  downloaded on your remote seedbox (whether it's a Transmission Web, or
  TorrentFlux-b4rt, or a PulsedMedia seedbox) 100% automatically, without any
  manual intervention on your part.

  With this program installed on your home computer, all you need to do is
  simply start a torrent in your seedbox, from anywhere you are; then, when
  you get back home, all your downloads will be fully downloaded at home,
  ready to use and enjoy.

  Tools included in this set
  --------------------------

  This package contains several tools:

      1. leechtorrents: a tool that leeches finished downloads from a torrent
         seedbox to your local computer.
      2. configleecher: a configuration wizard to set up the clients to work
         properly against your seedbox.
      3. uploadtorrents: a tool that lets you queue up a torrent or magnet link
         for download on your seedbox.

  What you need to have before using this package
  -----------------------------------------------

      - Python 2.7 on your local machine
      - Python iniparse installed there
      - Python requests installed there, version 0.11.1 or higher (with SSL support)
      - a seedbox running TorrentFlux-b4rt or Transmission Web + API, or
        a PulsedMedia ruTorrent seedbox from PulsedMedia.com
      - an SSH server on your seedbox
      - an SSH client on your local machine
      - a public key-authenticated user account in the seedbox, so that your user
        can log in without passwords and can read the torrents and downloads
        directories in the seedbox
      - rsync installed on both machines
      - if you are using TorrentFlux-b4rt on your seedbox:
          * the command torrentinfo-console from the BitTorrent package, installed
            on the seedbox
          * the command fluxcli installed and operational on the seedbox
      - if you are using Transmission on your seedbox:
          * the command transmission-remote from the Transmission package,
            installed on your local machine
          * the API server port open so that transmission-remote can query it
      - if you are using a PulsedMedia seedbox, you don't need to do anything

  Installation
  ------------

  You will need to install this package on your local machine.

  You can install this package directly from PyPI using pip::

      pip install seedboxtools

  If you are on an RPM-based distribution, build an RPM from the source package
  and install the resulting RPM::

      python setup.py bdist_rpm

  Otherwise, just use the standard Python installation system::

      python setup.py install

  You can also run it directly from the unpacked source directory::

      export PYTHONPATH=src
      bin/leechtorrents --help

  Configuration
  -------------

  The tools require some configuration after installation.  There is a nifty
  configuration wizard that will set the configuration file up.  Run it and
  answer a few questions::

      configleecher

  The script will ask you for the necessary configuration values before you can
  run the tools here.  You should run this wizard on the machine where you'll
  be running `leechtorrents` (see below).

  Note: Both TorrentFlux and Transmission protect their download and torrent
  directories using permissions.  You should become part of the UNIX group
  they use to protect those directories, and change the permissions
  accordingly so you have at least read and list permissions (rx).

  Downloading finished torrents with the leecher tool
  ---------------------------------------------------

  The leecher tool will contact your seedbox and ask for a listing of finished
  torrents, then download them locally to the directory you chose during
  configuration.  There are various ways to run the script:

  * manually on a terminal window
  * with cron
  * in a systemd unit file as a service

  In all cases, the leecher tool will figure out finished torrents, download
  them to the download folder you configured during the `configleecher` stage,
  then create a file named `.<downloaded file>.done` within the download folder,
  to indicate that the torrent has finished downloading.  This marker helps the
  leecher tool remember which torrents were fully downloaded, so that it doesn't
  attempt to download them yet again.

  Manually
  ________

  In your terminal program of choice, just run the command::

      leechtorrents

  There are various options you can supply to the program to change its
  behavior, such as enabling periodic checks and logging to a file. Run
  `leechtorrents -h` to see the options.

  With cron
  ~~~~~~~~~

  Put this in your crontab to run it every minute::

      * * * * * leechtorrents -Dql

  `leechtorrents` will daemonize itself, write to its default log file (which
  you could change with another command line option), and be quiet if no work
  needs to be done.  Locking prevents multiple `leechtorrents` processes from
  running simultaneously.

  With systemd
  ~~~~~~~~~~~~

  Create a unit file::

      
      

      [Unit]
      Description=Torrentleecher
      After=network.target

      [Service]
      Type=simple
      ExecStart=/usr/bin/leechtorrents -g .torrentleecher.log -ql -t 30
      User=<YOUR_USERNAME_GOES_HERE>
      Restart=always

      [Install]
      WantedBy=network.target

  Then run as root::

      systemctl daemon-reload
      systemctl enable leechtorrents.service
      systemctl start leechtorrents.service

  Removing completed torrents once they have been fully downloaded
  ----------------------------------------------------------------

  The leecher tool has the ability to remove completed downloads that aren't
  seeding from your seedbox.  Just pass the command line option `-r` to the
  leecher tool `leechtorrents`, and it will automatically remove from the
  seedbox each torrent it successfully downloads, so long as the torrent
  is not seeding anymore.  This feature helps conserve disk space in your
  seedbox.  Note that, once a torrent has been removed from the seedbox,
  its corresponding `.<downloaded file>.done` file on the download folder
  will be eliminated, to clear up clutter in the download folder.

  Example::

      leechtorrents -r

  Running a program after a torrent is finished downloading
  ---------------------------------------------------------

  The leecher tool has the capacity to run a program (non-interactively) right
  after a download is completed, and will also pass the full path to the file
  or directory that was downloaded to the program.  This program will be run
  right after the download is done, and (if you have enabled said option)
  before the torrent is removed from the seedbox, and its marker file removed
  from the download folder.

  To activate the running of the post-download program, pass the option `-s`
  followed by the path to the program you want to run.

  Here is an example that runs a particular program to process downloads::

      leechtorrents -s /usr/local/bin/blend-linux-distributions

  In this example, right after your favorite Linux distribution torrent
  (which surely is `Fedora-22.iso`) is done and saved to your download folder
  `/srv/seedbox`, `leechtorrents` will execute the following command line::

      /usr/local/bin/blend-linux-distributions /srv/seedbox/Fedora-22.iso

  The standard output and standard error of the program are passed to the
  standard output and standard error of `leechtorrents`, which may be your
  terminal, a logging service, or the log file set aside for logging purposes
  by the `leechtorrents` command line parameter `-l`.  Standard input will
  be nullified, so no option for interacting with the program will exist.

  Note that your program will only ever execute once per downloaded torrent.
  Also note that the return value of your program will be ignored.  Finally,
  please note that if your program doesn't finish, this will block further
  downloads, so make sure to equip your program with a timeout (perhaps using
  `SIGALRM` or such mechanisms).

  If you want to run a shell or other language script against the downloaded
  file or directory, you are advised to write a script file and pass that as
  the argument to `-s`, then use the first argument to the script file as
  the path to the downloaded file (it's usually `$1` in sh-like languages,
  like it is `sys.argv[1]` in Python).

  How to upload torrents to your seedbox
  --------------------------------------

  The `uploadtorrents` command-line tool included in this package will upload the
  provided torrent files or magnet links to your seedbox::

      uploadtorrents TORRENT [TORRENT ...]

  This tool currently only supports PulsedMedia clients.


pkgId: 940d9d1b3686dd6c619857a4dce04de9306a1e0cb75936ea7dd07941c31fc8a0
name: simplegtd
arch: noarch
version: 0.0.24
epoch: 0
release: 1.fc33
summary: Manage your to-do list using the Getting Things Done system.
url: https://pypi.org/project/simplegtd/
rpm_license: GPLv3+
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: simplegtd-0.0.24-1.fc33.src.rpm
location_href: packages/simplegtd-0.0.24-1.fc33.noarch.rpm
checksum_type: sha256
description:
  Simple GTD: manage your TODO.txt
  ================================

  Simple GTD lets you manage your to-do list using the Getting Things Done system.

  Skip below for usage and installation instructions.

  Features
  --------

  **Sync-ready and sync-friendly**

  While Simple GTD does not have any built-in sync features -- and has no plans to gain them -- it supports any sync tool you want to use, from Git to Syncthing to Dropbox.  Incoming changes to your to-do file are reflected in the user interface immediately.  The author has verified that syncing `todo.txt` to and from Simpletask Cloudless works perfectly (using Syncthing as the sync mechanism).

  The algorithm used to persist and detect state changes in the to-do file is robust and efficient.  When Simple GTD detects external changes to your to-do file, only the portions of the file that changed are reloaded.  When you make changes to your to-do file in Simple GTD, Simple GTD saves the changes immediately, letting your sync program do its job right away.

  **Keyboard- and mouse-friendly**

  Entering new tasks and managing existing tasks with Simple GTD is quick and easy -- a single keystroke to add a task, and a single keystroke to edit an existing task.  Most of the standard shortcut keys you've learned work exactly as intended.

  **Fast**

  The program is consciously developed to reduce the overhead of common operations like inserting / rearranging / filtering your to-do lists.

  **Multi-lists**

  Unlike most to-do apps, you can manage multiple lists with Simple GTD.  Exiting the app and reopening the app again will open all lists you had open before.  Even window sizes are remembered per list, so short and long lists won't be a chore to manage.

  Usage
  -----

  The application is fairly simple to use.  When you start it, an empty window will pop up.  Click on the *Help* icon in the header bar to see the shortcut keys you can use to manage your tasks.  The standard keyboard shortcuts will work well.

  By default, the application will store your `todo.txt` file in its hidden data directory (on Linux, `~/.local/share/simplegtd/`) within your home folder.  You can, however, change that -- use the header bar Open icon to select / create a to-do file of your choice anywhere you want.  Simple GTD will then open a new window with the file.  Now close the other window -- Simple GTD will now remember which files you have opened.

  The application will remember multiple windows with different files open as well.  If you quit the application (using Quit in the toolbar or the keyboard combination) instead of closing windows one-by-one, next time you run it, Simple GTD will reopen the files you'd had open first.

  Installation
  ------------

  Ensure your system has the necessary requirements:

  * Python 3
  * GTK+ 3
  * the GTK+ Python 3 bindings (pygobject3)
  * the PyXDG Python 3 module (pyxdg)
  * libhandy 0.x

  * Install from PyPI: `pip3 install --user simplegtd`
  * Install as RPM: download / unpack the source and run `python3 setup.py bdist_rpm` in the source-unpacked folder, then install the RPM from the `dist/` folder.
  * Install on your system: download / unpack the source and run `python3 setup.py install` in the source-unpacked folder.
  * Run directly from the source: download / unpack the source and run `bin/simplegtd` from the source-unpacked folder.

  All methods work equally well, but only the RPM installation method is guaranteed to install a desktop menu icon for the application.


pkgId: 13fc67869bbc687a965c5b8801c04a3dc97f201eb232e4acae10bd27926b0318
name: snmp_exporter
arch: src
version: 0.19.0
epoch: 0
release: 1.fc33
summary: Prometheus SNMP exporter.
url: https://github.com/prometheus/snmp_exporter
rpm_license: ASL 2.0
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
location_href: packages/snmp_exporter-0.19.0-1.fc33.src.rpm
checksum_type: sha256
description:
  This is an exporter that exposes information gathered from SNMP for use by the Prometheus monitoring system.


pkgId: 24d839981d703e443ec9e423253d7e5bd7f1dbbcc57038512cd98ac44f5c9096
name: ssconverter
arch: noarch
version: 0.1.2
epoch: 0
release: 1.fc33
summary: A program to convert to CSV specific sheets of an OpenOffice / LibreOffice spreadsheet
url: http://github.com/Rudd-O/ssconverter
rpm_license: LGPLv2.1+
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: ssconverter-0.1.2-1.fc33.src.rpm
location_href: packages/ssconverter-0.1.2-1.fc33.noarch.rpm
checksum_type: sha256
description:
  ssconverter
  ============================

  This is a very small program, maintained and ported to Python 3, that
  converts specific sheets of OpenOffice / LibreOffice spreadsheets
  to CSV.

  Its name is ssconverter.  Its original  and current  purpose is to batch-convert any number of spreadsheets from OpenOffice or LibreOffice into CSV files, with a twist: unlike unoconv, it lets you specify which sheet of the many possible sheets in the spreadsheet file you want to convert.  It's invaluable to speed up batch conversion of CSV files.

  Another feature not present in the original is the ability to enable macros and recalculate the spreadsheet right before exporting it to CSV.  This is useful for people who have macro-based formulas in their spreadsheets, which would otherwise export with #VALUE! in every cell position where a macro-based formula was entered.

  Installation
  ------------

  Clone the source into a directory on your computer.

  Open a terminal and navigate to that directory.

  Make an RPM package which you can install by running

  ```
  python3 setup.py bdist_rpm
  ```

  in a terminal window.

  Tnstall the created `noarch` RPM inside the `dist/` folder.

  Alternatively, you can install it using `python setup.py install`.

  Usage
  -----

  Run the program `ssconverter` without options to get help.

  Credits
  -------

  This program [originated on Linux Journal](https://www.linuxjournal.com/content/convert-spreadsheets-csv-files-python-and-pyuno-part-1v2).


pkgId: 26c15c84bd7c53c293516b62952d9f3e1f7d5e079929e47d7957743e5a4e100e
name: takeown
arch: src
version: 0.0.12
epoch: 0
release: 1.fc33
summary: A tool to delegate file ownership to non-administrators
url: https://github.com/Rudd-O/takeown
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O)
rpm_group: System administration tools
rpm_buildhost: qubes-chroot
location_href: packages/takeown-0.0.12-1.fc33.src.rpm
checksum_type: sha256
description:
  takeown is a simple command-line tool that allows non-administrators to take
  ownership of files they do not own, so long as the administrator has set
  appropriate policy to allow that.


pkgId: e4ac9970bfae6d3518ed06cfe1f33009dd3872b61143b3cbd2e583aeb9e15b20
name: takeown-debuginfo
arch: x86_64
version: 0.0.12
epoch: 0
release: 1.fc33
summary: Debug information for package takeown
url: https://github.com/Rudd-O/takeown
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O)
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: takeown-0.0.12-1.fc33.src.rpm
location_href: packages/takeown-debuginfo-0.0.12-1.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package takeown.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 0e8b9189a6293d71f78ee6d82db980acf07caa664c6960b7eeb9369dfa8893f3
name: takeown-debugsource
arch: x86_64
version: 0.0.12
epoch: 0
release: 1.fc33
summary: Debug sources for package takeown
url: https://github.com/Rudd-O/takeown
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O)
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: takeown-0.0.12-1.fc33.src.rpm
location_href: packages/takeown-debugsource-0.0.12-1.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug sources for package takeown.
  Debug sources are useful when developing applications that use this
  package or when debugging this package.


pkgId: dd66adc412e613796a9c41211f1c6ce5b53a69f2e9c06b868dd1d1c3da44d8da
name: wol-monitor
arch: noarch
version: 0.0.4
epoch: 0
release: 5.fc33
summary: Monitor for Wake-on-LAN packets.
url: https://github.com/Rudd-O/wol-monitor
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: wol-monitor-0.0.4-5.fc33.src.rpm
location_href: packages/wol-monitor-0.0.4-5.fc33.noarch.rpm
checksum_type: sha256
description:
  This program runs as a service listening on ports 9 and 40000 (UDP), then
  when a message arrives on any of those ports (traditionally Wake-on-LAN
  messages), it reacts by writing to a well-known socket in the local
  file system.


pkgId: 3fe628c0494ca7f8966d949fb441a64b937b49c99ce682dde3af7520e12c3e54
name: youtube-dl-helper
arch: noarch
version: 0.0.13
epoch: 0
release: 1.fc33
summary: A tool to automate YouTube downloads via drag and drop
url: http://github.com/Rudd-O/youtube-dl-helper
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: youtube-dl-helper-0.0.13-1.fc33.src.rpm
location_href: packages/youtube-dl-helper-0.0.13-1.fc33.noarch.rpm
checksum_type: sha256
description:
  YouTube download helper
  =======================

  Drag and drop URLs from your browser to this application to download YouTube
  videos using `youtube-dl`.

  Requires `youtube-dl` installed in your system and in your `PATH`, as well as GNOME
  terminal, or Konsole5.

  To build a package you can install on your system: `python3 setup.py bdist_rpm`.


pkgId: c88d77d5a8301f43c1d35dd0e97eed76f3ae0ebc82d9bb96cccb72d24acdd1ad
name: zfs-debuginfo
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc33
summary: Debug information for package zfs
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc33.src.rpm
location_href: packages/zfs-debuginfo-2.0.0-0.142.38686cb9a.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package zfs.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: bb4aaa283a217392de24316675d3d5f77497d9e30516e6f08f0d7cc8c64d9a74
name: zfs-debugsource
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc33
summary: Debug sources for package zfs
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc33.src.rpm
location_href: packages/zfs-debugsource-2.0.0-0.142.38686cb9a.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug sources for package zfs.
  Debug sources are useful when developing applications that use this
  package or when debugging this package.


pkgId: 6389a77f3d13b37d188dd52e8be6149f4e8bb848ae129b87ed973f6a09ebf37f
name: zfs-test-debuginfo
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc33
summary: Debug information for package zfs-test
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc33.src.rpm
location_href: packages/zfs-test-debuginfo-2.0.0-0.142.38686cb9a.fc33.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package zfs-test.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: f434a4f1ecf0f352ea782a06acb1237b32e35246a76aaccbbfea625f82bb8f63
name: zfs-tools
arch: noarch
version: 0.5.1
epoch: 0
release: 1.fc33
summary: ZFS synchronization and snapshotting tools
url: http://github.com/Rudd-O/zfs-tools
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-tools-0.5.1-1.fc33.src.rpm
location_href: packages/zfs-tools-0.5.1-1.fc33.noarch.rpm
checksum_type: sha256
description:
  | Donate to support this free software |
  |:------------------------------------:|
  | <img width="164" height="164" title="" alt="" src="doc/bitcoin.png" /> |
  | [1Cw9nZu9ygknussPofMWCzmSMveusTbQvN](bitcoin:1Cw9nZu9ygknussPofMWCzmSMveusTbQvN) |

  The ZFS backup tools will help you graft an entire ZFS pool as a filesystem
  into a backup machine, without having to screw around snapshot names or
  complicated shell commands or crontabs.

  The utilities let you do this:

  1. zfs-shell:
     a shell that allows remote ZFS administration and nothing more

  3. zsnap:
     a command that snapshots a dataset or pool, then deletes old snapshots

  4. zreplicate
     a command that replicates an entire dataset tree using ZFS replication
     streams.  Best used in combination with zsnap as in:

     - zsnap on the local machine
     - zreplicate from the local machine to the destination machine

     Obsolete snapshots deleted by zsnap will be automatically purged on
     the destination machine by zreplicate, as a side effect of using
     replication streams.  To inhibit this, use the
     --no-replication-stream option.

     Run `zreplicate --help` for a compendium of options you may use.

  5. zbackup:
     a command to snapshot and replicate filesystems according to their user properties.
     This uses zsnap and zreplicate to do the work, which is all driven by properties.
     For details, see this [further description of zbackup](doc/README-zbackup.md).

  The repository, bug tracker and Web site for this tool is at [http://github.com/Rudd-O/zfs-tools](http://github.com/Rudd-O/zfs-tools).  Comments to me through rudd-o@rudd-o.com.



  Setup is rather complicated.  It assumes that you already have ZFS running
  and vaults on both the machine you're going to back up and the machine that
  will be receiving the backup.



  - Install the zfs-shell command
    `cp zfs-shell /usr/local/sbin`
    `chmod 755 /usr/local/sbin/zfs-shell`
    `chown root.root /usr/local/sbin/zfs-shell`

  - Create a user with a home directory and shell `zfs-shell`
    `useradd -rUm -b /var/lib -s /usr/local/sbin/zfs-shell zfs`

  - Let `sudo` know that the new user can run the zfs command
    `zfs ALL = NOPASSWD: /usr/local/sbin/zfs`
    (ensure you remove the `requiretty` default on `/etc/sudoers`)
    (check `sudoers.zfs-tools` in `contrib/` for an example)

  - Set up a cron job to run `zsnap` as frequently as you want to,
    snapshotting the dataset you intend to replicate.



  - Set up public key authentication for SSH so the backup machine
    may log as the user `zfs` (as laid out above) in the machine to
    be backed up.

  - Create a dataset to receive the backup stream.

  - Set up a cron job to fetch the dataset snapshotted by zsnap
    from the remote machine into the newly created dataset.  You
    will use `zreplicate` for that (see below for examples).

  - After the first replication, you may want to set the `mountpoint`
    attributes on the received datasets so they do not automount
    on the backup machine.



  If all went well, you should be able to do this without issue:

  (on the machine to back up)

      [root@peter]
      zsnap senderpool

  (on the machine to receive)

      [root@paul]
      zfs create receiverpool/senderpool # <--- run this ONLY ONCE
      zreplicate -o zfs@paul:senderpool receiverpool/senderpool
      
      

  (on the machine to back up)

      [root@peter]
      zsnap senderpool

  (on the machine to receive)

      [root@paul]
      zreplicate -o zfs@paul:senderpool receiverpool/senderpool
      
      

  And that's it, really.


pkgId: 27c92cfba1bfca3b94fb7890d1d06dad143868d34869ca8d485a97f7eeb0a6c7
name: zfs-tools
arch: noarch
version: 0.6.1
epoch: 0
release: 1.fc33
summary: ZFS synchronization and snapshotting tools
url: http://github.com/Rudd-O/zfs-tools
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-tools-0.6.1-1.fc33.src.rpm
location_href: packages/zfs-tools-0.6.1-1.fc33.noarch.rpm
checksum_type: sha256
description:
  | Donate to support this free software |
  |:------------------------------------:|
  | <img width="164" height="164" title="" alt="" src="doc/bitcoin.png" /> |
  | [1Cw9nZu9ygknussPofMWCzmSMveusTbQvN](bitcoin:1Cw9nZu9ygknussPofMWCzmSMveusTbQvN) |

  The ZFS backup tools will help you graft an entire ZFS pool as a filesystem
  into a backup machine, without having to screw around snapshot names or
  complicated shell commands or crontabs.

  The utilities let you do this:

  1. zfs-shell:
     a shell that allows remote ZFS administration and nothing more

  3. zsnap:
     a command that snapshots a dataset or pool, then deletes old snapshots

  4. zreplicate
     a command that replicates an entire dataset tree using ZFS replication
     streams.  Best used in combination with zsnap as in:

     - zsnap on the local machine
     - zreplicate from the local machine to the destination machine

     Obsolete snapshots deleted by zsnap will be automatically purged on
     the destination machine by zreplicate, as a side effect of using
     replication streams.  To inhibit this, use the
     --no-replication-stream option.

     Run `zreplicate --help` for a compendium of options you may use.

  5. zbackup:
     a command to snapshot and replicate filesystems according to their user properties.
     This uses zsnap and zreplicate to do the work, which is all driven by properties.
     For details, see this [further description of zbackup](doc/README-zbackup.md).

  6. zflock:
     a command to lock a filesystem against replication by zbackup.
     For details, see this [further description of zbackup](doc/README-zbackup.md).

  The repository, bug tracker and Web site for this tool is at [http://github.com/Rudd-O/zfs-tools](http://github.com/Rudd-O/zfs-tools).  Comments to me through rudd-o@rudd-o.com.



  Setup is rather complicated.  It assumes that you already have ZFS running
  and vaults on both the machine you're going to back up and the machine that
  will be receiving the backup.



  - Install the zfs-shell command
    `cp zfs-shell /usr/local/sbin`
    `chmod 755 /usr/local/sbin/zfs-shell`
    `chown root.root /usr/local/sbin/zfs-shell`

  - Create a user with a home directory and shell `zfs-shell`
    `useradd -rUm -b /var/lib -s /usr/local/sbin/zfs-shell zfs`

  - Let `sudo` know that the new user can run the zfs command
    `zfs ALL = NOPASSWD: /usr/local/sbin/zfs`
    (ensure you remove the `requiretty` default on `/etc/sudoers`)
    (check `sudoers.zfs-tools` in `contrib/` for an example)

  - Set up a cron job to run `zsnap` as frequently as you want to,
    snapshotting the dataset you intend to replicate.



  - Set up public key authentication for SSH so the backup machine
    may log as the user `zfs` (as laid out above) in the machine to
    be backed up.

  - Create a dataset to receive the backup stream.

  - Set up a cron job to fetch the dataset snapshotted by zsnap
    from the remote machine into the newly created dataset.  You
    will use `zreplicate` for that (see below for examples).

  - After the first replication, you may want to set the `mountpoint`
    attributes on the received datasets so they do not automount
    on the backup machine.



  If all went well, you should be able to do this without issue:

  (on the machine to back up)

      [root@peter]
      zsnap senderpool

  (on the machine to receive)

      [root@paul]
      zfs create receiverpool/senderpool # <--- run this ONLY ONCE
      zreplicate -o zfs@paul:senderpool receiverpool/senderpool
      
      

  (on the machine to back up)

      [root@peter]
      zsnap senderpool

  (on the machine to receive)

      [root@paul]
      zreplicate -o zfs@paul:senderpool receiverpool/senderpool
      
      

  And that's it, really.


# files

type: file
name:
  /usr/lib/debug/usr/share/zfs/zfs-tests/bin/libzfs_input_check-2.0.0-0.142.38686cb9a.fc33.x86_64.debug


type: file
name:
  /usr/lib/debug/usr/share/zfs/zfs-tests/bin/rm_lnkcnt_zero_file-2.0.0-0.142.38686cb9a.fc33.x86_64.debug


