Michael Schroeder

Do we want to set `require_order` to stay compatible?

The macro section gets copied verbatim into the rpmmacros file for the build, so rpm will also no longer be able to work. Thus just ignoring it in the scheduler...

That's certainly not the case. Note that this is about a macro named "%if", not some %if line in the macro *body*.

I think it could be done by using the official devtools as "build engine". As an example from the Fedora world, you can use the "mock" tool as build engine...

Mock seems to always set the PATH to /usr/bin:/bin:..., so I'd rather just do something like that if /etc/redhat-release is present and not do those version testing. Would that also...

It shouldn't be necessary to add a querthdrmd5 function, the data is supposed to come from the containerinfo file.

(Or, like in OBS, via a .obsbinlnk file.)

Now implemented in 50b1a5881130d2d26ca907874f4f9f37eeea8a06

Wait wait, with this you are killing some UEFI versions. We had to go back to 2048 because of this in the past.

We use 'gzip --rsyncable' because we support delta downloads of repository metadata. The way forward would be to switch to zchunk metadata compression. All the code is in place, but...