Line 580:
Line 580:
===FIXING ERRORS IN SPEC FILES===
===FIXING ERRORS IN SPEC FILES===
−
Last one you will have to teach me is how to fix missing bug reference or spelling errors in spec file of packages already build
+
how to fix missing bug reference or spelling errors in spec file of packages already build
+
cvs update -dPA
+
then edit the .spec file in your favourite editor
+
cvs commit -m 'your description, eg correct spelling'
−
[12:13:40 PM] Ian Wells: Those are in the spec files
+
{{Tip box|You don't build anything, just commit to CVS. The next build will then publish your change. If very important you can force a build, but that needs the version updated and a changelog added to indicate why.}}
−
[12:13:52 PM] Ian Wells: So...
−
[12:14:19 PM] Ian Wells: cvs update -dPA to get the latest for that package
−
[12:14:33 PM] Ian Wells: then edit the .spec file in your favourite editor
−
[12:15:08 PM] Ian Wells: then cvs commit -m '' <-- your description, eg correct spelling
−
[12:15:23 PM] Ian Wells: You don't build anything, just commit to CVS
−
[12:15:33 PM] Ian Wells: The next build will then publish your change
−
[12:16:29 PM] Ian Wells: If very important you can force a build, but that needs the version updated and a changelog added to indicate why.
−
[12:16:52 PM] xyz burnat: Great, I understand. Many thanks, We are getting somewhere on all fronts.
EXAMPLE:
EXAMPLE:
Line 677:
Line 672:
* Tue Apr 23 2013 xyz burnat <devlist@burnat.com> 0.84-4.sme
* Tue Apr 23 2013 xyz burnat <devlist@burnat.com> 0.84-4.sme
−
- qpsmtpd allows the spamassassin plugin to read the size limit
+
- qpsmtpd allows the spamassassin plugin to read the size limit
−
+
===REVERSE CHANGES MADE PREVIOUSLY===
===REVERSE CHANGES MADE PREVIOUSLY===
* Edit specfile as usual, except you delete patch references as applicable.
* Edit specfile as usual, except you delete patch references as applicable.