Page 1 of 1

Backporting from "cauldron" to "1"

PostPosted: Nov 23rd, '11, 11:53
by roadrunner
I recently requested a new package through Bugzilla and someone has now been kind enough to action my request. In order to test the new package, I had to install Cauldron and I find that the package works perfectly. I'm assuming that the package will now sit in Cauldron until the release of Mageia2 (May 2012?). My question is, is there a way of getting the package backported to Mageia1.

.\\artin

Re: Backporting from "cauldron" to "1"

PostPosted: Nov 23rd, '11, 12:29
by doktor5000
Yes, just add the Keyword "Backport" to the bug in question. This is to let the assigned packager know
that a backport is wanted. Still we need to wait until the necessary infrastructure for the backports has been set up,
you know our sysadmins are only humans, too ;)

Re: Backporting from "cauldron" to "1"

PostPosted: Nov 23rd, '11, 12:52
by roadrunner
OK, I've done that, thanks.

I wasn't aware of that useful feature, thanks for pointing it out.
This now leads to another question:

If I want a package backported that's already in Cauldron, can I just file a bug report and add the "Backport" keyword, even if I'm not actually reporting a bug. A typical example of this is hplip, where the version in Cauldron is newer than the version in "1" and it fixes a problem I'm having.

.\\artin

Re: Backporting from "cauldron" to "1"

PostPosted: Nov 23rd, '11, 13:36
by doktor5000
Well, this is not a good candidate for backports, as it directly affects the printing stack and is rather low-level.
What is the problem that is fixed with hplip-3.11.10 and not in Mageia 1? I could backport that fix only and include
it in the next hplip update for Mageia 1.

Re: Backporting from "cauldron" to "1"

PostPosted: Nov 23rd, '11, 14:01
by roadrunner
See my bug report here: https://bugs.mageia.org/show_bug.cgi?id=3382

.\\artin