On Tue, Dec 18, 2018 at 11:54:29AM +0100, Max Horn wrote: > Hi, > > I am one of the GAP developers, and just saw this report; and I'd like > to ask something that has bothered me for a while: why does Debian > change the upstream version at all? Why not use 4.9.3 as we use > upstream, instead if 4r9r3? Note that GAP versions always used dots; > it is true that years ago, the filenames of our tarballs used "r" > instead of dots, but I don't see why that'd be a reason to keep using > a version that is different from what GAP itself reports, what our > documentation and websites use etc. > > AFAICT, in Debian, 4r9 < 4.9 and so changing this wouldn't even require a new > epoch.
Hello Max, The issue is that I never got the official decision to move to 4.x.y. The decision to use 4rxpy predate my involvement with gap in Debian, so maybe it is an historical misunderstanding. GAP used 4rxpy as version number for a long time. Not so long ago, the upstream achive I based the packcage on was named gap4r8p9_nopackages.zip. As you say I can change to 4.9 without requiring an epoch, however I cannot change back, and this might cause problem with some versionned depends. So if the GAP consensus is that I should change to 4.x.y, I will do it fo GAP 4.11 but I consider this is a minor issue compared to the potential for breakage. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here.
