On Sat, 6 Jul 2013 17:30:49 +0200
Thibaut VARENE wrote:
> The two libotr2* are gone, as part of the migration. So all is left to wait
> for the 3 packages you already mentioned, and as I said, that means that
> if, for some reason, they're never updated, libotr will never migrate, i.e.
> slow pok
On Sat, 2013-07-06 at 17:14 +0200, Thibaut VARENE wrote:
> On Sat, Jul 6, 2013 at 4:39 PM, Paul Wise wrote:
> On Sat, Jul 6, 2013 at 10:31 PM, Thibaut VARENE wrote:
>
> > libotr 4.0.0 hasn't entered testing yet and I don't
> understand why. The
> > status p
On Sat, Jul 6, 2013 at 5:27 PM, Paul Wise wrote:
> On Sat, Jul 6, 2013 at 11:14 PM, Thibaut VARENE wrote:
>
> > Still don't get it: why are bugs in packages that depend on libotr
> blocking
> > libotr? libotr is perfectly fine and I don't see why it should be blocked
> > from moving to testing be
On Sat, Jul 6, 2013 at 11:14 PM, Thibaut VARENE wrote:
> Still don't get it: why are bugs in packages that depend on libotr blocking
> libotr? libotr is perfectly fine and I don't see why it should be blocked
> from moving to testing because some packages that depend on it aren't
> properly mainta
On Sat, Jul 6, 2013 at 10:31 PM, Thibaut VARENE wrote:
> libotr 4.0.0 hasn't entered testing yet and I don't understand why. The
> status page reports that it hasn't been built on any arch ("missing 3
> binaries"), but those binaries are no longer built by libotr.
The transition looks like it is
Hi,
libotr 4.0.0 hasn't entered testing yet and I don't understand why. The
status page reports that it hasn't been built on any arch ("missing 3
binaries"), but those binaries are no longer built by libotr.
Help?
Thanks
--
Thibaut VARENE
http://hacks.slashdirt.org/
6 matches
Mail list logo
