Hello Adam,
On Sat, Jun 08, 2013 at 05:59:54PM +0100, Adam D. Barratt wrote:
> On Sat, 2013-06-08 at 18:32 +0200, Helge Kreutzmann wrote:
> > On Fri, Jun 07, 2013 at 09:02:21PM +0100, Adam D. Barratt wrote:
> > > On Fri, 2013-06-07 at 21:54 +0200, Helge Kreutzmann wrote:
> > > > a) the recent secur
On Sat, 2013-06-08 at 18:32 +0200, Helge Kreutzmann wrote:
> On Fri, Jun 07, 2013 at 09:02:21PM +0100, Adam D. Barratt wrote:
> > On Fri, 2013-06-07 at 21:54 +0200, Helge Kreutzmann wrote:
> > > a) the recent security update for *stable* broke tabmix as well (not only
> > > sid/jessie version) => p
Hello Adam,
On Fri, Jun 07, 2013 at 09:02:21PM +0100, Adam D. Barratt wrote:
> On Fri, 2013-06-07 at 21:54 +0200, Helge Kreutzmann wrote:
> > Hello,
> > a) the recent security update for *stable* broke tabmix as well (not only
> > sid/jessie version) => please tag 690998 appropriatly
>
> There's a
On Fri, 2013-06-07 at 21:54 +0200, Helge Kreutzmann wrote:
> Hello,
> a) the recent security update for *stable* broke tabmix as well (not only
> sid/jessie version) => please tag 690998 appropriatly
There's a fun extra complication there, in that the security update
isn't in stable, and won't be
Hello,
a) the recent security update for *stable* broke tabmix as well (not only
sid/jessie version) => please tag 690998 appropriatly
b) the build system (how to get the orig.tar.bz2) is not documented,
upstream does not provide those files. Please document the (albeit
simple) procedure in a READ
5 matches
Mail list logo
