# packages

pkgId: 0b3effe78637628df205d4f2633e0a890624bc3a8d025493bb63793c3bd7c900
name: glideinwms
arch: src
version: 3.11.1
epoch: 0
release: 0.1.rc1.osg23up.el8
summary: The glidein Workload Management System (glideinWMS)
url: http://glideinwms.fnal.gov
rpm_license: Fermitools Software Legal Information (Modified BSD License)
rpm_vendor: Koji
rpm_group: Unspecified
rpm_buildhost: kojibuilder2-kojid-85f9bfd8b-bp69q
rpm_packager: Koji
location_href: Packages/g/glideinwms-3.11.1-0.1.rc1.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 condor 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.


