[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Helping to fix some bugs in tetex



Hilmar Preusse <hille42@web.de> schrieb:

> On 22.07.03 Frank Küster (frank@kuesterei.ch) wrote:
>
> Hi,
>
>> in the last view days I have looked at a couple of bugs in
>> tetex-base, willing to help you fixing them. Since I'm lazy, I'm
>> going to start with the most easy ones - some of them so
>> unimportant that nobody has ever responded to the bug reports (or
>> bothered to lower the severity).
>> 
>> I have some questions how I should act in order not to cause you
>> unnecessary work. 
>> 
>> - Some bugs are clearly to be forwarded to upstream, or even to the
>>   individual package authors. Should I give you a list of that, or
>>   do you prefer that I do a "non-maintainer tagging" and forward it
>>   myself (note that I'm not a Debian developer)?
>> 
> I'm not a developer either. Nevertheless you might have noticed, that
> I've forwarded bugs to upstream and even closed some. I'm just
> subscribed to debian-tetex-maint. 

Me too, now. I just didn't notice that this was a public debian list. 

>> - Some bugs are still open although the responses indicate that they are
>>   resolved, e.g. #175839 which ends with
>> 
> I think I've spoken with Atsuhito about that. The result was: If we
> close that and it vanishes from the bug page of tetex-extra, it might
> be possible, that few days later anybody comes whining, that
> SIunits.sty is included twice. I know that should not happen, cause
> everybody should search through the database of closed bugs too,
> before submitting a report, especially if he's running stable, but..
> as you see in #175839.

Err, I remember. What I would like to see is a "severity" "fixed in
unstable/testing", so that the bug still appears on the package's bug
page, but in a separate section. But that's clearly not the job of this
list. 

Thanks, Frank
-- 
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie



Reply to: