Re: [pacman-dev] Misleading info when epoch is used

2010-12-13 Thread Nagy Gabor
On Tue, Dec 7, 2010 at 11:44 PM, Dan McGee dpmc...@gmail.com wrote: On Tue, Dec 7, 2010 at 4:55 PM, Nagy Gabor ng...@bibl.u-szeged.hu wrote: In fact I don't like neither force nor epoch. Epoch is just a version prefix, why don't we let the packager to workaround this (KISS)? We can

Re: [pacman-dev] Misleading info when epoch is used

2010-12-13 Thread Dan McGee
On Mon, Dec 13, 2010 at 6:41 PM, Nagy Gabor ng...@bibl.u-szeged.hu wrote: On Tue, Dec 7, 2010 at 11:44 PM, Dan McGee dpmc...@gmail.com wrote: On Tue, Dec 7, 2010 at 4:55 PM, Nagy Gabor ng...@bibl.u-szeged.hu wrote: In fact I don't like neither force nor epoch. Epoch is just a version

Re: [pacman-dev] Misleading info when epoch is used

2010-12-09 Thread Pierre Schmitz
On Wed, 8 Dec 2010 21:23:22 +0100, Xavier Chantry chantry.xav...@gmail.com wrote: On Tue, Dec 7, 2010 at 11:44 PM, Dan McGee dpmc...@gmail.com wrote: On Tue, Dec 7, 2010 at 4:55 PM, Nagy Gabor ng...@bibl.u-szeged.hu wrote: Well, of course a new separator is not necessary, packager can do

Re: [pacman-dev] Misleading info when epoch is used

2010-12-08 Thread Sven-Hendrik Haase
On 08.12.2010 00:40, Dan McGee wrote: On Tue, Dec 7, 2010 at 5:40 PM, Allan McRae al...@archlinux.org wrote: On 08/12/10 08:45, Sven-Hendrik Haase wrote: On 07.12.2010 23:51, Nagy Gabor wrote: $ sudo pacman -Su warning: supertuxkart: local (0.6.2a-2) is newer than community (0.7rc1-1)

Re: [pacman-dev] Misleading info when epoch is used

2010-12-08 Thread Allan McRae
On 08/12/10 22:31, Sven-Hendrik Haase wrote: On 08.12.2010 00:40, Dan McGee wrote: On Tue, Dec 7, 2010 at 5:40 PM, Allan McRaeal...@archlinux.org wrote: On 08/12/10 08:45, Sven-Hendrik Haase wrote: On 07.12.2010 23:51, Nagy Gabor wrote: $ sudo pacman -Su warning: supertuxkart: local

Re: [pacman-dev] Misleading info when epoch is used

2010-12-08 Thread Xavier Chantry
On Tue, Dec 7, 2010 at 11:44 PM, Dan McGee dpmc...@gmail.com wrote: On Tue, Dec 7, 2010 at 4:55 PM, Nagy Gabor ng...@bibl.u-szeged.hu wrote: In fact I don't like neither force nor epoch. Epoch is just a version prefix, why don't we let the packager to workaround this (KISS)? We can introduce a

[pacman-dev] Misleading info when epoch is used

2010-12-07 Thread Nagy Gabor
$ sudo pacman -Su warning: supertuxkart: local (0.6.2a-2) is newer than community (0.7rc1-1) What? First I thought that our vercmp code is buggy, but vercmp binary worked as expected. Then I figured out that my local package has epoch=1, but the epoch is unset on the community package (so this

Re: [pacman-dev] Misleading info when epoch is used

2010-12-07 Thread Nagy Gabor
In fact I don't like neither force nor epoch. Epoch is just a version prefix, why don't we let the packager to workaround this (KISS)? We can introduce a new separator (now we have one: '.'), for example '#', and let the packager define his favourite pkgversion (maybe epoch in mind), like

Re: [pacman-dev] Misleading info when epoch is used

2010-12-07 Thread Dan McGee
On Tue, Dec 7, 2010 at 4:55 PM, Nagy Gabor ng...@bibl.u-szeged.hu wrote: In fact I don't like neither force nor epoch. Epoch is just a version prefix, why don't we let the packager to workaround this (KISS)? We can introduce a new separator (now we have one: '.'), for example '#', and let the

Re: [pacman-dev] Misleading info when epoch is used

2010-12-07 Thread Dan McGee
On Tue, Dec 7, 2010 at 4:51 PM, Nagy Gabor ng...@bibl.u-szeged.hu wrote: $ sudo pacman -Su warning: supertuxkart: local (0.6.2a-2) is newer than community (0.7rc1-1) What? First I thought that our vercmp code is buggy, but vercmp binary worked as expected. Then I figured out that my local

Re: [pacman-dev] Misleading info when epoch is used

2010-12-07 Thread Allan McRae
On 08/12/10 08:45, Sven-Hendrik Haase wrote: On 07.12.2010 23:51, Nagy Gabor wrote: $ sudo pacman -Su warning: supertuxkart: local (0.6.2a-2) is newer than community (0.7rc1-1) What? First I thought that our vercmp code is buggy, but vercmp binary worked as expected. Then I figured out that my