Differences between revisions 64 and 65
Revision 64 as of 2020-11-04 21:55:37
Size: 7663
Editor: ?Thomas Goirand
Comment:
Revision 65 as of 2020-11-04 22:05:21
Size: 7635
Editor: ?Thomas Goirand
Comment:
Deletions are marked like this. Additions are marked like this.
Line 69: Line 69:
 * --([puppetlabs/trapperkeeper-authorization 1.0.0] [[https://github.com/puppetlabs/trapperkeeper-authorization|(upstream)]] [[https://bugs.debian.org/969469|(ITP -- zigo)]])-- [[https://salsa.debian.org/clojure-team/trapperkeeper-authorization-clojure|Salsa project]] in NEW queue  * --([puppetlabs/trapperkeeper-authorization 1.0.0] [[https://github.com/puppetlabs/trapperkeeper-authorization|(upstream)]] [[https://bugs.debian.org/969469|(ITP -- zigo)]])-- [[https://salsa.debian.org/clojure-team/trapperkeeper-authorization-clojure|Salsa project]]
Line 75: Line 75:
 * --([puppetlabs/trapperkeeper-filesystem-watcher 1.2.2] [[https://github.com/puppetlabs/trapperkeeper-filesystem-watcher|(upstream)]] [[https://bugs.debian.org/969164|(ITP -- zigo)]])-- [[https://salsa.debian.org/clojure-team/trapperkeeper-filesystem-watcher-clojure|Salsa project]] in NEW queue  * --([puppetlabs/trapperkeeper-filesystem-watcher 1.2.2] [[https://github.com/puppetlabs/trapperkeeper-filesystem-watcher|(upstream)]] [[https://bugs.debian.org/969164|(ITP -- zigo)]])-- [[https://salsa.debian.org/clojure-team/trapperkeeper-filesystem-watcher-clojure|Salsa project]]
Line 103: Line 103:
 * [ring-basic-authentication 1.1.0] [[https://github.com/remvee/ring-basic-authentication|(upstream)]] [[https://bugs.debian.org/973726|(ITP -- zigo)]] in NEW queue  * --([ring-basic-authentication 1.1.0] [[https://github.com/remvee/ring-basic-authentication|(upstream)]] [[https://bugs.debian.org/973726|(ITP -- zigo)]])-- Done

Puppet Team Work in Progress

Puppet

5.6 is currently in sid/buster. 6 has Puppet Server as a strict requirement, as the CA functionality has become part of Puppet Server. Additionally, most of the native resource types have been split out to separate modules, which we must obtain and package separately.

We are missing some dependencies and we need to sort out PuppetDB first, before attempting to package Puppet Server.

Puppet Server

These are the packages we need to work on to be able to get puppetserver in Debian. The full dependency tree can be seen here.

When creating a bug for a top-level package, please mark it as blocking the RFP for puppetserver:

Control: block 830904 by -1
  • libclj-yaml-clojure 0.7.0-1

    • libordered-clojure 1.5.9-1

      • libuseful-clojure 0.11.6-1

  • libraynes-fs-clojure 1.5.1

  • [com.cemerick/url 0.1.1] (upstream) (ITP -- zigo) Salsa project

  • [com.fasterxml.jackson.module/jackson-module-afterburner 2.10.0] (upstream) (RFP) java module replaced upstream by https://github.com/FasterXML/jackson-modules-base probably need help from the Java team: super complicated multi-module package...

  • [grimradical/clj-semver 0.3.0] (upstream) done: Salsa project

  • [liberator 0.15.2] (upstream) done: Salsa project

  • [net.logstash.logback/logstash-logback-encoder 5.0] (upstream)

  • libprismatic-schema-clojure 1.1.9-1

  • [puppetlabs/clj-shell-utils 1.0.2] (upstream) done: Salsa project

  • libcomidi-clojure 0.3.1 < 0.3.2

    • libbidi-clojure 2.1.3

  • libdujour-version-check-clojure 0.2.2 < 0.2.3

  • libpuppetlabs-http-client-clojure 0.9.0 < 1.1.3

  • [puppetlabs/jruby-utils 3.1.4] (upstream)

    • libtools-logging-clojure 0.2.3 < 0.4.0

    • [puppetlabs/jruby-deps 9.2.11.1-1] (upstream)

      • jruby 9.1.17.0 < 9.2.11.1

        • libjffi-java 1.2.7 < 1.2.23

        • libjnr-constants-java 0.9.9 < 0.9.15

        • libjnr-enxio-java 0.16 < 0.25

        • libjnr-posix-java 3.0.45 < 3.0.54

        • libjnr-unixsocket-java 0.18 < 0.28

        • [com.headius/backport9 1.3] (upstream)

        • libinvokebinder-java 1.7 < 1.11

        • [javax.annotation/javax.annotation-api 1.3.1] (upstream) Java module

  • libkitchensink-clojure 2.3.0 < 3.1.0

    • libtools-cli-clojure 0.3.5 < 0.3.6

  • libpuppetlabs-ring-middleware-clojure 1.0.0 < 1.0.1

    • libring-core-clojure 1.6.2
      • libtools-reader-clojure 1.0.0 < 1.2.1

  • libssl-utils-clojure 0.8.3 < 3.0.4

  • [puppetlabs/trapperkeeper-authorization 1.0.0] (upstream) (ITP -- zigo) Salsa project

  • [puppetlabs/trapperkeeper-comidi-metrics 0.1.1] (upstream) done: Salsa project

  • [puppetlabs/trapperkeeper-filesystem-watcher 1.2.2] (upstream) (ITP -- zigo) Salsa project

  • libtrapperkeeper-metrics-clojure 0.4.2 < 1.2.3

    • libcheshire-clojure 5.7.1 < 5.8.0

      • libjackson2-dataformat-cbor 2.7.8 < 2.9.0

      • libjackson2-dataformat-smile 2.7.8 < 2.9.0

    • libdropwizard-metrics-java 3.2.6
    • [org.jolokia/jolokia-core 1.6.2] (upstream)

  • libtrapperkeeper-scheduler-clojure 0.1.0 < 1.1.2

    • libquartz2-java 2.3.0 < 2.3.1

      • libc3p0-java 0.9.1.2 < 0.9.5.3

      • [com.mchange/mchange-commons-java 0.2.15] (upstream) (RFP)

  • libtrapperkeeper-status-clojure 0.7.1 < 1.1.0

    • libversioneer-clojure 0.1.1 < 0.2.0

  • libtrapperkeeper-webserver-jetty9-clojure 1.7.0 < 4.1.0

    • libservlet-api-java 4.0.1 < 3.1.0

  • libtrapperkeeper-clojure 1.5.2 < 3.1.0

    • libcore-async-clojure 0.3.44 < 0.4.490

      • libtools-analyzer-jvm-clojure 0.7.1 < 0.7.2

        • libcore-memoize-clojure 0.5.1 < 0.7.1

          • libcore-cache-clojure 0.6.5 < 0.7.1

            • libdata-priority-map-clojure 0.0.7 < 0.0.9

    • libjanino-java 2.7.0 < 3.0.8

  • [ring-basic-authentication 1.1.0] (upstream) (ITP -- zigo) Done

  • libring-mock-clojure 0.3.1 < 0.3.2

PuppetDB

Current Status

The PuppetDB package in unstable is as of Sep 2018 broken.

Autopkgtests failing: https://ci.debian.net/packages/p/puppetdb/

The PuppetDB process fails to start, being unable to find any subcommands.

Apart from being broken for the past 6 months, the package never migrated to testing, mostly due to the following RC bugs:

If we want to see PuppetDB in Buster, all of these bugs must be resolved.

Packaging notes

PuppetDB & deps were packaged without using leiningen, as it was not in the archive at the time. Any dependency being re-uploaded should be converted to build using leiningen.

TBD: provide sample d/rules content for building with leiningen, at least until we have a DH buildsystem that does that automatically.