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

Re: Processed: Re: Bug#408540: tex-common: Warnings during upgrade



owner@bugs.debian.org (Debian Bug Tracking System) wrote:

> Processing commands for control@bugs.debian.org:
>
>> forcemerge  408263 408541
> Bug#408263: tex-common: buggy ucfr calls
> Bug#408541: tex-common: "Need a fully qualified path" messages on install
> Forcibly Merged 408263 408541.

Ich hab's spaßeshalber mal ausprobiert: Forcemerge beschwert sich nicht,
dass die Bugs unterschiedliche 

Oh my, I have already drunken too much beer (bi-monthly institute
"Thanks God it's Friday" gathering...), I shouldn't be talking german
here.

Well, this was for testing, and indeed "forcemerge" doesn't complain
about the severities of the two bugs not being the same.  The question
remains whether it takes the severity of the first bug or the highest
severity of any of the bugs.

But no, no questions: it *is* documented:

,---- http://www.debian.org/Bugs/server-control
| forcemerge bugnumber bugnumber ...
|     Forcibly merges two or more bug reports. The first bug listed is
|     the master bug, and its settings (the settings which must be equal
|     in a normal merge) are assigned to the bugs listed next. To avoid
|     typos erroneously merging bugs, bugs must be in the same
|     package. See the text above for a description of what merging
|     means.
| 
|     Note that this makes it possible to close bugs by merging; you are
|     responsible for notifying submitters with an appropriate close
|     message if you do this.
`----

Regards, Frank
-- 
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)



Reply to: