|0008-Adjust-defaults-paths.patch||Adjust defaults paths
This patch adjusts the default paths used in various places in
Puppetserver, mainly replacing /opt/puppetlabs with paths that conform to
Debian Policy. It also replaces the "puppetlabs" path component with "puppet"
in the places where it appears, as a matter of consistency with previous
releases of Puppet packages in the Debian archive.
Patch project.clj to build locally using lein.
|Puppet Package Maintainers <email@example.com>||not-needed||2023-01-09|
|0002-Patch-out-pjstadig-humane-test-output-library.patch||Patch out pjstadig/humane-test-output library
This is not packaged in Debian yet, and not required to run tests.
|0003-Add-JRuby-stdlib-libraries-to-ruby-load-path.patch||Add JRuby stdlib libraries to ruby-load-path
Since we don't run puppetserver with jruby-stdlib.jar on the
classpath (because we hope to get rid of it at some point) we need to
ensure we always have "/usr/share/jruby/lib/ruby/stdlib" on the JRuby
|0004-Don-t-mess-with-RUBYLIB-when-calling-autosign-script.patch||Don't mess with RUBYLIB when calling autosign script
Since Debian installs Puppet and Facter libraries in the system-wide
path, there is no need to modify RUBYLIB in the exec environment. Doing
so causes errors because of the overlapping namespaces: "warning:
already initialized constant [..]"
|0005-Disable-remote-update-check-and-dropsonde-analytics.patch||Disable remote update-check and dropsonde analytics
This disables the update-check by default, although it can be enabled
and should work. Dropsonde analytics, however, are not supported at all
because the required gem isn't packaged in Debian.
|0006-Fix-unknown-symbol-error-in-integration-tests.patch||Fix unknown symbol error in integration tests
This is a workaround for a clojure testsuite compilation error that
appears with the upstream code:
Syntax error compiling at (puppetlabs/services/jruby/jruby_metrics_service_test.clj:126:1).
Unable to resolve symbol: mock-puppetserver-config-service in this context
It's unknown what is causing the issue, it should be investigated at
some point, but the workaround should be sound and doesn't affect the
main app code which does not suffer this issue.
|0007-Adapt-JRuby-environment-test-for-Debian.patch||Adapt JRuby environment test for Debian
When JRuby is executed from a jar (embedded), it adds the RUBY
environment variable. Since JRuby is instead loaded from the filesystem,
this envvar isn't present, so don't expect it.
A similar patch also exists for src:jruby-utils-clojure.
|0009-Remove-call-to-symlink-cadir.patch||Remove call to symlink-cadir
Because upstream assumes :ssldir and :cadir are always under :confdir,
this doesn't work well for Debian. Furthermore, this function will
full-on *delete* the :old-cadir directory tree with very little
confidence that it's actually safe to do so. This does not seems like a
worthy tradeoff for a backwards-compatibility symlink?
Anyway, we assume the system administrator knows what they're doing when
moving around the Puppet CA certificates, and let them handle the
compatibility symlinks as needed...
|0010-Backport-fix-for-CVE-2023-1894.patch||Backport fix for CVE-2023-1894
|=?utf-8?b?SsOpcsO0bWUgQ2hhcmFvdWk=?= <firstname.lastname@example.org>||not-needed||debian upstream||2023-05-07|