Hi,
Quoting Vagrant Cascadian (2023-02-03 00:18:58)
> On 2023-02-01, Jérôme Charaoui wrote:
> > I don't know how common that is in build environments, but it's not
> > something that I have or think I should have in my build (sbuild) or
> > test (autopkgtest) environments.
>
> I was able to rep
On 2023-02-02, Vagrant Cascadian wrote:
> On 2023-02-01, Jérôme Charaoui wrote:
>> Perhaps an alternative would be to add "puppet-agent" as a build
>> dependency, because that package will create a "puppet" user in the
>> environment.
And for completeness, this also worked for me:
sbuild --ad
On 2023-02-01, Jérôme Charaoui wrote:
> I don't know how common that is in build environments, but it's not
> something that I have or think I should have in my build (sbuild) or
> test (autopkgtest) environments.
I was able to reproduce the issue with sbuild.
This appears to be because sbuild
I think this is occurring because the test is being run as "root".
I don't know how common that is in build environments, but it's not
something that I have or think I should have in my build (sbuild) or
test (autopkgtest) environments.
Is there some flag we could use to tell reproducible-bui
Source: ruby-puppetserver-ca-cli
Version: 2.4.0-1
Severity: serious
Tag: ftbfs
Dear Maintainer,
ruby-puppetserver-ca-cli currently fails to build from source with test
failures. Example:
1) Puppetserver::Ca::Action::Enable infracrl does not print the help
output if called correctly
F
5 matches
Mail list logo
