Re: maxima 'serious' bug fix missed freeze
Greetings!
"Adam D. Barratt" <adam@adam-barratt.org.uk> writes:
> On Fri, 2010-09-17 at 18:24 -0500, Kumar Appaiah wrote:
>> On Tue, Sep 14, 2010 at 11:45:40AM -0500, Kumar Appaiah wrote:
>> > Yes. You should upload to the same place, and instead of using
>> > "unstable" as the target distribution, use "testing" or
>> > "testing-proposed-updates". Naturally, since you will be basing your
>> > package on the version currently in testing, you should set a version
>> > number higher than that, but just about high enough. For example,
>> > 5.21.1-2+squeeze1 ot 5.21.1-2squeeze1 should be appropriate.
> [...]
>> Camm has done this[1]. Could you please consider this upload for
>> squeeze?
>
> The upload appears to have introduced several other changes which aren't
> documented in the changelog and don't appear related to fixing the bug;
> the changelog just says "Backport fixes to 591862 and related items":
>
> - a change to source format 3.0 (quilt); presumably to allow Kumar's
> patches to be added, but still not great for a tpu during freeze
> - (xmaxima) Depends change to use tk8.{5,4} instead of tk8.{4,3}; not so
> bad
> - (maxima) Dropping of gv and maxima-emacs from Recommends to Suggests
> - (maxima-emacs) Addition of maxima-doc to Depends, mime-support,
> postscript-viewer, pdf-viewer to Recomemnds
> - A build system change which results in debian/maxout.gnuplot,
> debian/tests.lisp.patch, doc/info/extract_categories.sh.debdiff,
> doc/info/include-maxima.texi, doc/man/ru/maxima.1 and tests/rtest14.ERR
> disappearing from the source package; it's possible some or all of them
> were never intended to be shipped, but it's not easy to tell.
>
Yes, please excuse the confusion and allow me to explain.
For some as yet still unclear reason, several bug fixes to the maxima
package were lost on each upstream upgrade starting from
5.20.1. (e.g. 5.21.0, 5.21.1, 5.22.0, 5.22.1). The issue seems to be
with uupdate, as I've relied for many years on the procedure 'uscan
--verbose' to upgrade my packages to follow upstream. This script is
failing now to propagate the previous changes, and I have not had time
to figure out exactly why.
Each of the issues you mention above (save the tk dependency version
change), together with the fix to the bug explicitly referred to in
this thread, were fixed in previous maxima releases that propagated
into testing, and were erroneously reverted on upstream upgrade in
this manner. This is the meaning behind 'related items'.
The files listed in your last point are build generated/modified files
erroneously included in the source diff. All of these 'were not
intended to be shipped'. This was a fix erroneously reverted.
The replacement of the gv dependency with mime-support and postscript
viewer was a fix to an explicit bug which had been erroneously
reverted. I did tighten the relationship a little by moving this
dependency away from maxima and to the sub-packages explicitly
requiring this functionality.
maxima suggests maxima-emacs was a bug fix erroneously reverted.
quilt was an improvement erroneously reverted.
If you want, I can send you the bug numbers, and/or re-weaken the
package by reintroducing any of the now fixed bugs in a new upload.
Take care,
> Regards,
>
> Adam
>
>
>
>
--
Camm Maguire camm@maguirefamily.org
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
Reply to: