Red Hat Bugzilla – Bug 661568
Changes file is out of date
Last modified: 2012-10-30 23:10:55 EDT
Description of problem:
Changes are being kept in the spec file instead of the Changes file. The Change log needs to be moved from the spec file in to Changes, and the spec file change log should track rebuilds of the packages not code changes.
The current method means that people not using the spec file, Debian, Windows etc, don't get a useful change log.
Version-Release number of selected component (if applicable):
Migrated change log from spec fiel to Changes file, reformatted to CPAN standard.
Commit number r1677.
How would us QA monkeys reproduce this to verify it works for you?
I would assume the following:
* someone with access to a non-rpm based system.
* someone who knows the location of the spec and changes files.
Sorry for potentially asking n00b questions here, but I think it might help QA testers to replicate the issue and test for you.
1: Check that the spec file contains a small change log.
2: Check that the Changes file contains a list of changes for each version.
Note that the spec file here isn't used by Fedora so it doesn't need to have everything the Fedora spec file contains :)
I don't think there is much point in trying to verify every change is documented.
(In reply to comment #3)
> 1: Check that the spec file contains a small change log.
> 2: Check that the Changes file contains a list of changes for each version.
> Note that the spec file here isn't used by Fedora so it doesn't need to have
> everything the Fedora spec file contains :)
> I don't think there is much point in trying to verify every change is
execute the above.
Checked on publican-3.0-0.fc16.t180
1. publican.spec contains a change log.
2. publican/publican/Changes contains a revision history.