Source: condor Maintainer: Debian HPC Team Uploaders: Tim Theisen Section: science Priority: optional Build-Depends: cmake (>= 3.16), debhelper, debhelper-compat (= 13), default-jdk, dh-python, libboost-filesystem-dev, libboost-program-options-dev, libboost-python-dev, libboost-regex-dev, libboost-system-dev, libboost-test-dev, libboost-thread-dev, libcgroup-dev, libcurl4-openssl-dev, libkrb5-dev, libldap2-dev | libldap-dev, libmunge-dev, libpam0g-dev, libpcre2-dev, libpq-dev, libscitokens-dev, libsqlite3-dev, libsystemd-dev, libvirt-dev, libx11-dev, libxml2-dev, libxss-dev, python3-dev, python3-setuptools, python3-sphinx, python3-sphinx-rtd-theme, python3-nbsphinx, python3-sphinx-autodoc-typehints, uuid-dev, voms-dev, zlib1g-dev Build-Conflicts: liblog4cpp5-dev Standards-Version: 4.6.2 Vcs-Browser: https://salsa.debian.org/hpc-team/condor Vcs-Git: https://salsa.debian.org/hpc-team/condor.git Homepage: https://htcondor.org/ Rules-Requires-Root: no Package: condor Architecture: any Depends: adduser, libdate-manip-perl, python3, python3-requests, libcom-err2, libgssapi-krb5-2, libk5crypto3, libkrb5-3, libkrb5support0, libmunge2, libssl3, libscitokens0, libvomsapi1v5, net-tools, libjs-bootstrap, libjs-jquery, ${misc:Depends}, ${perl:Depends}, ${python3:Depends}, ${shlibs:Depends} Recommends: openssh-server Suggests: docker.io, coop-computing-tools, singularity-container, slurm-client Conflicts: htcondor (<< ${binary:Version}), libclassad16 Breaks: htcondor (<< ${binary:Version}), libclassad16 Replaces: htcondor (<< ${binary:Version}), libclassad16 Description: distributed workload management system Like other full-featured batch systems, HTCondor provides a job queueing 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. It chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion. . Unlike more traditional batch queueing systems, HTCondor can also effectively harness wasted CPU power from otherwise idle desktop workstations. HTCondor does not require a shared file system across machines - if no shared file system is available, HTCondor can transfer the job's data files on behalf of the user. . This package can set up an appropriate initial configuration at install time for a machine intended either as a member of an existing HTCondor pool or as a "Personal" (single machine) HTCondor pool. Package: condor-dev Architecture: any Section: libdevel Depends: ${misc:Depends}, ${shlibs:Depends} Conflicts: htcondor-dev (<< ${binary:Version}), libclassad-dev Breaks: htcondor-dev (<< ${binary:Version}), libclassad-dev Replaces: htcondor-dev (<< ${binary:Version}), libclassad-dev Description: distributed workload management system - development files Like other full-featured batch systems, HTCondor provides a job queueing 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. It chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion. . Unlike more traditional batch queueing systems, HTCondor can also effectively harness wasted CPU power from otherwise idle desktop workstations. HTCondor does not require a shared file system across machines - if no shared file system is available, HTCondor can transfer the job's data files on behalf of the user. . This package provides headers and libraries for development of HTCondor add-ons. Package: condor-doc Architecture: all Section: doc Depends: ${misc:Depends} Conflicts: htcondor-doc (<< ${binary:Version}) Breaks: htcondor-doc (<< ${binary:Version}) Replaces: htcondor-doc (<< ${binary:Version}) Description: distributed workload management system - documentation Like other full-featured batch systems, HTCondor provides a job queueing 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. It chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion. . Unlike more traditional batch queueing systems, HTCondor can also effectively harness wasted CPU power from otherwise idle desktop workstations. HTCondor does not require a shared file system across machines - if no shared file system is available, HTCondor can transfer the job's data files on behalf of the user. . This package provides HTCondor's documentation in HTML and PDF format, as well as configuration and other examples. Package: minicondor Architecture: any Section: science Depends: condor (= ${binary:Version}), ${misc:Depends} Conflicts: minihtcondor (<< ${binary:Version}) Breaks: minihtcondor (<< ${binary:Version}) Replaces: minihtcondor (<< ${binary:Version}) Description: distributed workload management system - single node configuration Like other full-featured batch systems, HTCondor provides a job queueing 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. It chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion. . Unlike more traditional batch queueing systems, HTCondor can also effectively harness wasted CPU power from otherwise idle desktop workstations. HTCondor does not require a shared file system across machines - if no shared file system is available, HTCondor can transfer the job's data files on behalf of the user. . This package provides an example configuration is good for trying out HTCondor for the first time. It only configures the IPv4 loopback address, turns on basic security, and shortens many timers to be more responsive. Package: condor-annex-ec2 Architecture: any Section: science Depends: condor (= ${binary:Version}), ${misc:Depends} Conflicts: htcondor-annex-ec2 (<< ${binary:Version}) Breaks: htcondor-annex-ec2 (<< ${binary:Version}) Replaces: htcondor-annex-ec2 (<< ${binary:Version}) Description: distributed workload management system - single node configuration Like other full-featured batch systems, HTCondor provides a job queueing 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. It chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion. . Unlike more traditional batch queueing systems, HTCondor can also effectively harness wasted CPU power from otherwise idle desktop workstations. HTCondor does not require a shared file system across machines - if no shared file system is available, HTCondor can transfer the job's data files on behalf of the user. . This package provides configuration and script to make an EC2 image annex-compatible. Do NOT install on a non-EC2 image. Package: condor-upgrade-checks Architecture: all Section: science Depends: condor, python3, pcre2-utils, ${misc:Depends} Conflicts: htcondor-upgrade-checks (<< ${binary:Version}) Breaks: htcondor-upgrade-checks (<< ${binary:Version}) Replaces: htcondor-upgrade-checks (<< ${binary:Version}) Description: distributed workload management system - single node configuration Like other full-featured batch systems, HTCondor provides a job queueing 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. It chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion. . Unlike more traditional batch queueing systems, HTCondor can also effectively harness wasted CPU power from otherwise idle desktop workstations. HTCondor does not require a shared file system across machines - if no shared file system is available, HTCondor can transfer the job's data files on behalf of the user. . Examines the current HTCondor installation and recommends changes to ensure a smooth upgrade to a subsequent HTCondor version. Package: condor-kbdd Architecture: any Section: science Depends: condor (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends} Description: distributed workload management system - single node configuration Like other full-featured batch systems, HTCondor provides a job queueing 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. It chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion. . Unlike more traditional batch queueing systems, HTCondor can also effectively harness wasted CPU power from otherwise idle desktop workstations. HTCondor does not require a shared file system across machines - if no shared file system is available, HTCondor can transfer the job's data files on behalf of the user. . The condor_kbdd monitors logged in X users for activity. It is only useful on systems where no device (e.g. /dev/*) can be used to determine console idle time. Package: condor-vm-gahp Architecture: any Section: science Depends: condor (= ${binary:Version}), libvirt0, ${misc:Depends}, ${shlibs:Depends} Description: distributed workload management system - single node configuration Like other full-featured batch systems, HTCondor provides a job queueing 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. It chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion. . Unlike more traditional batch queueing systems, HTCondor can also effectively harness wasted CPU power from otherwise idle desktop workstations. HTCondor does not require a shared file system across machines - if no shared file system is available, HTCondor can transfer the job's data files on behalf of the user. . The condor_vm-gahp enables the Virtual Machine Universe feature of HTCondor. The VM Universe uses libvirt to start and control VMs under HTCondor's Startd. Package: condor-test Architecture: any Section: science Depends: condor (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends} Conflicts: htcondor-test (<< ${binary:Version}) Breaks: htcondor-test (<< ${binary:Version}) Replaces: htcondor-test (<< ${binary:Version}) Description: distributed workload management system - single node configuration Like other full-featured batch systems, HTCondor provides a job queueing 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. It chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion. . Unlike more traditional batch queueing systems, HTCondor can also effectively harness wasted CPU power from otherwise idle desktop workstations. HTCondor does not require a shared file system across machines - if no shared file system is available, HTCondor can transfer the job's data files on behalf of the user. . This package provides a few miscellaneous test scripts. Package: htcondor Architecture: any Depends: condor (= ${binary:Version}), ${misc:Depends} Description: transitional dummy package This package aids upgrades of existing htcondor installations to the package name "condor". The package is empty and it can safely be removed. Package: htcondor-dev Architecture: any Depends: condor-dev (= ${binary:Version}), ${misc:Depends} Description: transitional dummy package This package aids upgrades of existing htcondor installations to the package name "condor". The package is empty and it can safely be removed. Package: htcondor-doc Architecture: all Depends: condor-doc (= ${binary:Version}), ${misc:Depends} Description: transitional dummy package This package aids upgrades of existing htcondor installations to the package name "condor". The package is empty and it can safely be removed. Package: minihtcondor Architecture: any Depends: minicondor (= ${binary:Version}), ${misc:Depends} Description: transitional dummy package This package aids upgrades of existing htcondor installations to the package name "condor". The package is empty and it can safely be removed. Package: htcondor-annex-ec2 Architecture: any Depends: condor-annex-ec2 (= ${binary:Version}), ${misc:Depends} Description: transitional dummy package This package aids upgrades of existing htcondor installations to the package name "condor". The package is empty and it can safely be removed. Package: htcondor-upgrade-checks Architecture: all Depends: condor-upgrade-checks (= ${binary:Version}), ${misc:Depends} Description: transitional dummy package This package aids upgrades of existing htcondor installations to the package name "condor". The package is empty and it can safely be removed. Package: htcondor-test Architecture: any Depends: condor-test (= ${binary:Version}), ${misc:Depends} Description: transitional dummy package This package aids upgrades of existing htcondor installations to the package name "condor". The package is empty and it can safely be removed.