Mailinglist Archive: opensuse-packaging (267 mails)
| < Previous | Next > |
Re: [opensuse-packaging] RFC: Fonts Repo and Renaming Questions
- From: Vincent Untz <vuntz@xxxxxxxxxxxx>
- Date: Wed, 14 Dec 2011 09:17:21 +0100
- Message-id: <20111214081721.GS5871@vuntz.net>
Hi,
Le mercredi 14 décembre 2011, à 08:39 +0100, Thomas Schraitle a écrit :
The right thing is to live with the rpmlint warning; it will go away
once there is a new version.
FWIW, what we do in GNOME packages for this case is:
- until there's a new version out:
Provides: $oldname = %{version}
# FIXME: This causes a rpmlint warning; change <= to < once there's a new
upstream version
Obsoletes: $oldname <= %{version}
- when there's a new version out:
Provides: $oldname = %{version}
Obsoletes: $oldname < %{version}
Cheers,
Vincent
Vincent
--
Les gens heureux ne sont pas pressés.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
Le mercredi 14 décembre 2011, à 08:39 +0100, Thomas Schraitle a écrit :
Hi,
I tried to build it as you recommended, but another question turned
up...
[...]
2. Current version of Linux Libertine is 5.1.3. Which one is the
correct line and why:
a) Obsoletes: LinuxLibertine < 5.1.3
b) Obsoletes: LinuxLibertine < %{version}
When renaming a package with the same version, better to use "<=".
Otherwise the obsoletes won't be applied.
That is,
Obsoletes: LinuxLibertine <= 5.1.3
Provides: LinuxLibertine = %{version}
where 5.1.3 is the version you started rename. [...]
Currently, I have version 5.1.3_2011_06_21 and my SPEC file and added
the above condition. The SPEC file looks like this:
Name: linux-libertine-fonts
Version: 5.1.3
Obsoletes: LinuxLibertine <= 5.1.3
Provides: LinuxLibertine = %{version}
[...]
If I build it with osc I get the following warning:
RPMLINT report:
===============
linux-libertine-fonts.noarch: W: self-obsoletion LinuxLibertine <=
5.1.3 obsoletes LinuxLibertine = 5.1.3 The package obsoletes itself.
This is known to cause errors in various tools and should thus be
avoided, usually by using appropriately versioned Obsoletes and/or
Provides and avoiding unversioned ones.
This is somehow to be expected. :) If I change the "Obsoletes" condition
from "<=" to "<", the above warning disappears.
Now, the question is, is better to use "<" in this case or should I
change the version number? Which is the recommended strategy?
Just to make it right from the start. :)
The right thing is to live with the rpmlint warning; it will go away
once there is a new version.
FWIW, what we do in GNOME packages for this case is:
- until there's a new version out:
Provides: $oldname = %{version}
# FIXME: This causes a rpmlint warning; change <= to < once there's a new
upstream version
Obsoletes: $oldname <= %{version}
- when there's a new version out:
Provides: $oldname = %{version}
Obsoletes: $oldname < %{version}
Cheers,
Vincent
Vincent
--
Les gens heureux ne sont pas pressés.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
| < Previous | Next > |