Re: preloading git needed for COPR builds using forgemeta/scm?
On Wednesday, July 1, 2020 6:22:31 PM CEST PGNet Dev wrote:
> You need to debug what is going on here, this is behind the
support edge
> for copr maintainers.
My _goal_ is to get local, mock & COPR builds generating the _same_ results.
Ideally, using the available forgemeta constructs.
I'm guessing that consistent build results is not an uncommon goals.
Definitely. But the forgemeta (triggering dynamic source downloads) thing
brings a lot of variables in to the game.
I need to revisit/rethink this. It seems that SRPMS are the
preferred 'input' ...
I don't want to claim `src.rpm` upload is preferred method (both methods
should just work), it is just more straightforward and there's less space
to make a mistake (both on build submitter and copr sides).
> I'd suggest you to compare the source RPMs you and copr
works with. Compare
> the local sources, spec files, etc.
Well THAT much i've been doing :-)
I mean, compare youre src.rpm with copr-generated src.rpm (rpmdiff, e.g.).
And any peculiarity.
> We can lend you some copr builder
> temporarily if you need it for debugging (so you can try the `copr-rpmbuild`
> commands manually).
lol. still a Fedora-land noob, here.
I have no idea what 'lend you some copr builder' means or entails! yet ...
I mean, if you (a) contact us off-list with your ssh key, (b) we can
allocate a copr builder VM for you, (c) setup the ssh access there for you
and (d) than throw the VM away when you don't need it. If it makes your
debugging easier...
Pavel