ok, so perhaps I needed to use `sudo` previously - I ended up manually
wiping the `/var/lib/mock/ directory contents and that fixed me up
Mark E. Fuller, Ph.D.
fuller(a)fedoraproject.org
fuller(a)mefuller.dev
@fuller:fedora.im
@fuller:one.ems.host
https://mefuller.dev
PGP Fingerprint: 73F1 A30C BDF4 DB4B C75F FD0F D599 E76C FFCA BF60
On 12/31/23 12:43, Mark E. Fuller wrote:
> Unfortunately, this doesn't seem to do the trick - the `mock
> --scrub=all` runs, but then the same error keeps occurring on both systems
>
> Any other thoughts as to how to more aggressively/manually force an update?
>
> Mark E. Fuller, Ph.D.
> fuller(a)fedoraproject.org
> fuller(a)mefuller.dev
> @fuller:fedora.im
> @fuller:one.ems.host
>
https://mefuller.dev
> PGP Fingerprint: 73F1 A30C BDF4 DB4B C75F FD0F D599 E76C FFCA BF60
>
> On 12/28/23 14:32, Jonathan Steffan wrote:
>> Mark,
>>
>> You likely just need to scrub mock to clean out the dnf4 based
>> bootstrap. A fresh one with dnf5 will be automatically downloaded.
>>
>> mock --scrub=all
>>
>> --
>> Jonathan Steffan
>>
>> --
>> _______________________________________________
>> devel mailing list -- devel(a)lists.fedoraproject.org
>> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>> 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/devel@lists.fedoraproject.org
>> Do not reply to spam, report it:
>>
https://pagure.io/fedora-infrastructure/new_issue