It would be nice to extend the %patchlist concept to have a %patchlist0
(patches to apply after extracting %source0), %patchlist1 (patches to apply
after extracting %source1), etc
That would get one step closer to deprecate the byzantine way %setup expects to
specify patch ordering in
ignatenkobrain commented on this pull request.
> @@ -228,12 +229,13 @@ static rpmRC doCheckBuildRequires(rpmts ts, rpmSpec
> spec, int test)
rpmps ps = rpmSpecCheckDeps(ts, spec);
if (ps) {
- rpmlog(RPMLOG_ERR, _("Failed build dependencies:\n"));
- rpmpsPrint(NULL, ps);
pmatilai commented on this pull request.
> @@ -228,12 +229,13 @@ static rpmRC doCheckBuildRequires(rpmts ts, rpmSpec
> spec, int test)
rpmps ps = rpmSpecCheckDeps(ts, spec);
if (ps) {
- rpmlog(RPMLOG_ERR, _("Failed build dependencies:\n"));
- rpmpsPrint(NULL, ps);
-
@ignatenkobrain pushed 1 commit.
cc8b9865b13bc06c96b404f12a9ea531e46ac4de Fix dynbrs with --quiet
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
