Hi Brady,

do you have any opinion what do do about this bug? 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=307131

For me, 100% compatibility within the versions of "testing"
is not a goal. However, this will probably also hit people upgrading
from the previous stable version (3.0.6-1) once sarge is released.
There are two choices:

* leave things as are, and add documentation on how to adapt
existing source.

* move the current glpk package to "glpk4", and upload as "glpk" the
latest version that does not contain API changes as compared to 3.0.6.

I guess the choice mainly depends on how many people would get hit
by this, and how difficult it would be to adapt your sources... what do you
think?

   Falk




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to