Hello, please, see the answer below...
On Tue, Jun 27, 2017 at 11:41 AM, jeandet <alexis.jeandet(a)member.fsf.org>
wrote:
Hello Michal,
Thank you for your help, I'm not a RPM/Mock/Copr pro, you confirm that my
spec file is Ok, and that copr should use spectool to fetch sources?
If yes I'll be happy to submit the request.
Then I didn't find examples of packages using github on copr, is there
people doing this?
Hello, your specfile probably would be ok if we supported spectool. I think
we will but a user request at bugzilla or on pagure (
) would help ;). You can e.g. see
Best regards,
Alexis.
Le mardi 27 juin 2017 à 11:13 +0200, Michal Novotny a écrit :
COPR does not currently use spectool so the required sources are not
downloaded for you as in the command-line example you provided. You can
file a request here:
https://bugzilla.redhat.com/
enter_bug.cgi?product=Copr so that we start to use spectool :) (the RFE
will be welcome).
On Sun, Jun 25, 2017 at 7:22 PM, jeandet <alexis.jeandet(a)member.fsf.org>
wrote:
Hi,
I'm quite lost here, I followed the doc here:
https://fedoraproject.org/wiki/Packaging:SourceURL?rd=Packag
ing/SourceURL#Git_Hosting_Services
My spec file is here:
https://github.com/jeandet/vera-rpm
Does not build on copr:
https://copr.fedorainfracloud.org/coprs/ajeandet/SciQLop/build/570647/
On my machine it works with:
spectool -g -R vera.spec && rpmbuild -bs ./vera.spec && rpmbuild -bb
./vera.spec
With mock:
sudo mock -r fedora-25-x86_64 --scm-enable --scm-option method=git
--scm-option package=vera --scm-option git_get='git clone
https://github.com/jeandet/vera-rpm' --scm-option --spec='vera.spec'
--scm-option branch=master --scm-option write_tar=True -v
I get errors on checkout:
DEBUG: Executing command: ['git', 'checkout', 'master'] with env
environ({'HOME': '/root', 'DISPLAY': ':1',
'USERHELPER_UID': '0', 'SHELL':
'/bin/bash', 'TERM': 'xterm-256color', 'LOGNAME':
'root', 'LANG':
'fr_FR.UTF-8', 'PATH': '/usr/sbin:/usr/bin:/sbin:/bin:/root/bin',
'USER':
'root'}) and shell False
ERROR: Exception occurred in preexec_fn.
Traceback (most recent call last):
File "/usr/libexec/mock/mock", line 886, in <module>
main()
File "/usr/lib/python3.5/site-packages/mockbuild/trace_decorator.py",
line 89, in trace
result = func(*args, **kw)
File "/usr/libexec/mock/mock", line 701, in main
run_command(options, args, config_opts, commands, buildroot, state)
File "/usr/lib/python3.5/site-packages/mockbuild/trace_decorator.py",
line 89, in trace
result = func(*args, **kw)
File "/usr/libexec/mock/mock", line 720, in run_command
scmWorker.get_sources()
File "/usr/lib/python3.5/site-packages/mockbuild/trace_decorator.py",
line 89, in trace
result = func(*args, **kw)
File "/usr/lib/python3.5/site-packages/mockbuild/scm.py", line 102, in
get_sources
util.do(shlex.split(command), shell=False, cwd=self.src_dir,
env=os.environ)
File "/usr/lib/python3.5/site-packages/mockbuild/trace_decorator.py",
line 89, in trace
result = func(*args, **kw)
File "/usr/lib/python3.5/site-packages/mockbuild/util.py", line 532, in
do
preexec_fn=preexec,
File "/usr/lib64/python3.5/subprocess.py", line 676, in __init__
restore_signals, start_new_session)
File "/usr/lib64/python3.5/subprocess.py", line 1283, in _execute_child
raise child_exception_type(err_msg)
subprocess.SubprocessError: Exception occurred in preexec_fn.
Best regards,
Alexis.
Le mercredi 31 mai 2017 à 14:19 +0200, Michal Novotny a écrit :
The problem is with this line:
https://github.com/jeandet/ver
a/blob/master/vera.spec#L26, where you specify -n vera-master for
%autosetup. That's how directory is called in
https://github.com/jeandet/vera/archive/master.tar.gz. But in dist-git
the directory in the tarball is called vera++-1.3 (name of the package +
version). If the command was %autosetup -q, it would work. Are you able to
change the name of the directory in the archive at
https://github.com/jeandet/vera/archive/master.tar.gz?
clime
On Wed, May 31, 2017 at 11:59 AM, Michal Novotny <clime(a)redhat.com> wrote:
Hello, I am just deploying a new version of copr-dist-git that should fix
that particular problem so you can try that. There seems to be a problem
later on in building phase but we need to solve it afterwards. clime
On Wed, May 31, 2017 at 12:54 AM, Jeandet Alexis <
alexis.jeandet(a)member.fsf.org> wrote:
Hi,
I try to build a package from gtihub, it seems that git repo name must be
the same that package name in spec file?
Looking this build:
https://copr.fedorainfracloud.org/coprs/ajeandet/SciQLop/build/559025/
Looking the log here:
http://copr-dist-git.fedorainfracloud.org/per-task-logs/559025-f25.log
I tried on my desktop, I had to replace the following options:
package=vera by package=vera++
and
git_get=git clone --depth 1
https://github.com/jeandet/vera.git vera by
git_get=git clone --depth 1
https://github.com/jeandet/vera.git vera++
Did I miss something? On github, it seems that I can't call my repo
vera++, how can I override previous options?
Best regards,
Alexis.
_______________________________________________
copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org
_______________________________________________
copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org
_______________________________________________
copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org
_______________________________________________
copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org
_______________________________________________
copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org