On 12/07/2019 05:21, Matthias Bach wrote:
Hi,
Am Donnerstag, 11. Juli 2019, 15:52:57 CEST schrieb Maurizio Galli (MauG):
Also, because the old and new package share the same version (no update upstream, only the package), the old package does not seem to be replaced by the new renamed one. Does this mean that will have to delete the old package from Factory immediately to avoid duplicates? Is there a nicer way to deal with it?
Isn't this exactly what the package version, or "Release" as it is called in the spec file, is for; to indicate that the package changed despite the upstream still being the same?
I know the build service does magic things to the Release field. But AFAIR it only ever increments, so bumping it sufficiently in the spec of the new package should give you the desired result.
Almost, except obs built packages also contain a "build" number that increments with each build of the same version so you generally don't have to worry about it (unless your swapping between repo's where the build number in the "old" repo can be higher then the one in the "new" repo). -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org