Bug 2633 - Building mga1 updates breaks cauldron RPM changelogs due to wrong markrelease
Summary: Building mga1 updates breaks cauldron RPM changelogs due to wrong markrelease
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: BuildSystem (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
Depends on:
Blocks: 858
  Show dependency treegraph
Reported: 2011-09-05 20:21 CEST by Anssi Hannula
Modified: 2014-05-08 18:06 CEST (History)
2 users (show)

See Also:
Source RPM:
Status comment:


Description Anssi Hannula 2011-09-05 20:21:14 CEST
Markreleases for mga1 are done for the
cauldron tree, causing changelogs for cauldron releases to be grouped
according to submissions of mga1 updates_testing:

$ mgarepo rpmlog -s apache
* Thu Sep 01 2011 guillomovitch <guillomovitch> 2.2.20-1.mga2
+ Revision: 137516
- add missing LSB headers to htcacheclean init script

* Wed Aug 31 2011 guillomovitch <guillomovitch> 2.2.17-5.1.mga1
+ Revision: 137231
- new version
- drop suexec PATH patch

While in fact all of the above commit lines belong to 2.2.20-1.mga2, and there has been no 2.2.17-5.1.mga1 release in this tree at all.

The steps needed to fix this are:

1) disable markrelease on these submits
2) propedit the wrong markreleases (look for post-final mga1
markreleases in cauldron tree) to have invalid log msgs so that mgarepo
will ignore them
3) make the youri action run markrelease in the originating tree
instead of cauldron, or add making markrelease to the final update move (from _testing to updates) script
Jani Välimaa 2011-09-05 20:41:17 CEST

CC: (none) => jani.valimaa

Nicolas Vigier 2011-09-07 22:22:06 CEST

CC: (none) => boklm
Blocks: (none) => 858

Comment 1 Anssi Hannula 2011-12-07 20:55:52 CET
markrelease was disabled (as per (1) above) a few months ago by boklm:

I'm now looking into removing the wrong entries from /svn/packages/cauldron/foo/releases/bar and propediting the %repsys commits, so that the affected changelogs will be fixed.
Comment 2 Anssi Hannula 2011-12-08 00:57:39 CET
Now done (233 wrong entries were propedited and rm'd).

Closing this one, and opened bug #3666 for the wrong changelogs in stable updates.

Resolution: (none) => FIXED

Nicolas Vigier 2014-05-08 18:06:05 CEST

CC: boklm => (none)

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