copr-dist-git hotfixes
by Michal Novotny
Hello,
there were some problems in the last release that we tackled yesterday and
today. Namely:
- wrong package version information displayed in UI
- extending Release with scm commit hash for MockSCM method (that was not
intended)
- packing sources for SCM methods did not work if repo contained a symlink
loop
These particular problems should be fixed now.
COPR team
6 years, 4 months
COPR deploy
by Michal Novotny
Hello, we have just deployed copr-frontend 1.117 and copr-dist-git 0.34.
The deploy is quite special because the packages' origin is Fedora
Infrastructure repositories for the first time and not @copr/copr repo as
it used to be. That is because we have switched to deploying COPR only from
official Fedora repositories (and from the dedicated Infrastructure
repositories for hotfixing) to be able to get Fedora Infrastructure support.
Apart from that, those two packages fix several bugs:
- *Bug 1473671* <https://bugzilla.redhat.com/show_bug.cgi?id=1473671> - Could
not parse /tmp/tmpGj3KZs/rust-bytecount.spec with error can't parse specfile
- *Bug 1473361* <https://bugzilla.redhat.com/show_bug.cgi?id=1473361> - New
SCM 2 build does not recall the 'Subdirectory' setting
- DistGitProvider has been reimplemented
- *Bug 1460399* <https://bugzilla.redhat.com/show_bug.cgi?id=1460399> - Build
breadcrumb incorrect for group project (yet to be closed)
- sqlalchemy deprecation warnings fixed
- monitor page fixed from jinja 2.9
- #106 <https://pagure.io/copr/copr/issue/106> Renaming a spec file in a
newer version causes the build to fail
And also SELinux was set to Enforcing on copr-dist-git machine...
We have also updated docs with respect to the SCM source type
https://docs.pagure.org/copr.copr/user_documentation.html#scm. There is one
bit missing and that is that copr-cli buildmock currently stands for SCM-2
and copr-cli buildtito currently stands for SCM-1.
Enjoy
COPR team
6 years, 4 months
New Release
by Michal Novotny
Hello,
we have just released copr-dist-git-0.33 and copr-frontend-1.116. These
packages are taking another step towards having a seamless integration with
SCM systems.
Mainly Tito method was renamed to SCM-1 source and MockSCM method was
renamed to SCM-2 source.
Backend for these two sources is already the same on copr-dist-git
(ScmProvider), only frontend forms are currently a bit different.
Note that we don't use Tito (nor mock-scm already for some time) so
tito.props is now just a silently ignored file.
What we did is that we defined two kinds of repositories: upstream and
downstream.
*Downstream repo:* is empty (except .spec, README, tito.props, hidden
files, currently) or contains at least one source or patch mentioned in the
specfile
*Upstream repo:* is not a downstream repo, meaning it contains something
significant not mentioned in .spec as source or patch
This definition allows us to auto-differentiate between the two kinds of
the repositories and do the right thing - either pack the repository
content as tarball with name specified in Source0 (upstream repo) or just
collect patches + sources there are already present (downstream repo).
There also might be just a spec file in the repository (or its
subdirectory) with the sources being downloaded from network completely
during rpm-build process.
This might sound complicated at first but really isn't. The idea is that
the system should do the right thing for you automatically.
We are very happy about these changes and further possibilities this brings
along and we hope you will be too.
COPR team
6 years, 4 months
New COPR release
by Michal Novotny
Hello,
we have just deployed copr-frontend-1.115 and copr-dist-git-0.32. There
should be little to none user-visible changes except bugs. What changed,
however, is that:
- we don't build srpms on copr-dist-git anymore, we only fetch sources,
spec, and patches an import them directly into dist-git
- that means we don't use Docker anymore on copr-dist-git
- TitoProvider and MockScm provider were unified into just one ScmProvider
internally
- that e.g. means you should be able to use SVN repos when building with
"UI Tito method" (when tested properly)
The next step is going to be pretty big as well even though code change
should be minimal this time. We are going to allow use-case described in
https://bugzilla.redhat.com/show_bug.cgi?id=1471066. Meaning, you can have
a Git (or SVN) repo with just a spec and patches. All the sources will be
then downloaded additionally during build.
Enjoy and we are sorry if we managed to break something - we will resolve
it as best and fast as we can
COPR team
6 years, 4 months
New release/deploy
by Michal Novotny
Hello,
we have just deployed copr-frontend-1.114, copr-dist-git-0.31, and
copr-rpmbuild 0.6 into production.
The updated COPR stack now offers quite a cool feature - building form a
.spec file directly by specifying URL or uploading it. You can even combine
.src.rpm and .spec files in the URL build method (the only one that
currently offers launching multiple builds at once).
copr-rpmbuild was updated to use %{disable_source_fetch 0} instead of
spectool for downloading additional sources. The macro has support directly
in rpm and is hence very preferred.
COPR team
6 years, 5 months