Enter the query into the form above. You can look for specific version of a package by using @ symbol like this: gcc@10.
API method:
GET /api/packages?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel webring send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
389ds is an enterprise-class LDAP server. It is hardened by real-world use, is full-featured, and supports multi-master replication.
Other features include:
Online, zero downtime, LDAP-based update of schema, configuration, and management including Access Control Information (ACIs);
Asynchronous Multi-Master Replication, to provide fault tolerance and high write performance;
Extensive documentation;
Secure authentication and transport (TLS, and SASL);
LDAPv3 compliant server.
This package provides an object-oriented API to access LDAP directory servers from Python programs.
nss-pam-ldapd provides a Name Service Switch (NSS) module that allows your LDAP server to provide user account, group, host name, alias, netgroup, and basically any other information that you would normally get from /etc flat files or NIS. It also provides a Pluggable Authentication Module (PAM) to do identity and authentication management with an LDAP server.
The library provides a sort of useful classes, algorithms, and high-level protocols to support an application programmer in writing such software. The most remarkable feature is the absence of a trusted third party (TTP), i.e. neither a central game server nor trusted hardware components are necessary.
The corresponding cryptographic problem, actually called Mental Poker, has been studied since 1979 (Shamir, Rivest, and Adleman) by many authors. LibTMCG provides the first practical implementation of such protocols.
The Distributed Privacy Guard (DKGPG) implements Distributed Key Generation (DKG) and Threshold Cryptography for OpenPGP. The generated public keys are compatible with the standard and thus can be used by any RFC4880-compliant application (e.g. GnuPG). The main purposes of this software are distributing power among multiple parties, eliminating single points of failure, and increasing the difficulty of side-channel attacks on private key material.
DKGPG consists of a bunch of simple command-line programs. The current implementation is in experimental state and should NOT be used in production environments.
This package provides a C++ library for working with S-Expressions.
Set of OpenPGP (RFC4880) tools that works on Linux, *BSD and macOS as a replacement of GnuPG. It is maintained by Ribose after being forked from NetPGP, itself originally written for NetBSD.
librnp is the library used by rnp for all OpenPGP functions, useful for developers to build against. It is a “real” library, not a wrapper like GPGME of GnuPG.
The Oslo Test framework provides common fixtures, support for debugging, and better support for mocking results.
Git-review is a command-line tool that helps submitting Git branches to Gerrit for review, or fetching existing ones.
Python-hacking is a set of flake8 plugins that test and enforce the OpenStack style guidelines.
The Oslo Concurrency Library provides utilities for safely running multi-thread, multi-process applications using locking mechanisms and for running external processes.
The OpenStack Service Types Authority contains information about officiag OpenStack services and their historical service-type aliases. The data is in JSON and the latest data should always be used. This simple library exists to allow for easy consumption of the data, along with a built-in version of the data to use in case network access is for some reason not possible and local caching of the fetched data.
The oslo.i18n library contain utilities for working with internationalization (i18n) features, especially translation for text strings in an application or library.
The Oslo context library has helpers to maintain useful information about a request context. The request context is usually populated in the WSGI pipeline and used by various modules such as logging.
The cliff framework allows creating multi-level commands such as those of subversion and git, where the main program handles some basic argument parsing and then invokes a sub-command to do the work. It uses plugins to define sub-commands, output formatters, and other extensions.
The oslo.log (logging) configuration library provides standardized configuration for all OpenStack projects. It also provides custom formatters, handlers and support for context specific logging (like resource id’s etc).
Python makes loading code dynamically easy, allowing you to configure and extend your application by discovering and loading extensions ("plugins") at runtime. Many applications implement their own library for doing this, using __import__ or importlib. Stevedore avoids creating yet another extension mechanism by building on top of setuptools entry points. The code for managing entry points tends to be repetitive, though, so stevedore provides manager classes for implementing common patterns for using dynamically loaded extensions.
The cliff framework allows creating multi-level commands such as those of subversion and git, where the main program handles some basic argument parsing and then invokes a sub-command to do the work. It uses plugins to define sub-commands, output formatters, and other extensions.
The oslo.utils library provides support for common utility type functions, such as encoding, exception handling, string manipulation, and time handling.
Keystoneauth provides a standard way to do authentication and service requests within the OpenStack ecosystem. It is designed for use in conjunction with the existing OpenStack clients and for simplifying the process of writing new clients.
The OpenStack Service Types Authority contains information about officiag OpenStack services and their historical service-type aliases. The data is in JSON and the latest data should always be used. This simple library exists to allow for easy consumption of the data, along with a built-in version of the data to use in case network access is for some reason not possible and local caching of the fetched data.
Reno is a tool for storing release notes in a git repository and building documentation from them.
This is a set of integration tests to be run against a live OpenStack cluster. Tempest has batteries of tests for OpenStack API validation, scenarios, and other specific tests useful in validating an OpenStack deployment.
This package provides themes and extensions for Sphinx for publishing to docs.openstack.org and developer.openstack.org.