On Tue, Nov 6, 2012 at 2:43 PM, Neil Williams 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 t
On Tue, 6 Nov 2012 14:17:05 +0100
Thibaut VARENE wrote:
> On Tue, Nov 6, 2012 at 1:04 PM, Neil Williams wrote:
> > On Tue, 6 Nov 2012 10:59:42 +0100
> > Thibaut VARENE wrote:
> > If you want it in Debian now, push it into experimental. If you want it
> > Jessie (the next testing), then wait fo
On Tue, Nov 6, 2012 at 1:04 PM, Neil Williams wrote:
> On Tue, 6 Nov 2012 10:59:42 +0100
> Thibaut VARENE wrote:
>
>> On Tue, Nov 6, 2012 at 10:48 AM, Philipp Kern wrote:
>> > On Mon, Nov 05, 2012 at 03:04:21PM +0100, Thibaut VARENE wrote:
>> >> I thought that Wheezy having been frozen for quite
On Tue, 6 Nov 2012 10:59:42 +0100
Thibaut VARENE wrote:
> On Tue, Nov 6, 2012 at 10:48 AM, Philipp Kern 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 unstabl
On Tue, Nov 6, 2012 at 10:48 AM, Philipp Kern 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 th
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.
(Also please don't put a ">" befo
On Mon, Nov 5, 2012 at 15:04:21 +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. Please note in passing that
> libotr5, being NEW, went through the NEW queue and was reviewed at that
> time.
>
It
On Mon, Nov 5, 2012 at 2:32 PM, Dmitrijs Ledkovs wrote:
> On 05/11/12 10:58, Thibaut VARENE wrote:
> > severity 692327 important
> > thanks
> >
> > I don't see how this is a serious bug.
>
> Currently libotr2* are not build from any source package in sid.
> That means that any packages depending
On Mon, Nov 5, 2012 at 2:36 PM, Julien Cristau wrote:
> On Mon, Nov 5, 2012 at 11:58:12 +0100, Thibaut VARENE wrote:
>
> > severity 692327 important
> > thanks
> >
> > On Mon, Nov 5, 2012 at 1:32 AM, Dmitrijs Ledkovs
> wrote:
> >
> > > Package: libotr, release.debian.org
> > > Severity: serious
On Mon, Nov 5, 2012 at 11:58:12 +0100, Thibaut VARENE wrote:
> severity 692327 important
> thanks
>
> On Mon, Nov 5, 2012 at 1:32 AM, Dmitrijs Ledkovs wrote:
>
> > Package: libotr, release.debian.org
> > Severity: serious
> > User: release.debian@packages.debian.org
> > Usertags: transitio
On 05/11/12 10:58, Thibaut VARENE wrote:
> severity 692327 important
> thanks
>
> I don't see how this is a serious bug.
Currently libotr2* are not build from any source package in sid.
That means that any packages depending on it cannot transition into
testing (if it was not frozen).
That also m
severity 692327 important
thanks
On Mon, Nov 5, 2012 at 1:32 AM, Dmitrijs Ledkovs wrote:
> Package: libotr, release.debian.org
> Severity: serious
> User: release.debian@packages.debian.org
> Usertags: transition
>
> Recently libotr has been updated to version 4.x.x with binary package
> nam
Package: libotr, release.debian.org
Severity: serious
User: release.debian@packages.debian.org
Usertags: transition
Recently libotr has been updated to version 4.x.x with binary package
name libotr5.
By the looks of things, it was done because of pidgin-otr package which
now requires libotr5.
13 matches
Mail list logo
