Merged #385.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/385#event-1457661587___
Rpm-maint mailing list
Nagware to effect policy is usually just an annoyance.
There are arguable cases (in renaming) where versionless or greater than are
perfectly sensible.
Also: Obsoletes: (after installation) are essentially Conflicts: and should be
treated similarly if you insist on adding nagware.
--
You are
These are pretty minor but they do all seem to me to be reasonably good ideas.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
ignatenkobrain commented on this pull request.
> @@ -277,6 +277,21 @@ rpmRC parseRCPOT(rpmSpec spec, Package pkg, const char
> *field, rpmTagVal tagN,
if (checkDep(spec, N, EVR, ))
goto exit;
+ if (nametag == RPMTAG_OBSOLETENAME) {
+ if (rpmCharCheck(spec,
Conan-Kudo requested changes on this pull request.
> @@ -277,6 +277,21 @@ rpmRC parseRCPOT(rpmSpec spec, Package pkg, const char
> *field, rpmTagVal tagN,
if (checkDep(spec, N, EVR, ))
goto exit;
+ if (nametag == RPMTAG_OBSOLETENAME) {
+ if
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/385
-- Commit Summary --
* rpmbuild: Error out if name Obsoletes have invalid characters
* rpmbuild: Warn out if version bound is not set for Obsoletes
* rpmbuild: Warn
