Bug 1043621 - bogus date in %changelog
Summary: bogus date in %changelog
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pygobject3
Version: 7.0
Hardware: All
OS: All
unspecified
low
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-16 18:24 UTC by jcpunk
Modified: 2019-10-25 14:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-25 14:59:39 UTC
Target Upstream Version:


Attachments (Terms of Use)
bash script to fix bogus weekdays in rpm spec files. (2.23 KB, application/x-shellscript)
2014-02-14 07:06 UTC, Edward J. Huff
no flags Details

Description jcpunk 2013-12-16 18:24:05 UTC
Description of problem:The changelog contains bad date range


Version-Release number of selected component (if applicable):3.8.2-2.1.el7

How reproducible: 100%


Steps to Reproduce:
1. rpmbuild --rebuild <SRPM>
2.
3.

Actual results:
warning: bogus date in %changelog: Thu Aug 19 2011 John (J5) Palmieri <johnp> - 2.90.2-2
warning: bogus date in %changelog: Thu Aug 22 2011 John (J5) Palmieri <johnp> - 2.90.2-3


Expected results:
valid dates

Additional info:

Comment 2 Edward J. Huff 2014-02-14 07:06:24 UTC
Created attachment 863127 [details]
bash script to fix bogus weekdays in rpm spec files.

This script automatically corrects bogus weekdays in spec files, generating a changelog entry and adding a line after the bogus date noting the original date. (The weekday might have been correct and the day of the month wrong). The input file is copied to a backup file, and a diff is printed.

Comment 3 RHEL Program Management 2014-03-22 06:22:10 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.


Note You need to log in before you can comment on or make changes to this bug.