hi,
> ...
All the above^ is an interesting/informative read.
On 7/3/20 2:31 AM, Nicolas Mailhot via devel wrote:
> The requester is clearly attempting the second approach.
Well, not explicitly. I'm not requesting any _specific_ approach.
The goal is simply to 'build it here (locally, via mock), then build it there
(remotely, on COPR)'. And have the results be the same.
My general question is why what works in _mock_ here, locally, fails to work
similarly on COPR. Not just rpmbuild, which I understand _is_ well integrated
into my local env, but the supposedly _isolated_, basic mock env.
And if it inherently does/can work similarly, what specifically I need to
do/configure to get there.
On 7/2/20 10:26 PM, Pavel Raiskup wrote:
> and it needs to have the internet enabled at that time to
> get the contents of %commitX.
>
> So the alternative local mock command would be:
>
> mock --buildsrpm --spec nginx.spec --enable-network
in both cases, networking _is_ 'on'
Here, the mock env is setup as
cat /etc/mock/site-defaults.cfg
...
config_opts['rpmbuild_networking'] = True
config_opts['chroot_additional_packages'] = 'git'
...
mock --init
and the copr build as,
copr-cli create \
--chroot fedora-32-x86_64 \
--multilib off \
--description "x" \
--instructions "x" \
--use-bootstrap on \
--enable-net on \
--unlisted-on-hp on \
<project>
On 7/3/20 12:01 AM, Nicolas Mailhot wrote:
> You added some processing that depends on the git command (that
> forgemeta does not use) but forgot to BuildRequire the package
> providing that command.
It's _clearly_ already added in my referenced spec:
BuildRequires: git
On 7/3/20 1:23 AM, Pavel Raiskup wrote:
> I'm afraid that for building the src.rpm simply adding git to BuildRequires
> will not help.
Agreed; it does not.
On 7/3/20 12:01 AM, Nicolas Mailhot wrote:
> dead stupid (so stupid
Let's chalk that up this time to 'lost in translation', shall we?
> As stated before forgemeta does not depend on the git (or hg, or svn,
> or…) command, it’s a pure URL munger, so it won’t pull in your scm of
> choice in the buildroot.
>
> Presumably your workflow is so git oriented your local setup always has
> git installed.
I've been working with Fedora for < 2 weeks now; i.e., not much 'baggage' at
all.
There _is_ no "so oriented" or "always" workflow. ALL of what I'm attempting
to do is simply based on new/fresh eyes reading the docs provided, and giving
it a whirl.
I'll certainly acknowledge the _hope_ that there's something similar to my
prior build env's 'Source Services' capability,
https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.source_service.html
doable here.
On 7/2/20 10:26 PM, Pavel Raiskup wrote:
> So basically it needs to have the /bin/git installed in the chroot (it is
> not by default),
git _was_ trivially added to the local mock chroot, for its use, with obvious
success, in the local mock build of the spec.
COPR uses mock.
So far, I have not seen how that's to be similarly done for the COPR env.
Is is possible to, similarly, add git to the COPR mock env?
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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
