Bug 684641 - %changelog not in descending chronological order
%changelog not in descending chronological order
Status: CLOSED NOTABUG
Product: Publican
Classification: Community
Component: publican (Show other bugs)
2.5
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jeff Fearn
Ruediger Landmann
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-03-14 00:20 EDT by Tomas Dabašinskas
Modified: 2011-03-14 00:33 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-03-14 00:33:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Tomas Dabašinskas 2011-03-14 00:20:52 EDT
Hi, I'm getting an error %changelog not in descending chronological order when I run publican package -brew -lang en-US.
My Revision_History.xml:
<appendix>
 <title>Revision History</title>
 <simpara>
  <revhistory>
   <revision>
    <revnumber>8-2</revnumber>
    <date>2011-02-23</date>
    <author>
     <firstname>Tomas</firstname>
     <surname>Dabasinskas</surname>
     <email>tomas@redhat.com</email>
    </author>
    <revdescription><member>Week 8, build 2</member></revdescription>
   </revision>
   <revision>
    <revnumber>11-1</revnumber>
    <date>2011-03-14</date>
    <author>
     <firstname>Tomas</firstname>
     <surname>Dabasinskas</surname>
     <email>tomas@redhat.com</email>
    </author>
    <revdescription><member>Week 11, build 1</member></revdescription>
   </revision>
  </revhistory>
 </simpara>
</appendix>

If I move revision 11-1 above 8-2 it starts to work again. 
Can you please fix this so that date chronological order is determined by the revision number+date? Alternatively order from bottom of the file to the top.

Thanks
Comment 1 Jeff Fearn 2011-03-14 00:33:25 EDT
Publican does not change the order of the entries, they are expected to be in reverse chronological order. i.e. newest at top.

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