# packages

pkgId: 54000be54863ca94b4cedee8d1bba5fc22e16b13db42bcc81457b86c24d13bc7
name: condor
arch: src
version: 23.0.0
epoch: 0
release: 1.el8
summary: HTCondor: High Throughput Computing
url: https://htcondor.org/
rpm_license: ASL 2.0
rpm_group: Applications/System
rpm_buildhost: htcss2000.chtc.wisc.edu
location_href: Packages/condor-release/condor-23.0.0-1.el8.src.rpm
checksum_type: sha256
description:
  HTCondor is a specialized workload management system for
  compute-intensive jobs. Like other full-featured batch systems, HTCondor
  provides a job queuing mechanism, scheduling policy, priority scheme,
  resource monitoring, and resource management. Users submit their
  serial or parallel jobs to HTCondor, HTCondor places them into a queue,
  chooses when and where to run the jobs based upon a policy, carefully
  monitors their progress, and ultimately informs the user upon
  completion.


pkgId: 09c4f139bd9b00dff0d83c106b7d63d2450f619e274e3c0b89a5b92c53032eb9
name: lotman
arch: src
version: 0.0.2
epoch: 0
release: 1.osg23up.el8
summary: C++ Implementation of the LotMan Library
url: https://github.com/PelicanPlatform/lotman
rpm_license: Apache-2.0
rpm_vendor: Koji
rpm_group: Unspecified
rpm_buildhost: koji-builder-64fd87566-4hvc7
rpm_packager: Koji
location_href: Packages/condor-release/lotman-0.0.2-1.osg23up.el8.src.rpm
checksum_type: sha256
description:
  Public headers for the LotMan library, which tracks data usage in dHTC environments over the "lot" object.


pkgId: a107115475ce7eb585c4cd82bf40b3707c7273b4a90081752b8b0b676199216b
name: oidc-agent
arch: src
version: 5.1.0
epoch: 0
release: 1.1.osg23up.el8
summary: Managing OpenID Connect tokens on the command line
url: https://github.com/indigo-dc/oidc-agent
rpm_license: MIT AND ISC AND LGPL-2.1-or-later AND BSD-2-Clause
rpm_vendor: Koji
rpm_group: Unspecified
rpm_buildhost: koji-builder-64fd87566-s82xc
rpm_packager: Koji
location_href: Packages/o/oidc-agent-5.1.0-1.1.osg23up.el8.src.rpm
checksum_type: sha256
description:
  oidc-agent is a set of tools to manage OpenID Connect tokens and make
  them easily usable from the command line. We followed the ssh-agent
  design, so users can handle OIDC tokens in a similar way as they do
  with ssh keys.

  oidc-agent is usually started in the beginning of an X-session or a
  login session. Through use of environment variables the agent can be
  located and used to handle OIDC tokens.

  The agent initially does not have any account configurations
  loaded. You can load an account configuration by using
  oidc-add. Multiple account configurations may be loaded in oidc-agent
  concurrently. oidc-add is also used to remove a loaded configuration
  from oidc-agent. oidc-gen is used to initially generate an account
  configurations file.


