[Mageia-dev] please stop doing "bugs" for updating magia 1

[Christian Lohmaier]

Hi Luis, *,

On Mon, Jan 9, 2012 at 5:47 AM, Luis Daniel Lucio Quiroz
<dlucio at okay.com.mx> wrote:
> AS i understand
> we are not a rolling distribution, so i dont get why i'm getting tickets to
> update release.
>
> What I mean, if you consider an update, like the one i did squid 3.1.12 to
> 3.1.15 please explain why.

No knowing squid's release-numbering-scheme, but update in micro
version usually are (fully compatible) bugfix releases, so why is an
explanation necessary? The explanation is "fixed bugs"

And using a fixed upstream release surely is preferable over adding
patches manually, isn't it?

> Otherwhise i gues it is better you cand use Mageia
> cauldron SRPM and do backport for  your self.

I understand a backport as adding a version with new features, usually
signalled by an update in either major or minor version. Those might
come with break in backwards or forwad-compatibility, so giving clear
reason why it should be backported surely is justified.

The lower in the stack (the more other packages depend on the package
in question), the more thought needs to be put into it. But if a
package that no other package depends on is concerned, then I'd say it
is up to the  packager to decide whether he/she will go through the
trouble of backporting it. If the spec is well written, and
configuring the package is "sane", then it is easy, if it is a
hacked-together spec/build-system it is hard.

But bugfixreleases (i.e. just micro version changed for most package
versioning schemes) should just consist of updating the source-tarball
(and maybe dropping some patches that found their way upstream and
rediff the remaining ones) and I don't understand your request to
"stop" those requests.

ciao
Christian