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.gi t 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.
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@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@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
The problem is with this line: https://github.com/jeandet/vera/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@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@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@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
Le mercredi 31 mai 2017 à 14:19 +0200, Michal Novotny a écrit :
The problem is with this line: https://github.com/jeandet/vera/blob/m aster/vera.spec#L26, where you specify -n vera-master for %autosetup. That's how directory is called in https://github.com/jeandet/vera/arc hive/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/m aster.tar.gz?
Ok I see, I don't think this is possible with github, and you can't call a repo with a '+' in the name :(.
clime
On Wed, May 31, 2017 at 11:59 AM, Michal Novotny clime@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@me mber.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/55 9025/ Looking the log here: http://copr-dist-git.fedorainfracloud.org/per-task-logs/559025-f2 5.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/v era.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@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave@lists.fedorahost ed.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.o rg
Hi, I'm quite lost here, I followed the doc here:https://fedoraproject.org/ wiki/Packaging:SourceURL?rd=Packaging/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 ht tps://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 FalseERROR: 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/vera/blob/m aster/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@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@me mber.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/55 9025/ Looking the log here: http://copr-dist-git.fedorainfracloud.org/per-task-logs/559025-f2 5.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@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave@lists.fedorahost ed.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.o rg
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@member.fsf.org wrote:
Hi,
I'm quite lost here, I followed the doc here: https://fedoraproject.org/wiki/Packaging:SourceURL?rd= Packaging/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/ vera/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@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@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@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
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? 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?pr oduct=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@member.fsf.o rg> wrote:
Hi,
I'm quite lost here, I followed the doc here: https://fedoraproject.org/wiki/Packaging:SourceURL?rd=Packaging/Sou rceURL#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/5706 47/
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://g ithub.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/vera/bl ob/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@redhat.co m> 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.jeande t@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/buil d/559025/ Looking the log here: http://copr-dist-git.fedorainfracloud.org/per-task-logs/55902 5-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@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave@lists.fedora hosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahost ed.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave@lists.fedorahosted .org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.o rg
Hello, please, see the answer below...
On Tue, Jun 27, 2017 at 11:41 AM, jeandet alexis.jeandet@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 ( https://pagure.io/copr/copr) would help ;). You can e.g. see https://copr.fedorainfracloud.org/coprs/g/mock/mock/ as an example project hosted on Github that uses MockSCM build method.
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@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@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@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@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
Le mardi 27 juin 2017 à 15:24 +0200, Michal Novotny a écrit :
Hello, please, see the answer below...
On Tue, Jun 27, 2017 at 11:41 AM, jeandet <alexis.jeandet@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 (https://pa gure.io/copr/copr) would help ;). You can e.g. see https://copr.fedor ainfracloud.org/coprs/g/mock/mock/ as an example project hosted on Github that uses MockSCM build method.
Thank you, I tried to fetch mock sources with 'spectool -g mock.spec' it doesn't work while building mock in mock works as expected.Is there something related to to %setup -q Vs %autosetup -n? BTW: https://bugzilla.redhat.com/show_bug.cgi?id=1465480
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.co m/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@member.f sf.org> wrote:
Hi,
I'm quite lost here, I followed the doc here: https://fedoraproject.org/wiki/Packaging:SourceURL?rd=Packaging /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://git hub.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/mas ter.tar.gz?
clime
On Wed, May 31, 2017 at 11:59 AM, Michal Novotny <clime@redha t.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.je andet@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/5 > 59025-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://gith > ub.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@lists.fedorahosted. > org > > To unsubscribe send an email to copr-devel-leave@lists.fe > dorahosted.org > >
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedora hosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave@lists.fedoraho sted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahost ed.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave@lists.fedorahosted .org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.o rg
I believe 'spectool -g mock.spec' does not do anything because Source is just a filename and not URL. The spec in the mock project does not include external resources. It relies on the sources being generated into the local directory by Tito method. Thanks a lot for filling the bug by the way. It was meanwhile incorrectly assigned to a different system component but well...what can you do. I made this new issue https://pagure.io/copr/copr/issue/96, where you can follow the progress.
clime
On Tue, Jun 27, 2017 at 10:40 PM, Jeandet Alexis < alexis.jeandet@member.fsf.org> wrote:
Le mardi 27 juin 2017 à 15:24 +0200, Michal Novotny a écrit :
Hello, please, see the answer below...
On Tue, Jun 27, 2017 at 11:41 AM, jeandet alexis.jeandet@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 ( https://pagure.io/copr/copr) would help ;). You can e.g. see https://copr.fedorainfracloud.org/coprs/g/mock/mock/ as an example project hosted on Github that uses MockSCM build method.
Thank you, I tried to fetch mock sources with 'spectool -g mock.spec' it doesn't work while building mock in mock works as expected. Is there something related to to %setup -q Vs %autosetup -n?
BTW: https://bugzilla.redhat.com/show_bug.cgi?id=1465480
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/en ter_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@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@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@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@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
Le mercredi 31 mai 2017 à 11:59 +0200, Michal Novotny a écrit :
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
Hi Michal, I'll try that tonight. thanks,Alexis.
On Wed, May 31, 2017 at 12:54 AM, Jeandet Alexis <alexis.jeandet@memb er.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/5590 25/ 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/ver a.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@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave@lists.fedorahosted .org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.o rg
copr-devel@lists.fedorahosted.org
-
jeandet -
Jeandet Alexis
-
Michal Novotny