[opensuse-packaging] Create a rpm-spec which forces a higher version to be replaced be a lower version
Hello! I have the following problem: A package which has been versioned without number but with a date as version number ( mediawiki-math-1401961173 ) starting some month ago, the package has now a "real" version number (1.26). I'd like to use the new number, but I do not see how I could force a update then... Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Fri, 2015-11-27 at 11:21 +0100, Johannes Weberhofer wrote:
Hello!
I have the following problem: A package which has been versioned without number but with a date as version number ( mediawiki-math- 1401961173 ) starting some month ago, the package has now a "real" version number (1.26). I'd like to use the new number, but I do not see how I could force a update then...
There is only one method, which we do not employ in openSUSE: rpm epoch. As our policy is to use 'zypper dup' between releases and openSUSE Tumbleweed snapshots, you don't even have to care that much: zypper will perform an auto-downgrade to the 'real' version once the dated ones are no longer in the configured repositories. Cheers, Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 27.11.2015 um 13:07 schrieb Dominique Leuenberger / DimStar:
On Fri, 2015-11-27 at 11:21 +0100, Johannes Weberhofer wrote:
Hello!
I have the following problem: A package which has been versioned without number but with a date as version number ( mediawiki-math- 1401961173 ) starting some month ago, the package has now a "real" version number (1.26). I'd like to use the new number, but I do not see how I could force a update then...
There is only one method, which we do not employ in openSUSE: rpm epoch.
Why don't we emply the only method there is? Just wondering, because it would make life much easier if we would not need to depend on a particular implementation of a packagemanager frontend. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Fri, Nov 27, 2015 at 5:50 PM, Stefan Seyfried
Just wondering, because it would make life much easier if we would not need to depend on a particular implementation of a packagemanager frontend.
Because it makes life easier for users, but makes it harder for packagers? :) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Friday 27 November 2015, 15:50:54 wrote Stefan Seyfried:
Am 27.11.2015 um 13:07 schrieb Dominique Leuenberger / DimStar:
On Fri, 2015-11-27 at 11:21 +0100, Johannes Weberhofer wrote:
Hello!
I have the following problem: A package which has been versioned without number but with a date as version number ( mediawiki-math- 1401961173 ) starting some month ago, the package has now a "real" version number (1.26). I'd like to use the new number, but I do not see how I could force a update then...
There is only one method, which we do not employ in openSUSE: rpm epoch.
Why don't we emply the only method there is?
Just wondering, because it would make life much easier if we would not need to depend on a particular implementation of a packagemanager frontend.
it just increases the problem to the next level. Once epoch is more known, people will misuse it for example as repository priority workaround and set always Epoch:1000 to have their package first. Just an evil example ;) -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Friday 2015-11-27 16:22, Adrian Schröter wrote:
Just wondering, because it would make life much easier if we would not need to depend on a particular implementation of a packagemanager frontend.
it just increases the problem to the next level. Once epoch is more known, people will misuse it for example as repository priority workaround and set always Epoch:1000 to have their package first. Just an evil example ;)
They can already edit Version and get the same effect... -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hello, Am Freitag, 27. November 2015 schrieb Johannes Weberhofer:
I have the following problem: A package which has been versioned without number but with a date as version number ( mediawiki-math-1401961173 ) starting some month ago, the package has now a "real" version number (1.26). I'd like to use the new number, but I do not see how I could force a update then...
I'd try (untested, adjust the number as needed) Obsoletes: mediawiki-math > 1401960000 Note that you'll need to remove that again once mediawiki-math reaches version 1401960000.1 ;-) Regards, Christian Boltz -- Development is still fast. First I said it went from Ferrari to Lada, but that is not true. It went from Space Shuttle to Ferrari... slower...but still extremely fast. [Azerion in opensuse-factory] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 27.11.2015 um 13:42 schrieb Christian Boltz:
Hello,
Am Freitag, 27. November 2015 schrieb Johannes Weberhofer:
I have the following problem: A package which has been versioned without number but with a date as version number ( mediawiki-math-1401961173 ) starting some month ago, the package has now a "real" version number (1.26). I'd like to use the new number, but I do not see how I could force a update then...
I'd try (untested, adjust the number as needed)
Obsoletes: mediawiki-math > 1401960000
Note that you'll need to remove that again once mediawiki-math reaches version 1401960000.1 ;-)
Regards,
Christian Boltz
I had the same Idea; but unfortunately:
sudo rpm -Uhv /var/tmp/build-root/openSUSE_13.2-x86_64/home/abuild/rpmbuild/RPMS/noarch/mediawiki-math-1.26.0-0.noarch.rpm Preparing... ################################# [100%] package mediawiki-math-1401961173-4.1.noarch (which is newer than mediawiki-math-1.26.0-0.noarch) is already installed
Thanks, Christian, for your suggestion! Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 27.11.2015 um 11:21 schrieb Johannes Weberhofer:
Hello!
I have the following problem: A package which has been versioned without number but with a date as version number ( mediawiki-math-1401961173 ) starting some month ago, the package has now a "real" version number (1.26). I'd like to use the new number, but I do not see how I could force a update then...
That's what rpm epoch was designed for. For unknown reasons, in the SUSE ecosystem this seems to be frowned upon. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Stefan Seyfried wrote:
Am 27.11.2015 um 11:21 schrieb Johannes Weberhofer:
Hello!
I have the following problem: A package which has been versioned without number but with a date as version number ( mediawiki-math-1401961173 ) starting some month ago, the package has now a "real" version number (1.26). I'd like to use the new number, but I do not see how I could force a update then...
That's what rpm epoch was designed for.
For unknown reasons, in the SUSE ecosystem this seems to be frowned upon.
http://lists.opensuse.org/opensuse-packaging/2009-01/msg00090.html cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 27.11.2015 um 11:21 schrieb Johannes Weberhofer:
Hello!
I have the following problem: A package which has been versioned without number but with a date as version number ( mediawiki-math-1401961173 ) starting some month ago, the package has now a "real" version number (1.26). I'd like to use the new number, but I do not see how I could force a update then...
Best regards, Johannes
I have found a solution which works: As mediawiki-math requires mediawiki I have updated mediawiki to have an conflict with "mediawiki-math > 20000000". Therefore zypper asks automatically for downgrading. Best regrads, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (8)
-
Adrian Schröter -
Andrei Borzenkov -
Christian Boltz -
Dominique Leuenberger / DimStar -
Jan Engelhardt -
Johannes Weberhofer -
Ludwig Nussel -
Stefan Seyfried