Packaging upstream with released tarballs in Copr
by Martin Novák
Hello,
It appears there's currently no option to build a package by just a
SPEC file which contains valid Source0 URL.
There's a project on GitHub with released tarballs, which I'd like to
package in Copr (and later in Fedora perhaps). The easiest method for
building that package in Copr for me would be to link a SPEC file from
my GitHub repository which I'd regulary update with new project
releases.*
Copr however offers only Tito and Mock SCM builds. From what I read,
it seems to me that both methods expect upstream and packaging files
to be in same repository. Is it true? If not, is there any example of
a Tito/MockSCM project linking external tarball which builds on Copr?
If yes, then maintaining a forked repository seems a bit cumbersome to
me. For each release Git tag in the upstream repository, I'd have to
create a new child tag for the release with a SPEC file and it doesn't
seem Tito automates this case so I'd have to cherry-pick the SPEC file
from my master branch and modify it. Of course I can automate this
with a script also in my master branch, but it feels "custom" to me.
Is there any proper method?
Even though I've researched the topic I'm still newbie to packaging
and Git so please have mercy.
Thank you.
* Or linking repository and specifying subdirectory and SPEC file name
so that the repository could contain more projects and a project
could contain patches.
7 years, 4 months
copr-dist-git moves to F23
by Miroslav Suchý
FYI - in case you operate your own Copr instance.
Currently our copr-dist-git is on EL7, but this means we are unable to
process weak and rich deps. So I moved our devel instance to F23 and it
work flawlessly. So after next deploy to production we will stop
actively support EL7 as target plaftorm for copr-dist-git and we will
focus on Fedora.
Mirek
7 years, 5 months
Failed builds in Copr
by Miroslav Suchý
I am very sorry.
Today Lubos K. accidentally submitted 10k packages to Copr. I wanted to run one simple SQL query to set all those builds
as failed. Unfortunately I made big mistake - I forgot to add one column to 'where' condition. As result of this error
*all* builds were marked as failed. All builds of all projects.
Mea culpa, mea maxima.
Fortunately we have backup, so we restored the state of the builds from this backup. This backup is few hours old. So if
you submitted your build between 06:00UTC and 14:00UTC your build will be still marked as failed no matter of what
actual result was.
This is "just" state in webUI db. It does not affect dnf repository of your project. Built rpms and logs are intact.
I apologize if this caused you some problems of confusion.
--
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
7 years, 5 months
Objective-C Build Not Working?
by Sean Callaway
Good afternoon, all.
I'm trying to build an SRPM in Copr and am getting an error stating that configure can't locate a working Objective-C runtime, although gcc-objc-4.8.5-4.el7.x86_64 and libobjc-4.8.5-4.el7.x86_64 are installed. I am rather new to this, so I might be missing something obvious, but I've poured over the logs and done my Googling.
======================================
From root.log.gz:
DEBUG util.py:417: Installed:
DEBUG util.py:417: check-devel.x86_64 0:0.9.9-5.el7 doxygen.x86_64 1:1.8.5-3.el7
DEBUG util.py:417: gcc-objc.x86_64 0:4.8.5-4.el7 openldap-devel.x86_64 0:2.4.40-9.el7_2
DEBUG util.py:417: re2c.x86_64 0:0.13.5-1.el7.centos
...
DEBUG util.py:417: libobjc.x86_64 0:4.8.5-4.el7
======================================
From build.log.gz:
checking how to run the Objective C preprocessor... gcc -E
checking objc/objc.h usability... yes
checking objc/objc.h presence... yes
checking for objc/objc.h... yes
checking if linking libobjc requires pthreads... no
checking for Apple Objective-C runtime... no
checking for GNU Objective C runtime... no
configure: error: Could not locate a working Objective-C runtime.
See `config.log' for more details.
error: Bad exit status from /var/tmp/rpm-tmp.BuTvvo (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.BuTvvo (%build)
Child return code was: 1
======================================
Any ideas?
Thanks!
- Sean Callaway
7 years, 5 months
