Copr upgrade
by Jakub Kadlčík
Hi, today I am proud to announce new Copr release which brings us some very interesting new features and a lot of bugfixes.
Highlights:
- support building from PyPI via pyp2rpm (See some of your projects > "Builds" > "New Build" > "PyPI")
- support project forking [1]
- dockerized copr-backend for testing purposes [2]
Fixed bugs:
- 1314920 - No logs when Git or Mock SCM import fails
- 1314918 - Invalid edit of Package Git/SCM URL in group-owned copr causes error 404
- 1314917 - Cannot unset Git/SCM
- 1314369 - Exception raised when resubmitting Git&Tito build
- 1311777 - failure to delete project (and cancelled build)
- 1307239 - "inline HTMLis forbidden" -> "inline HTML is forbidden"
- 1306182 - A single failure makes the whole monitoring line red
- 1304012 - Can't see logs on failed build
- 1305754 - Incorrect dates are displayed on the build page
- 1318229 - Can't delete or remove a package definition
[1] http://frostyx.cz/posts/copr-forking-projects
[2] https://fedorahosted.org/copr/wiki/Contribute#Builddockerbackendimage
Jakub
7 years, 8 months
/bin/tar: Skipping to next header
by Antonio Trande
tar.gz archives cannot be unpacked with this error:
+ /bin/tar -xf -
+ /usr/bin/gzip -dc /builddir/build/SOURCES/MUMPS_5.0.1.tar.gz
/bin/tar: Skipping to next header
gzip: /builddir/build/SOURCES/MUMPS_5.0.1.tar.gz: unexpected end of file
/bin/tar: Exiting with failure status due to previous errors
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.39gzzd (%prep)
This does not happen on koji or in local.
Copr project: http://copr-fe.cloud.fedoraproject.org/coprs/sagitter/Ipopt-EPEL/build/16...
7 years, 8 months
no yum-plugin-copr for EL7
by Jean-Marc Liger
Hi,
I've tried to configure copr repositories directly with yum but there is
no yum-plugin-copr in EPEL-7.
Regards,
Jean-Marc
7 years, 8 months
"unknown" build cannot be deleted and never finishes
by Benji Wiebe
In my COPR project benjiwiebe/serverstuff, I have a build from 42 days
ago that never shows pending/importing/running, it always shows
"unknown". And I cannot delete it. The build number is 156906. I'd
appreciate if someone could help me with deleting it.
Thanks!
Benji
7 years, 9 months
dist-git build problem on epel-6-x86_64 chroot
by Jean-Marc Liger
Hy,
I'm facing the problem below on epel-6-x86_64 chroot for both from URL
and upload SRPM :
[2016-01-19 15:16:26,790][ INFO][PID:3241] Setting up builder: 172.25.94.167
[2016-01-19 15:16:27,991][ INFO][PID:3241] marking build dir with build_id,
[2016-01-19 15:16:27,992][ INFO][PID:3241] Start build: BuildJob<id: 154509, owner: jmliger, project: virt6-upstream, git branch: el6, git_hash: acef5efd6153aa8f9ea760f468333e65c9b46a4e, status: 3 >
[2016-01-19 15:16:27,993][ INFO][PID:3241] putting into minimal buildroot of epel-6-x86_64
[2016-01-19 15:16:28,902][ INFO][PID:3241] Cloning Dist Git repo jmliger/virt6-upstream/libvirt, branch acef5efd6153aa8f9ea760f468333e65c9b46a4e, hash el6
[2016-01-19 15:16:30,906][ ERROR][PID:3241] Failed to obtain srpm from dist-git
Traceback (most recent call last):
File "/usr/share/copr/backend/mockremote/builder.py", line 209, in download_job_pkg_to_builder
self.remote_pkg_path = list(results["contacted"].values())[0][u"stdout"].split("Wrote: ")[1]
IndexError: list index out of range
[2016-01-19 15:16:30,911][ ERROR][PID:3241] builder.build error building pkg `libvirt`: BuildError: Failed to obtain srpm from dist-git: ansible results {'dark': {}, 'contacted': {'172.25.94.167': {'cmd': 'rm -rf /tmp/build_package_repo && mkdir /tmp/build_package_repo && cd /tmp/build_package_repo && git clone http://copr-dist-git.fedorainfracloud.org/git/jmliger/virt6-upstream/libv... && cd libvirt && git checkout acef5efd6153aa8f9ea760f468333e65c9b46a4e && fedpkg-copr --dist el6 srpm', 'end': '2016-01-19 15:16:30.308282', 'stdout': 'Downloading libvirt-1.3.1.tar.gz\n\r 0.0%\r 100.0%\r######################################################################## 100.0%', 'changed': True, 'start': '2016-01-19 15:16:28.758321', 'delta': '0:00:01.549961', 'stderr': "Cloning into 'libvirt'...\nNote: checking out 'acef5efd6153aa8f9ea760f468333e65c9b46a4e'.\n\nYou are in 'detached HEAD' state. You can look around, make experimental\nchanges and commit them, and you can discard any commits you make in this\nstate without impacting any branches by performing another checkout.\n\nIf you want to create a new branch to retain commits you create, you may\ndo so (now or later) by using -b with the checkout command again. Example:\n\n git checkout -b <new-branch-name>\n\nHEAD is now at acef5ef... import_srpm\nerror: line 1800: Trigger fired by the same package is already defined in spec file: %post daemon-config-network\n\nerror: query of specfile /tmp/build_package_repo/libvirt/libvirt.spec failed, can't parse\n\nCould not execute srpm: Could not get n-v-r-e from '\\n\\n'", 'rc': 1, 'invocation': {'module_name': 'shell', 'module_complex_args': {}, 'module_args': u'rm -rf /tmp/build_package_repo && mkdir /tmp/build_package_repo && cd /tmp/build_package_repo && git clone http://copr-dist-git.fedorainfracloud.org/git/jmliger/virt6-upstream/libv... && cd libvirt && git checkout acef5efd6153aa8f9ea760f468333e65c9b46a4e && fedpkg-copr --dist el6 srpm'}, 'warnings': ['Consider using file module with state=absent rather than running rm']}}}
[2016-01-19 15:16:31,759][ INFO][PID:3241] End Build: BuildJob<id: 154509, owner: jmliger, project: virt6-upstream, git branch: el6, git_hash: acef5efd6153aa8f9ea760f468333e65c9b46a4e, status: 3 >
https://copr.fedoraproject.org/coprs/jmliger/virt6-upstream/builds/
Regards,
Jean-Marc LIGER
7 years, 9 months
Re: packages not signed in F24 are breaking copr builds
by Sérgio Basto
On Ter, 2016-03-08 at 14:49 +0100, Jakub Jelen wrote:
> On 03/08/2016 12:20 PM, Sérgio Basto wrote:
> >
> > Hello ,
> >
> > Packages not signed in F24 are breaking copr builds , but I need
> > copr
> > to test packages for F24 ...
> >
> > What should we do ? to workaround this problem.
> >
> > Thanks,
> Wait for tomorrow. The packages should be signed starting today, as
> it
> is the bodhi activation point.
Meanwhile , can't we hack copr , with gpgcheck=0 in Fedora 24 repos. It
will be much less stressful.
> It was asked many times here and around during last few days. Here
> [1],
> here [2] and may be more.
I can't see any workaround to manage builds on copr and this is broken
for a few days ...
> [1]
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproje
> ct.org/thread/A7VQ45QJW6CM5UW3PJKC5S2V7GIC32AH/
> [2]
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproje
> ct.org/thread/V5B6J4UNMOJIPC5J7O5VRW7PLGPCLGR3/
>
--
Sérgio M. B.
7 years, 9 months
