> > 1. There is already a Breaks for gettext-base. Why "Conflicts" should > > be used here and not Breaks? > > hmm, good question. Just applying these mechanically.
Ok. I think this is a case for Breaks, because the old library will be deprecated as soon as the new library exists. The relevant portion of policy is here: https://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts Conflicts is more for packages that "will always conflict" but this does not really hold because the old library will not be in Debian 9 anymore. > > 2. The report talks about experimental but the proposed patch is > > supposed to be applied in unstable as soon as possible, right? > > right, but not yet, after GCC 5 is the default. This is really my fault, I forgot to read the Subject :-) So I suppose that I can still upload 0.19.5.1 safely, unless you tell me that the new g++ will be the default in less than 5 days. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
