Bug 505083 - rpm-add-change-log-entry date format rejected by rpmbuild
Summary: rpm-add-change-log-entry date format rejected by rpmbuild
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Novotny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-10 15:40 UTC by Miloslav Trmač
Modified: 2009-06-16 02:25 UTC (History)
3 users (show)

Fixed In Version: 22.3-12.fc11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-16 02:25:20 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
a new "utc" patch (1.46 KB, patch)
2009-06-11 09:19 UTC, Daniel Novotny 		no flags Details | Diff
View All

Description Miloslav Trmač 2009-06-10 15:40:59 UTC 
emacs-22.3-11.fc11.x86_64
rpm-build-4.7.0-1.fc11.x86_64

My locale configuration is LANG=cs_CZ.UTF-8

rpm-add-change-log-entry creates the following change log header:
> * St čen 10 2009 Miloslav Trmač <mitr> - 0.19.1-8

rpm rejects the date value:
> error: bad date in %changelog: St čen 10 2009 Miloslav Trmač <mitr> - 0.19.1-8

When I rewrite the date to use English words, it is accepted.
Comment 1 Daniel Novotny 2009-06-11 09:19:38 UTC 
Created attachment 347360 [details]
a new "utc" patch

seems the change ("utc" patch) in bug #489829 introduced this bug, updating the "utc" patch a bit (temporarily set (system-time-locale "C") before calling the date formatting function)
Comment 2 Daniel Novotny 2009-06-11 11:00:36 UTC 
fixed in rawhide, pushed into F11
Comment 3 Fedora Update System 2009-06-11 11:41:43 UTC 
emacs-22.3-12.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/emacs-22.3-12.fc11
Comment 4 Fedora Update System 2009-06-16 02:25:16 UTC 
emacs-22.3-12.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.