On Mon, Mar 15, 2010 at 01:03:19AM +0100, Julien Cristau wrote:
> On Mon, Mar 15, 2010 at 00:29:45 +0100, Bill Allombert wrote:
>
> > On Sun, Feb 14, 2010 at 09:44:57PM +0100, Andreas Barth wrote:
> > > * Sune Vuorela (nos...@vuorela.dk) [100214 21:32]:
> > > I fear I need to agree with you. We sh
bill.allomb...@math.u-bordeaux1.fr wrote:
>If you compile-time link a binary with libjpeg62 w/ versionned symbols, and try
>to run-time link it with libjpeg62 w/o versionned symbols, then the dynamic
>linker output a warning:
>
>cjpeg: /usr/lib/libjpeg.so.62: no version information available (requ
On Mon, Mar 15, 2010 at 00:29:45 +0100, Bill Allombert wrote:
> On Sun, Feb 14, 2010 at 09:44:57PM +0100, Andreas Barth wrote:
> > * Sune Vuorela (nos...@vuorela.dk) [100214 21:32]:
> > I fear I need to agree with you. We should have libjpeg62 with
> > symbols, recompile every package build-depend
On Sun, Feb 14, 2010 at 09:44:57PM +0100, Andreas Barth wrote:
> * Sune Vuorela (nos...@vuorela.dk) [100214 21:32]:
> I fear I need to agree with you. We should have libjpeg62 with
> symbols, recompile every package build-depending on libjpeg*-dev after
> that till the release, and then move to lib
* Andreas Barth (a...@not.so.argh.org) [100214 21:45]:
> In other words, please rollback libjpeg-dev to point again to
> libjpeg62-dev, and add symbol versions to libjpeg62 (the second can
> happen later, but as sooner it happens the better it is). After
> libjpeg-dev points again to libjpeg62-dev,
On 2010-02-14, Marc 'HE' Brockschmidt wrote:
> I think we might even do this before releazing squeeze. Once we have
> versioned symbols, the transition won't hurt as much.
>
> The current situation is quite problematic, as we can't foresee how many
> package can break after partial upgrades. We kn
* Sune Vuorela (nos...@vuorela.dk) [100214 23:32]:
> On 2010-02-14, Marc 'HE' Brockschmidt wrote:
> > --=-=-=
> > Content-Transfer-Encoding: quoted-printable
> >
> > Andreas Barth writes:
> >> * Sune Vuorela (nos...@vuorela.dk) [100214 21:32]:
> >>> I currently think roll-back, doing things prope
On 2010-02-14, Marc 'HE' Brockschmidt wrote:
> --=-=-=
> Content-Transfer-Encoding: quoted-printable
>
> Andreas Barth writes:
>> * Sune Vuorela (nos...@vuorela.dk) [100214 21:32]:
>>> I currently think roll-back, doing things properly, going ahead, is the
>>> way forward.
>> I fear I need to agr
Andreas Barth writes:
> * Sune Vuorela (nos...@vuorela.dk) [100214 21:32]:
>> I currently think roll-back, doing things properly, going ahead, is the
>> way forward.
> I fear I need to agree with you. We should have libjpeg62 with
> symbols, recompile every package build-depending on libjpeg*-dev
* Sune Vuorela (nos...@vuorela.dk) [100214 21:32]:
> On 2010-02-14, Andreas Barth wrote:
> >> So I will state it a last time:
> >> I propose to upload the libjpeg6b source package that generate
> >> libjpeg62 and libjpeg6b-dev (*not* libjpeg62-dev) and to upload
> >> libjpeg8 source package that
On 2010-02-14, Andreas Barth wrote:
>> So I will state it a last time:
>> I propose to upload the libjpeg6b source package that generate
>> libjpeg62 and libjpeg6b-dev (*not* libjpeg62-dev) and to upload
>> libjpeg8 source package that generate a libjpeg8-dev that provides
>> both libjpeg62-dev
On 2010-02-14, Andreas Barth wrote:
>> So I will state it a last time:
>> I propose to upload the libjpeg6b source package that generate
>> libjpeg62 and libjpeg6b-dev (*not* libjpeg62-dev) and to upload
>> libjpeg8 source package that generate a libjpeg8-dev that provides
>> both libjpeg62-dev
* Bill Allombert (bill.allomb...@math.u-bordeaux1.fr) [100214 13:22]:
> On Sun, Feb 14, 2010 at 12:17:42PM +0100, Andreas Barth wrote:
> > * Bill Allombert (bill.allomb...@math.u-bordeaux1.fr) [100214 10:19]:
> > > The second step would be to fix packages that Build-Depend on
> > > 'libjpeg62-dev'
On Sun, Feb 14, 2010 at 12:17:42PM +0100, Andreas Barth wrote:
> * Bill Allombert (bill.allomb...@math.u-bordeaux1.fr) [100214 10:19]:
> > The second step would be to fix packages that Build-Depend on
> > 'libjpeg62-dev'
> > to Build-Depend on 'libjpeg-dev' instead, but that might make theirs
> >
* Bill Allombert (bill.allomb...@math.u-bordeaux1.fr) [100214 10:19]:
> The second step would be to fix packages that Build-Depend on 'libjpeg62-dev'
> to Build-Depend on 'libjpeg-dev' instead, but that might make theirs
> build-dependencies unsatisfiable until they have been fixed. Again, please d
15 matches
Mail list logo
