mockchain: regression of local repo functionality from 1.3.4-1 to 1.4.1-1 on F25 about mock HOT 10 CLOSED

mockchain_local_repo_fail.tar.gz

from mock.

See https://github.com/rpm-software-management/mock/wiki#using-file-urls-in-configs

from mock.

So mockchain is broken then?

The whole point of mockchain is to give it two or more SRPMs and build them in series.

Why isn't mockchain handling that? (the bind mounting)

Why hasn't the documentation been updated?

Why did you close this ticket? It's a valid bug the command is broken as described in the manual.

from mock.

@xsuchy it should be noticed in Release Notes then, it is important change!
Can I still use file:// in baseurls without systemd-nspawn and bootstrap options?

from mock.

@Frodox I set --no-bootstrap-chroot as default (in master) as the proposed solution with bind mounting does not work either. So in next version it should work again (with default settings).

from mock.

Note this breaks the ability to build RPMs that require dependencies from other RPMs being built, for example building Mesa + LLVM/clang for i686 you need LLVM/clang built before you can build Mesa against the correct LLVM/clang libraries..

Please provide an example as to how to do this before closing this bug.

from mock.

@xsuchy are you ever going to answer to these inquiries? Can you just remove mockchain altogether then if you're not going to support it?

from mock.

@xenithorb ??? This issue happens only with the bootstrap feature turned on. This feature was enabled in mock 1.4.0, but I quickly disabled it in 1.4.1. So it should not happen right now unless you explicitly enable it. Therefore it is not the priority for me right now.

from mock.

Ok understood, so to reiterate:

1. 1.4.0 enabled the bootstrap feature by default and you backtracked from that in 1.4.1 and now it is off for the time being
2. This bug is affected by the bootstrap feature being on/off and it should work ok now, but should boostrapping be turned on later, it would then break again

Is that correct?

from mock.

This issue will have to be resolved before this feature will be enabled on again. Definitelly

from mock.