Bug 3666 - Subsequent stable updates have broken changelogs
Summary: Subsequent stable updates have broken changelogs
Status: ASSIGNED
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: BuildSystem (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: High major
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-08 00:56 CET by Anssi Hannula
Modified: 2017-03-14 14:43 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Anssi Hannula 2011-12-08 00:56:32 CET
Markreleases are not done for stable releases, causing the log messages for the releases to be merged under a single release in the rpm changelog.

e.g. if there are foo-1-1.1.mga1, foo-1-1.2.mga1, foo-1-1.3.mga1 in the updates repository, one gets

* Tue Oct 04 2011 foobar 11-1.3.mga1
- log messages of 1.1
- log messages of 1.2
- log messages of 1.3

  + baz <baz>
    - some other packager's log message for 1.2

  + foobaz <foobaz>
    - some third packager's log message for 1.3

etc.

Either the youri markrelease action should run markrelease in the originating tree
instead of cauldron, or add making markrelease to the final update move (from
_testing to updates) script.
The former approach would probably be better.
AL13N 2012-01-05 21:44:13 CET

Priority: Normal => High
CC: (none) => alien
Severity: normal => major

Nicolas Vigier 2012-01-13 23:02:04 CET

Status: NEW => ASSIGNED
CC: (none) => boklm

Nicolas Vigier 2014-03-24 10:47:22 CET

CC: boklm => (none)

Comment 1 Rémi Verschelde 2017-03-14 14:43:07 CET
Still valid today.

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