[Pkg-puppet-devel] Bug#1030256: FTBFS: test failures ArgumentError: can't find user for puppet

[Vagrant Cascadian]

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 copies the host's /etc/passwd and
/etc/group into the chroot when it builds... and presumably the buildd
environment does this as well (and all DSA machines have the puppet user
available?)... and so the puppet user is in fact available in those
cases, but not others...

I was able to workaround the issue with:

  sbuild --chroot-setup-commands='adduser --gecos ,,, --disabled-password puppet' ...

Is there an option in sbuild to not copy the passwd/group information
into the chroot? What are the implications of that?


> Is there some flag we could use to tell reproducible-builds to build 
> this package as a regular user instead of root?

It typically builds as two different users, pbuilder1 and pbuilder2, not
as root.


> If not I might have to patch the test suite to work around some of the 
> logic in there, which I'm not too excited about.
>
> Perhaps an alternative would be to add "puppet-agent" as a build 
> dependency, because that package will create a "puppet" user in the 
> environment.

That seems like a viable option, though obviously a bit ugly if that
package does a bunch of other things or has many other
dependencies. Would it make sense to have a package that just creates a
user and nothing else?


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-puppet-devel/attachments/20230202/ef55a81c/attachment-0001.sig>