[xml/sgml-pkgs] Bug#781232: Bug#766884: libxml2 broken in sid for months already

[Aron Xu]

On Mon, Sep 7, 2015 at 3:54 PM, Thorsten Glaser <t.glaser at tarent.de> wrote:
> On Sat, 5 Sep 2015, Vincent Lefevre wrote:
>
>> I'm not the maintainer, but I think that it is probably cleaner to
>> have testing version = stable version until this bug is fixed (it
>
> No, absolutely not. We’re in the midst of a hell of a transition,
> holding back packages just for fun isn’t helping.
>

I'm not being freak for keeping the same version, but I'm against
reverting to old version for this specific odd package.

>> On 2015-09-05 08:49:35 +0200, Raphael Hertzog wrote:
>
>> > This just proves that you don't know how Debian works. A fix for testing
>> > must come via unstable not from stable.
>>
>> First, I haven't said that a fix for testing must come from stable,
>> just that it was easy to fix testing too (because this would be the
>> same patch). And no, a fix for testing does not necessarily come
>> via unstable:
>
> This is the absolute exception; all uploads to testing should come
> via unstable if at all possible. The exception is for when people
> used unstable as experimental, preventing migration, but there are
> really urgent issues to be fixed in testing. Only. The paragraph
> you cited allows maintainers to deviate from the normal “via un‐
> stable” rule in such cases, it doesn’t make it the norm. This is
> how Debian works.
>

Yep, and testing's security support isn't a priority at this moment
(non-frozen) IMHO, even it's really nice to have.

> Same goes for stable: If there is a to-be-fixed-in-stable-too bug
> in the package, first fix it in unstable, then (while waiting for
> it to migrate to testing, or even after that) fix it in stable.
> This ensures we don’t have bugs fixed in stable that are reintroduced
> in later Debian versions (there even has been a package which had
> this for two subsequent Debian releases, people really don’t like
> to see this).
>

Agreed on fixing unstable first if possible, but it's only ideal case
that we really want to wait it migrate to testing. Stable is for
production, not another testing for testing that need to wait for
testing.

Regards,
Aron