On Mon, Oct 06, 2014 at 11:54:06AM +, Debian Bug Tracking System wrote:
> Date: Mon, 06 Oct 2014 13:52:42 +0200
> From: Ondřej Surý
> To: Bill Allombert , Andreas Barth
> Cc: Emilio Pozuelo Monfort , 763360-d...@bugs.debian.org
> Subject: Re: Bug#763360: libjpeg-turbo is hij
On Sun, Oct 5, 2014, at 14:38, Julien Cristau wrote:
> On Sat, Oct 4, 2014 at 20:48:31 +0200, Bill Allombert wrote:
>
> > On Fri, Oct 03, 2014 at 03:03:09PM +0200, Andreas Barth wrote:
> > > I hope we could leave it as that for the upload - nobody has a time
> > > machine to undo the upload, but
On Sat, Oct 4, 2014 at 20:48:31 +0200, Bill Allombert wrote:
> On Fri, Oct 03, 2014 at 03:03:09PM +0200, Andreas Barth wrote:
> > I hope we could leave it as that for the upload - nobody has a time
> > machine to undo the upload, but we could try to make it better now and
> > discuss where we sho
On Fri, Oct 03, 2014 at 03:03:09PM +0200, Andreas Barth wrote:
> I hope we could leave it as that for the upload - nobody has a time
> machine to undo the upload, but we could try to make it better now and
> discuss where we should go.
Ok, let's focus on libjpeg-progs, since I do not think there i
On Fri, Oct 03, 2014 at 12:37:09PM +0200, Emilio Pozuelo Monfort wrote:
> >>seemed like the sensible thing to do, and I didn't see any problem
> >>with the proposed plan. After all, libjpeg62 had been long
> >>deprecated in favor of libjpeg8. Neither of us thought you would
> >>care about libjpeg62
Hi,
looking a bit from the outside it looks to me as different questions
discussed in parallel.
The one question is how we came here.
* Bill Allombert (ballo...@debian.org) [141003 12:15]:
> On Fri, Oct 03, 2014 at 01:41:02AM +0200, Emilio Pozuelo Monfort wrote:
> > On 30/09/14 11:32, Bill Al
On 03/10/14 12:14, Bill Allombert wrote:
On Fri, Oct 03, 2014 at 01:41:02AM +0200, Emilio Pozuelo Monfort wrote:
On 30/09/14 11:32, Bill Allombert wrote:
On Mon, Sep 29, 2014 at 08:55:16PM +0200, Ondřej Surý wrote:
Bill,
I am very sorry that I have not Cced everything related to the
libjpeg-t
On Fri, Oct 03, 2014 at 01:41:02AM +0200, Emilio Pozuelo Monfort wrote:
> On 30/09/14 11:32, Bill Allombert wrote:
> >On Mon, Sep 29, 2014 at 08:55:16PM +0200, Ondřej Surý wrote:
> >>Bill,
> >>
> >>I am very sorry that I have not Cced everything related to the
> >>libjpeg-transition
> >>to you. I h
On 30/09/14 11:32, Bill Allombert wrote:
On Mon, Sep 29, 2014 at 08:55:16PM +0200, Ondřej Surý wrote:
Bill,
I am very sorry that I have not Cced everything related to the
libjpeg-transition
to you. I have honestly believed that you and everyone else involved was
following the transition plan as
On Tue, Sep 30, 2014, at 11:32, Bill Allombert wrote:
> On Mon, Sep 29, 2014 at 08:55:16PM +0200, Ondřej Surý wrote:
> > Bill,
> >
> > I am very sorry that I have not Cced everything related to the
> > libjpeg-transition
> > to you. I have honestly believed that you and everyone else involved was
On Mon, Sep 29, 2014 at 08:55:16PM +0200, Ondřej Surý wrote:
> Bill,
>
> I am very sorry that I have not Cced everything related to the
> libjpeg-transition
> to you. I have honestly believed that you and everyone else involved was
> following the transition plan as mentioned in #717076#225. As fo
Bill,
I am very sorry that I have not Cced everything related to the
libjpeg-transition
to you. I have honestly believed that you and everyone else involved was
following the transition plan as mentioned in #717076#225. As for the
takover
of the libjpeg62* packages it was discussed in the transiti
Source: libjpeg-turbo
Version: 1:1.3.1-3
Severity: serious
Dear maintainers,
libjpeg-turbo is hijacking binaries from other source packages:
libjpeg-progs : provided by libjpeg8
libjpeg62 libjpeg62-dbg libjpeg62-dev: provided by libjpeg6b
Please correct this as soon as possible.
Cheers,
--
Bi
13 matches
Mail list logo
