When we import SRPMs from an external source (other distro, thirdparty repo), the changelog is stripped and added as http://svnweb.mageia.org/packages/misc/<pkgname>/log. It is then supposed to be appended to the changelog generated from our SVN history in http://svnweb.mageia.org/packages/cauldron/<pkgname>, but this seems not to be working anymore. According to Neal Gompa [0] it seems to be a regression from around July 2016. An example: - Upstream changelog for python-semantic_version, imported from Fedora 26 [1] - Changelog from a generated RPM as seen in Sophie [2]: Fri Feb 10 2017 akien <akien> 2.6.0-1.mga6 + Revision: 1085555 - import python-semantic_version from Fedora 26 This should be fixed asap, keeping old changelogs and attribution is a must have for a good collaboration with other distros on packaging. [0] https://ml.mageia.org/l/arc/dev/2016-09/msg01029.html [1] http://svnweb.mageia.org/packages/misc/python-semantic_version/log?view=markup [2] http://sophie.zarb.org/rpms/f5cf5bd037b2f161a944f6996c8b0cc2/changelog
Summary: Old logs from SRPM import are no longer appended to Mageia changelog => Regression: Old logs from SRPM import are no longer appended to Mageia changelog
CC: (none) => ngompa13
Do you mean that mgarepo have to be adapted to deal with the logs?
CC: (none) => yves.brungard_mageia
For Mageia 6 it's too late, but we really need to fix this before the next mass rebuild during Mageia 7 development (or ideally before cauldron reopens for Mageia 7, so that we produce correct package changelogs from the start).
Priority: Normal => High
Target Milestone: --- => Mageia 7
Papoteur checked, and the feature still works: there is a `-o` switch for `mgarepo rpmlog` which appends the old log: ``` $ mgarepo rpmlog -o python-semantic_version * Fri Feb 10 2017 akien <akien> 2.6.0-1.mga6 + Revision: 1085555 - import python-semantic_version from Fedora 26 * Sat Jan 28 2017 Igor Gnatenko <ignatenko@redhat.com> - 2.6.0-1 - Update to 2.6.0 - Make package to comply guidelines * Mon Dec 19 2016 Miro Hrončok <mhroncok@redhat.com> - 2.5.0-3 - Rebuild for Python 3.6 [...] ``` So it must be that the buildsystem no longer uses this option. Could a sysadmin check?
Hi, This is High priority bug for a good reason. Making Mageia even better than ever is best direction. In order to do right thing, this bug should be examined and fixed as soon as possible. Packagers, please make the status to Assigned when you are working on this. Feel free to reassign the bug if bad-triaged. Also, if bug is old, please close it. On October 1st 2020, we will drop priority to normal.