Bug#692327: libotr: Please provide libotr2
On Tue, Nov 6, 2012 at 2:43 PM, Neil Williams <codehelp@debian.org> wrote:
> Having a freeze simply means that some package changes *must* be
> delayed until after the freeze. Experimental works for some, if it
> doesn't work for you then you cannot update the package in Debian until
> the release, so maybe help get the release out.
I believe I was mistaken as to what a "freeze" is. To me the freeze
impacted testing, not unstable, being the whole purpose of a "freeze",
i.e. ensuring that new packages in unstable don't make it to
testing-soon-to-be-stable. I didn't realize this meant that /unstable/
was to be considered as frozen too. Maybe it should effectively be so,
so that new packages that aren't RC fixes can't even be uploaded to
sid. This would avoid something like this happening again in the
future.
Anyway, I stand corrected.
That being said, I'd like to point out again that all this fuss was
made for nothing, since none of the packages listed in the initial
email are being blocked from entering wheezy because of this upload,
since none of them are unfrozen, and wheezy is unaffected by this
change. And I see nothing wrong with breaking packages in unstable,
but maybe there too I'm mistaken.
--
Thibaut VARENE
http://hacks.slashdirt.org/
Reply to: