Re: Reverting to an old version in a branch
So,if I got the point, what I should do is (x being the release number
of the current package)
* creating a new package for F-16 only, containing the latest version
compatible with such release of Fedora, with release number (x+1);
* incrementing the release number of the current package to (x+2) and
load it into the F-17, F-18 and devel branches only. (By the way,
should the changelog of this release contain also an entry for the
(x+1) release or should this be omitted?)
Is this right? Thank you.
Regards,
M.M. (odysseus)
2012/11/29 Nicolas Chauvet <kwizart(a)gmail.com>:
2012/11/25 M.M. <hal8600(a)hotmail.it>
>
> The package "gnome-shell-extension-weather" is currently in the f-16, f-17
> and f-18 branches.
> From a recent update onwards, it seems that the extension has lost
> compatibility with Fedora 16 (please see this bug report:
> https://bugzilla.rpmfusion.org/show_bug.cgi?id=2564 ).
>
> Is it possible to revert the package to an old build (the last compatible
> with F16) in the f-16 branch and then make such branch (and only that) stick
> to that version in the future?
> If so, how to do that?
You need to provide an update in F-16 that will upgrade the previous package
from RPM perspective, but downgrade to the appropriate software version at
the same time.
Next, you need to take into account that a package in F-17, always need to
be higher than one in F-16.
You can use rpmdev-vercmp to verify that behaviour.
Thx.
Nicolas (kwizart)