Re: tetex-bin_2.99.7.20041226-beta-1_i386.changes is NEW
#>> * Dropped build-dependency on xlibs-dev - all necessary libraries are
#>> pulled in by libxaw7-dev.
#>>
#> Closes #258256
#
#Uups, yes, missed that.
tags 258256 fixed-in-experimental
stop
Hilmar Preusse <hille42@web.de> wrote:
> On 10.01.05 Debian Installer (installer@ftp-master.debian.org) wrote:
>
> <snip>
>
>> - miscellaneous bugs: closes: #83146, #107258, #137823, #175794,
>> #176526, #197259, #209347, #219630, #225687, #232420, #238627,
>> #264394, #273596, #273597, #182215, #255101, #285395, #201935
>>
> Do you plan to explain more in detail, what you're speaking about?
> Should I refine it?
I am not sure about this. If we write something about every bug we
close, this would mean:
- the changelog gets \HUGE.
- it will be a big amount of work to go through the bug reports,
recollect what has been learned there, and formulate a sentence that
describes how the bug was closed. This time could as well be used for
something more forward-oriented. I checked for every bug I closed that
there is some explanation in the bug logs - at least something like
"confirmed to be fixed in ...".
I think that since we didn't do any changes to close these bugs, and the
reason why they are closed are already registered in the BTS, this mere
enumerating might be enough. Note that I also wrote (which you didn't
cite):
,----
| * Lots of bugs are closed by this upload - all bugs listed below have
| already been tagged fixed-upstream, and there should be an explanation
| in the bug logs at http://bugs.debian.org/<bugnumber>. In some cases
| the explanation is only a link to the LaTeX Project bug database, or
| it is in the comments of the mail sent to the control server, but it's
| always there.
`----
There might still be people complaining about this. But I think what I
did here is different to what people have done in the past to arouse
anger on -devel, namely just
* New upstream version (closes: #12345, #67890, #23456, #78901)
So that what I did is justified, I hope. Personally I'd suggest that you
rather pick some other thing you like to be fixed, e.g. splitting of
font packages or of whatever.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Reply to: