1RPM::Grill::Plugin::SpeUcsFeirleCSoanntirtiyb(u3t)ed PerRlPMD:o:cGurmielnlt:a:tPiloungin::SpecFileSanity(3)
2
3
4

NAME

6       FIXME - FIXME
7

SYNOPSIS

9           use Fixme::FIXME;
10
11           ....
12

DESCRIPTION

14       FIXME fixme fixme fixme
15

CONSTRUCTOR

17       FIXME-only if OO
18
19       new( FIXME-args )
20           FIXME FIXME describe constructor
21

METHODS

23       FIXME document methods
24
25       method1
26           ...
27
28       method2
29           ...
30

EXPORTED FUNCTIONS

EXPORTED CONSTANTS

EXPORTABLE FUNCTIONS

FILES

DIAGNOSTICS

36       MacroSurprise
37           Did you know that RPM expands macros even inside comments?
38
39           Sometimes this is OK: %{name}, %{version}. But when %{foo} is a
40           multi-line macro, or %if, or %patch, this can cause unpleasant
41           surprises. As of May 2012 this test will only trigger on a certain
42           well-defined list of hazardous macros: patch, if, else, endif,
43           define. (It used to trigger on %anything, but that gave way too
44           much noise). This list may need to be refined over time.
45
46           Recommendation: Double-percent all macros in comments: %%{name}
47
48       ChangelogMissing
49           There is no %changelog section in your specfile. Can this happen?
50
51       ChangelogEmpty
52           The %changelog section in your specfile is empty. This error
53           doesn't sound like it could happen, but it does.
54
55       ChangelogOnlyNeedsVR
56           You included your package name in the %changelog entry. All you
57           need is the Version-Release.  See
58           <http://fedoraproject.org/wiki/Packaging:Guidelines#Changelogs>
59
60       ChangelogCruftInVersion
61           The version string in your first %changelog entry includes
62           unnecessary cruft.
63
64       ChangelogWrongEpoch
65           You included an epoch in your %changelog entry, but it's the wrong
66           one.
67
68       ChangelogUnexpectedEpoch
69           You included an epoch in your %changelog entry, but the specfile
70           itself does not define an Epoch.
71
72       ChangelogBadVersion
73           The version string in your first %changelog entry does not match
74           the one defined in the package specfile.
75
76       ChangelogBadRelease
77           The release string in your first %changelog entry does not match
78           the one defined in the package specfile.
79
80       ChangelogWeirdLine
81           I could not parse the first line of the %changelog section in your
82           specfile.  See
83           <http://fedoraproject.org/wiki/Packaging:Guidelines#Changelogs>
84
85       ChangelogLeadingWhitespace
86           You've indented a line in a changelog message, perhaps for clarity,
87           but that indentation will not survive rpmbuild. Customers who run
88           "rpm -q --changelog" will see that line without any leading
89           whitespace.  This is probably not a cataclysmic source of
90           confusion, but please check anyway.
91
92       ChangelogMacros
93           Percent signs in .spec files get expanded as macros. When you write
94           "Replaced /bin with %{bindir}", "rpm -q --changelog" will show
95           "Replaced /bin with /bin". Confusing. The excerpt in the gripe
96           message shows you what you wrote and what customers will see.
97
98           Solution: double up percent signs: %%{foo}.
99
100       ChangelogWrongWeekday
101           A specfile %changelog entry has a mismatch between the weekday and
102           the date. There is no automated way to know which is correct.  This
103           needs human intervention.
104

SEE ALSO

106       L<>
107

AUTHOR

109       Ed Santiago <santiago@redhat.com>
110

POD ERRORS

112       Hey! The above document had some coding errors, which are explained
113       below:
114
115       Around line 616:
116           An empty L<>
117
118
119
120perl v5.30.0                      2019-07-R2P6M::Grill::Plugin::SpecFileSanity(3)