Bug#692327: libotr: Please provide libotr2
On Tue, Nov 6, 2012 at 1:04 PM, Neil Williams <codehelp@debian.org> wrote:
> On Tue, 6 Nov 2012 10:59:42 +0100
> Thibaut VARENE <varenet@debian.org> wrote:
>
>> On Tue, Nov 6, 2012 at 10:48 AM, Philipp Kern <pkern@debian.org> wrote:
>> > On Mon, Nov 05, 2012 at 03:04:21PM +0100, Thibaut VARENE wrote:
>> >> I thought that Wheezy having been frozen for quite some time, it was okay
>> >> to upload new packages to unstable again.
>> >
>> > I'm sure we would've communicated that on d-d-a if this would've been
>> > the case.
>>
>> Okay then. Wheezy has been frozen for 4 months already. Out of
>> curiosity, how long will we have to wait before new software can be
>> pushed again to Debian?
>
> If it's targeting experimental, that is already possible and has never
> been a problem.
>
> If it's to target unstable then expect an announcement on d-d-a to the
> effect that unstable is now open again a few days after the Wheezy
> release. (Release, not freeze). i.e. around the time that Jessie
> becomes available as the new testing.
>
> Note that from past experience, it's not advisable to upload very soon
> after the d-d-a announcement anyway. So many other packages get
> uploaded at that point that many dependencies become uninstallable. Talk
> to maintainers of packages which your package needs and co-ordinate in
> advance.
>
> If you want it in Debian now, push it into experimental. If you want it
> Jessie (the next testing), then wait for the d-d-a announcement. If you
> wanted it in Wheezy it's too late. If you just wanted it in unstable
> then it's clear that this is not desirable and your only option is
> experimental.
Noted. The package was in experimental for several weeks and got zero
attention. My general understanding is that nobody looks at
experimental anyway. Another part of the issue was upstream's will to
have it in Ubuntu as soon as possible. Ubuntu autosync doesn't fetch
from experimental.
--
Thibaut VARENE
http://hacks.slashdirt.org/
Reply to: