[Mageia-dev] Changelog entries - why not delimited by release/build?
Anssi Hannula
anssi at mageia.org
Fri Dec 21 20:51:44 CET 2012
21.12.2012 18:28, Christian Lohmaier kirjoitti:
> Hi *,
Hi!
> I wondered about this for quite some time.. When you view the
> changelog when updating your system, it is very hard to see what
> actually did change in that new release.
>
> For example the current cups update:
> Version available: 1.5.4-1.1.mga2
> currently installed: 1.5.4-1.mga2
>
> Changelog:
> * So 16 Dez 2012 13:00:00 CET oden <oden> 1.5.4-1.1.mga2
>
> + Revision: 331722
> - P103: attempt to fix #8318 (some usb printers stopped working)
> - 1.5.4
> - sync patches and some changes from cauldron
> - P102: security fix for CVE-2012-5519 (upstream, redhat)
> - merge spec file changes from fedora to deal with the new
> cups-files.conf file
>
> + guillomovitch <guillomovitch>
> - add upstream patches to fix #4673
>
> + tmb <tmb>
> - Require rpm-helper >= 0.24.8-1 for systemd support
>
> * Fr 27 Apr 2012 14:00:00 CEST tmb <tmb> 1.5.2-4.mga2
>
> + Revision: 233546
> [....]
>
> So what did actually change between 1.5.4-1.mga2 to 1.5.4-1.1.mga2?
>
> This time there is a hint about a major version bump in an update, so
> I can only assume the change is only "P103: attempt to fix #8318 (some
> usb printers stopped working)"
> (what does P# stand for btw? Is there a list of annotations used in changelogs?)
P103 means Patch #103 (it is in arbitrary number and not meaningful for
end users). No list that I know of.
> Why aren't changelogs separated by actual release?
This is not by intention, it is a bug in the build system:
https://bugs.mageia.org/show_bug.cgi?id=3666
--
Anssi Hannula
More information about the Mageia-dev
mailing list