copr-devel December 2015

copr-devel@lists.stg.fedorahosted.org

6 participants
6 discussions

How to make sure rpms to be signed on copr?
by Hiroaki Nakamura 15 Jan '16

15 Jan '16

Hello. How to make sure rpms to be signed on copr? I tried to build my Python2 rpm. It was built successfully but is was not signed. https://copr.fedoraproject.org/coprs/hnakamur/hnscl-python2-python/ I built other rpms and they are signed. https://copr.fedoraproject.org/coprs/hnakamur/varnish-head/ https://copr.fedoraproject.org/coprs/hnakamur/libvmod-header/ I don't why my Python2 rpm was not signed. I'd like to know the way to make sure rpms are signed on copr. By the way, thanks for a great service like copr! It is very useful! Best regards, Hioraki Nakamura

3 7

disable networking in Copr by default
by Pavel Raiskup 07 Jan '16

07 Jan '16

Just to be more pedantic and probably bit more secure, what about making networking in copr opt-in (at least for new projects)? If build of my package used internet arbitrarily, I would be warned very early.. Also, in Koji we also do not have networking, so we can faster teach (future) Fedora packagers. Thanks for considering, Pavel

3 3

(no subject)
by Pavel Raiskup 21 Dec '15

21 Dec '15

While trying to rebiuld packages from Copr's git in Copr, I'm facing several issues. Probably the first batch of patches is attached: [PATCH 1/3] [cli] fix packaging for epel-6+ and fedora-22+ [PATCH 2/3] [python] fixes for epel-6+ and fedora-22+ [PATCH 3/3] [backend] fix packaging issues in epel-7+ The status is available here: https://copr.fedoraproject.org/coprs/praiskup/copr-respin-test-2015-12-20/m… Pavel

2 4

[PATCH] [backend] fix specfile for rpmlint warnings
by Pavel Raiskup 21 Dec '15

21 Dec '15

--- backend/copr-backend.spec | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/backend/copr-backend.spec b/backend/copr-backend.spec index 559a97b..e5e1b92 100644 --- a/backend/copr-backend.spec +++ b/backend/copr-backend.spec @@ -171,7 +171,7 @@ cp -a conf/logstash/lighttpd.pattern %{buildroot}%{_datadir}/logstash/patterns/l #doc -# cp -a documentation/python-doc %{buildroot}%{_pkgdocdir}/ +# cp -a documentation/python-doc %%{buildroot}%%{_pkgdocdir}/ cp -a conf/playbooks %{buildroot}%{_pkgdocdir}/ install -d %{buildroot}%{_pkgdocdir}/examples/%{_sysconfdir}/logstash.d @@ -240,7 +240,7 @@ useradd -r -g copr -G lighttpd -s /bin/bash -c "COPR user" copr %files doc %license LICENSE %doc -# %{_pkgdocdir}/python-doc +# %%{_pkgdocdir}/python-doc %{_pkgdocdir}/ %exclude %{_pkgdocdir}/lighttpd %exclude %{_pkgdocdir}/playbooks -- 2.5.0

1 0

Extraction error on ppc64
by Richard Shaw 15 Dec '15

15 Dec '15

All builds completed fine for i686 and x86_64 but all my ppc64 builds failed, looking at one I saw this: [ 69%] Performing download step (verify and extract) for 'wsjtx' cd /builddir/build/BUILD/wsjtx-1.6.0/build/wsjtx-prefix/src && /usr/bin/cmake -P /builddir/build/BUILD/wsjtx-1.6.0/build/wsjtx-prefix/src/wsjtx-stamp/verify-wsjtx.cmake -- verifying file... file='/builddir/build/BUILD/wsjtx-1.6.0/src/wsjtx.tgz' -- verifying file... done cd /builddir/build/BUILD/wsjtx-1.6.0/build/wsjtx-prefix/src && /usr/bin/cmake -P /builddir/build/BUILD/wsjtx-1.6.0/build/wsjtx-prefix/src/wsjtx-stamp/extract-wsjtx.cmake -- extracting... src='/builddir/build/BUILD/wsjtx-1.6.0/src/wsjtx.tgz' dst='/builddir/build/BUILD/wsjtx-1.6.0/build/wsjtx-prefix/src/wsjtx' -- extracting... [tar xfz] CMake Error: Problem with archive_write_header(): Can't create 'wsjtx/WSPRBandHopping.hpp' CMake Error: Current file: wsjtx/WSPRBandHopping.hpp CMake Error: Problem extracting tar: /builddir/build/BUILD/wsjtx-1.6.0/src/wsjtx.tgz -- extracting... [error clean up] CMake Error at wsjtx-stamp/extract-wsjtx.cmake:33 (message): error: extract of '/builddir/build/BUILD/wsjtx-1.6.0/src/wsjtx.tgz' failed CMakeFiles/wsjtx-build.dir/build.make:86: recipe for target 'wsjtx-prefix/src/wsjtx-stamp/wsjtx-download' failed Any idea? Thanks, Richard

2 1

[Patch] Adds MANIFEST.in in python/ and cli/
by Sergio Oliveira 09 Dec '15

09 Dec '15

Building packages using setup.py would fail because setup.py now depends on .spec files and specs weren't available on sdist. By adding the MANIFEST.in in both packages the spec will be included in the source distributions. Cheers, -- Sergio Oliveira

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel December 2015