= Proposal topic =
FPC passed several guidelines today. A member asked that the non-unanimous decisions be sent to FESCo for review. Please review and decide whether to sent any of these back to FPC.
= Overview =
== Version free changelogs - https://fedorahosted.org/fpc/ticket/38 ==
FPC Decision: Documenting both scenarios (multiple entries with the same V-R, appending additional items to existing V-R entry) approved (as opposed to permitting version-less changelog entries, which was not) - (+1:6, 0:0, -1:1)
The FPC decided not to implement the original draft's suggestion to permit %changelog entries without NEVR strings. However, they did approve adding two other suggestions (by toshio and geppetto, both in the ticket) that document two methods for %changelog entries that do not result in a build. The one dissenting vote was cast to disagree with updating the guideline at all in this case, rather than in defense of the original suggestion. The objection was made on the basis of "adding reasons for confusion and inconstencies" which seems to go along with some previous questions by the objector as to whether commits to VCS should have a strict relationship to builds/package releases.
== Explain why rpmlint warns about executable files in %doc - https://fedorahosted.org/fpc/ticket/36 ==
FPC Decision: "%doc files must not have executable permissions" passes (+1:5, 0:0, -1:1)
FPC chose to make explicit in the Guidelines rpmlint's check for executable %doc files. This was based on two related factors. 1) executable doc files can bring in extra dependencies because the rpm automatic dep extraction will search all executable files. 2) auditing doc files for this would mean auditing the files with every new upstream release (otherwise a new dependency could easily creep in unnoticed). There was one dissenting vote. The example given by the dissenter was of a viewer specifically for the documentation shipped with the package. The objector argued that the viewer should be %doc as it wasn't useful for anything else and should be executable as it would need to be runnable to work. Other FPC members offered alternate ways to deal with this scenario but each side failed to convince the other.
= Logs =
Meeting logs for complete details are here:
FESCo has no objection to either of these.
If the changelog change causes problems for the kernel package we (or you guys) could revisit.
to comment on this ticket.