File: control

package info (click to toggle)
trapperkeeper-status-clojure 1.1.1-5
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 356 kB
  • sloc: sh: 71; makefile: 34; xml: 10
file content (55 lines) | stat: -rw-r--r-- 2,037 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
Source: trapperkeeper-status-clojure
Section: java
Priority: optional
Maintainer: Debian Clojure Maintainers <team+clojure@tracker.debian.org>
Uploaders:
 Apollon Oikonomopoulos <apoikos@debian.org>,
 Jérôme Charaoui <jerome@riseup.net>,
Build-Depends:
 debhelper-compat (= 13),
 default-jdk-headless,
 javahelper,
 leiningen,
 libcheshire-clojure (>= 5.11.0-2),
 libclojure-java (>= 1.11.1-2),
 libcomidi-clojure,
 libjava-jmx-clojure,
 libkitchensink-clojure (>= 3.2.1),
 libprismatic-schema-clojure,
 libpuppetlabs-http-client-clojure (>= 2.0.1-4) <!nocheck>,
 libpuppetlabs-i18n-clojure (>= 0.9.2-2),
 libpuppetlabs-ring-middleware-clojure (>= 1.3.1-3),
 libring-defaults-clojure,
 libslingshot-clojure,
 libtools-logging-clojure,
 libtrapperkeeper-authorization-clojure (>= 1.0.0-3),
 libtrapperkeeper-clojure (>= 3.2.0-2),
 libtrapperkeeper-scheduler-clojure (>= 1.1.3-7),
 libtrapperkeeper-webserver-jetty9-clojure (>= 4.4.1-4) <!nocheck>,
 libversioneer-clojure,
 maven-repo-helper,
Standards-Version: 4.6.2
Vcs-Git: https://salsa.debian.org/clojure-team/trapperkeeper-status-clojure.git
Vcs-Browser: https://salsa.debian.org/clojure-team/trapperkeeper-status-clojure
Homepage: https://github.com/puppetlabs/trapperkeeper-status
Rules-Requires-Root: no

Package: libtrapperkeeper-status-clojure
Architecture: all
Depends:
 ${java:Depends},
 ${misc:Depends},
Breaks:
 puppetserver (<= 7.9.4-2)
Recommends:
 ${java:Recommends},
Description: status monitoring for trapperkeeper services
 The Trapperkeeper Status Service is a Trapperkeeper service that provides a
 web endpoint for getting status information for a Trapperkeeper-based
 application.
 .
 Other Trapperkeeper services may register a status callback function with
 the Status Service, returning any kind of status information that is relevant
 to the consuming service. The Status Service will make this information
 available via HTTP, in a consistent, consolidated format. This makes it
 possible for users to automate monitoring and other tasks around the system.