BUG: bison port should use the epoch key

[yves@…]

yves$ sudo port upgrade bison Password:

## nothing happens, same with outdated but ...

yves$ port installed bison

bison 2.0_0+yacc (active)

yves$ port info bison bison 2.0a, Revision 2, devel/bison (Variants: yacc) yves$ more devel/bison/Portfile name bison version 2.0a revision 2

[olegb@…]

Try to use the -d flag it should give some output.

[olegb@…]

adding me as cc, making it slightly more difficult for me to forget this bug

[yves@…]

We do lose a bit of that mysterious feeling with the -d flag

Bilbo:~ yves$ sudo port -d upgrade bison Password: DEBUG: Found port in ​file:///Users/Shared/src/darwinports/dports/devel/bison DEBUG: epoch: in tree: 0 installed: 0 DEBUG: bison 2.0a_2 exists in the ports tree DEBUG: bison 2.0_0 is installed DEBUG: No need to upgrade! bison 2.0_0 >= bison 2.0a_2

[olegb@…]

That means what you are saying is that outdated and upgrade should make a "we are done statement" ? Because what you have reported is just default behaviour and what should be expected.

[yves@…]

My point is rather that v. 2.0a is more recent than v. 2.0, but port considers the opposite.

[olegb@…]

ah, now i see :-)

the problem is that:

2.0a *should* be older than 2.0 - but, in this case it isnt. The bison port should use the epoch key to tell the portssystem that the old version 2.0a is newer that 2.0.

[pguyot (Paul Guyot)]

Removing this from base queue.

[macdome@…]

I am no longer able to actively maintain the bison port.

[toby@…]

2.1 committed, this shouldn't be an issue any more