On Wednesday, April 15, 2020 10:22:42 PM CEST Göran Uddeborg wrote:
> Just in case someone with the same problem stumbles on my mail when
> googling, I'll explain what I did in the end.
>
> I got the suggestion to disable nspawn when building. That solved the
> initial problem, but introduced two other. I was able to work around
> those too by bind mounting /run and /tmp into the container. Giving
> fedpkg the below mock configuration; I was able to build systemd.
Who gave you this suggestion, haven't you tried to fill an issue against
systemd (please post link if yes)?
Pavel
> config_opts['use_nspawn'] = False
> config_opts['plugin_conf']['bind_mount_enable'] = True
> config_opts['plugin_conf']['bind_mount_opts']['dirs'].append(('/run', '/run'
> ))
> config_opts['plugin_conf']['bind_mount_opts']['dirs'].append(('/tmp', '/tmp'
> ))
>
> include('fedora-32-x86_64.cfg')
> _______________________________________________
> devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[email protected]
>
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
