On Mon, Aug 03, 2020 at 04:47:39PM +0200, Jun Aruga wrote:
...
> So, I suppose previously it tried to build outputed platform (f30).
> The other build id 9294 is f32, 9295 is f31, 9296 is f33.
Ah, that would do it. I finally was shown the command to retire the f30
eol platform and did so... before
> Can you try again now? we fixed a major issue with mbs, which I wouldn't
think was related to this, but who knows..
I tried it, and found the cause of the error now.
> So isn't this the relevant part of root.log which could give a hint?
Yes, possibly it is related to the issue.
> https://koji
Dne 02. 08. 20 v 0:21 Kevin Fenzi napsal(a):
> On Fri, Jul 31, 2020 at 04:05:20PM +0200, Jun Aruga wrote:
>> Hi,
>> Sometimes once per a few times, I faced the following weird build
>> error when building Ruby modules.
>> Did you see it? Known issue?
>>
>> https://koji.fedoraproject.org/koji/task
Hi,
> Weird. The actual error is:
> "ERROR: Could not find useradd in chroot, maybe the install failed?"
>
> But that sounds like what happens when it didn't install the build rpms
> in there.
>
> Can you try again now? we fixed a major issue with mbs, which I wouldn't
> think was related to this,
On Fri, Jul 31, 2020 at 04:05:20PM +0200, Jun Aruga wrote:
> Hi,
> Sometimes once per a few times, I faced the following weird build
> error when building Ruby modules.
> Did you see it? Known issue?
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=48194471
> BuildrootError: could not init
Hi,
Sometimes once per a few times, I faced the following weird build
error when building Ruby modules.
Did you see it? Known issue?
https://koji.fedoraproject.org/koji/taskinfo?taskID=48194471
BuildrootError: could not init mock buildroot, mock exited with status
20; see root.log for more inform
