# packages

pkgId: 7b5efb7ed5d77fa2673a2628e88ce465830132ab408a67de6fcb0b1c516a0cb7
name: condor
arch: src
version: 23.10.27
epoch: 0
release: 0.811708.el8
summary: HTCondor: High Throughput Computing
url: https://htcondor.org/
rpm_license: Apache-2.0
rpm_group: Applications/System
rpm_buildhost: htcss2000.chtc.wisc.edu
location_href: Packages/condor-daily/condor-23.10.27-0.811708.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: 979b1b5866cfdb8f47f407b68c7e21ca76fbfe19ab21b36ab77593a103cab2a0
name: frontier-squid
arch: src
version: 6.13
epoch: 11
release: 1.4.osg23up.el8
summary: The Frontier distribution of the Squid proxy caching server
rpm_license: GPL
rpm_vendor: Koji
rpm_group: System Environment/Daemons
rpm_buildhost: koji-builder-69c4448b7-8tdsg
rpm_packager: Koji
location_href: Packages/f/frontier-squid-6.13-1.4.osg23up.el8.src.rpm
checksum_type: sha256
description:
  Squid is a high-performance proxy caching server for Web clients,
  supporting FTP, gopher, and HTTP data objects. Unlike traditional
  caching software, Squid handles all requests in a single,
  non-blocking, I/O-driven process. Squid keeps meta data and especially
  hot objects cached in RAM, caches DNS lookups, supports non-blocking
  DNS lookups, and implements negative caching of failed requests.  This
  squid distribution has been expecially tuned to work with the Frontier
  server to cache Database entries retrieved from an ORACLE back-end,
  particularly its need for the http standard If-Modified-Since feature.


pkgId: 7156a3807c34c67014c72465d2199afadd8ba98540457b7a113d0964e4acd8d5
name: glideinwms
arch: src
version: 3.11.1
epoch: 0
release: 0.5.rc5.osg23up.el8
summary: The glidein Workload Management System (glideinWMS)
url: http://glideinwms.fnal.gov
rpm_license: Apache-2.0
rpm_vendor: Koji
rpm_group: Unspecified
rpm_buildhost: koji-builder-arm0000.chtc.wisc.edu
rpm_packager: Koji
location_href: Packages/g/glideinwms-3.11.1-0.5.rc5.osg23up.el8.src.rpm
checksum_type: sha256
description:
  This is a package for the glidein workload management system.
  GlideinWMS provides a simple way to access the Grid, Cloud and HPC
  resources through a dynamic HTCondor pool of grid-submitted resources.


pkgId: b358db16f4322e820a1ab14f98da8f3f947faa6e2caf0ccab223fbdb4d41a703
name: lotman
arch: src
version: 0.0.4
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: kojibuilder2-kojid-6c64ff84f8-zpq9c
rpm_packager: Koji
location_href: Packages/l/lotman-0.0.4-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: 45f39259665e963910ad8c19225d7f882047e9df3879255c2212b2f80c7aac09
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.


