On Mon, Jun 04, 2007, Wouter Verhelst wrote:
> On Sun, Jun 03, 2007 at 01:30:39PM +0200, Mike Hommey wrote:
> > On Sun, Jun 03, 2007 at 12:37:08PM +0200, Wouter Verhelst <[EMAIL
> > PROTECTED]> wrote:
> > > On Sat, May 26, 2007 at 11:02:37PM +0200, Raphael Hertzog wrote:
> > > > Right, I read your
On Sun, Jun 03, 2007 at 01:30:39PM +0200, Mike Hommey wrote:
> On Sun, Jun 03, 2007 at 12:37:08PM +0200, Wouter Verhelst <[EMAIL PROTECTED]>
> wrote:
> > On Sat, May 26, 2007 at 11:02:37PM +0200, Raphael Hertzog wrote:
> > > Right, I read your message too quickly, sorry. However the maintainer
> >
On Sun, Jun 03, 2007 at 10:51:24PM +0200, Pierre Habouzit <[EMAIL PROTECTED]>
wrote:
> On Sun, Jun 03, 2007 at 07:52:40PM +0200, Josselin Mouette wrote:
> > Le dimanche 03 juin 2007 à 19:32 +0200, Raphael Hertzog a écrit :
> > > Pierre explained that a sane library maintainer could/would use a new
On Sun, Jun 03, 2007 at 07:52:40PM +0200, Josselin Mouette wrote:
> Le dimanche 03 juin 2007 à 19:32 +0200, Raphael Hertzog a écrit :
> > Pierre explained that a sane library maintainer could/would use a new
> > version associated to the symbol even the ABI hasn't changed so that any
> > applicatio
Le dimanche 03 juin 2007 à 19:32 +0200, Raphael Hertzog a écrit :
> Pierre explained that a sane library maintainer could/would use a new
> version associated to the symbol even the ABI hasn't changed so that any
> application linked against the newer version get to effectively depend
> on the new
On Sun, 03 Jun 2007, Wouter Verhelst wrote:
> On Sat, May 26, 2007 at 11:02:37PM +0200, Raphael Hertzog wrote:
> > Right, I read your message too quickly, sorry. However the maintainer
> > can change the symbols file in his package and update the dependency
> > associated to this symbol and make su
On Sun, Jun 03, 2007 at 12:37:08PM +0200, Wouter Verhelst <[EMAIL PROTECTED]>
wrote:
> On Sat, May 26, 2007 at 11:02:37PM +0200, Raphael Hertzog wrote:
> > Right, I read your message too quickly, sorry. However the maintainer
> > can change the symbols file in his package and update the dependency
On Sat, May 26, 2007 at 11:02:37PM +0200, Raphael Hertzog wrote:
> Right, I read your message too quickly, sorry. However the maintainer
> can change the symbols file in his package and update the dependency
> associated to this symbol and make sure that a binary using this symbol
> will depend on
On Sun, May 27, 2007 at 09:56:13AM +0200, Raphael Hertzog wrote:
> On Sun, 27 May 2007, Mike Hommey wrote:
> > > Some research Scott James Remnant did back in the woody days indicated
> > > that
> > > with a more finely-grained shlibs implementation, the majority of packages
> > > could run fine a
On Sun, 27 May 2007, Mike Hommey wrote:
> > Some research Scott James Remnant did back in the woody days indicated that
> > with a more finely-grained shlibs implementation, the majority of packages
> > could run fine against glibc 2.0.
> >
> > No such luck with lenny due to the change of symbol h
Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> in the list of things that we can do to make it more easy to backport
> packages, there's one important item: have a finer-grained system for
> generating dependencies on shared libraries. The system should have
> historical knowledges of symbols exporte
On Sat, May 26, 2007 at 04:04:10PM -0700, Steve Langasek <[EMAIL PROTECTED]>
wrote:
> On Sat, May 26, 2007 at 10:09:44PM +0200, Josselin Mouette wrote:
> > Le samedi 26 mai 2007 à 21:06 +0200, Raphael Hertzog a écrit :
> > > Hello,
>
> > > in the list of things that we can do to make it more easy
On Sat, May 26, 2007 at 10:09:44PM +0200, Josselin Mouette wrote:
> Le samedi 26 mai 2007 à 21:06 +0200, Raphael Hertzog a écrit :
> > Hello,
> > in the list of things that we can do to make it more easy to backport
> > packages, there's one important item: have a finer-grained system for
> > gene
On Sat, May 26, 2007 at 10:47:10PM +0200, Josselin Mouette <[EMAIL PROTECTED]>
wrote:
> Le samedi 26 mai 2007 à 22:35 +0200, Raphael Hertzog a écrit :
> > > Another important point: such a system would help a lot to obtain lower
> > > testing migration times, but it would not help backports at all
On Sat, 26 May 2007, Josselin Mouette wrote:
> > If you can reuse most of the build-deps from testing instead of having to
> > recompile the build-deps too, it helps a lot.
>
> The build-deps also need to be rebuilt against the stable libc.
>
> > If you can reuse a
> > package from testing in st
On Sat, May 26, 2007 at 11:02:37PM +0200, Raphael Hertzog wrote:
> On Sat, 26 May 2007, Josselin Mouette wrote:
> > Le samedi 26 mai 2007 à 22:34 +0200, Raphael Hertzog a écrit :
> > > > This is not going to work. Checking that symbols are present in a
> > > > version does not guarantee they provid
On Sat, 26 May 2007, Josselin Mouette wrote:
> Le samedi 26 mai 2007 à 22:34 +0200, Raphael Hertzog a écrit :
> > > This is not going to work. Checking that symbols are present in a
> > > version does not guarantee they provide the required ABI.
> >
> > If the ABI changes, the soname changes. I st
Le samedi 26 mai 2007 à 22:34 +0200, Raphael Hertzog a écrit :
> > This is not going to work. Checking that symbols are present in a
> > version does not guarantee they provide the required ABI.
>
> If the ABI changes, the soname changes. I store the information of symbols
> for a given soname. So
Le samedi 26 mai 2007 à 22:35 +0200, Raphael Hertzog a écrit :
> > Another important point: such a system would help a lot to obtain lower
> > testing migration times, but it would not help backports at all, since
> > you still have to rebuild the package against the stable libc.
>
> If you can re
On Sat, 26 May 2007, Josselin Mouette wrote:
> Le samedi 26 mai 2007 à 21:06 +0200, Raphael Hertzog a écrit :
> > Hello,
> >
> > in the list of things that we can do to make it more easy to backport
> > packages, there's one important item: have a finer-grained system for
> > generating dependenci
On Sat, 26 May 2007, Josselin Mouette wrote:
> Le samedi 26 mai 2007 à 21:06 +0200, Raphael Hertzog a écrit :
> > in the list of things that we can do to make it more easy to backport
> > packages, there's one important item: have a finer-grained system for
> > generating dependencies on shared lib
Le samedi 26 mai 2007 à 21:06 +0200, Raphael Hertzog a écrit :
> Hello,
>
> in the list of things that we can do to make it more easy to backport
> packages, there's one important item: have a finer-grained system for
> generating dependencies on shared libraries.
Another important point: such a
Le samedi 26 mai 2007 à 21:55 +0200, Josselin Mouette a écrit :
> If libfoo 1.2 adds a new value in the enum (FOO_MODE_C), a new binary
> built against it may use it, and in this case will need version 1.2.
> However there is no obvious way by looking at the binary to tell whether
> this is the cas
Le samedi 26 mai 2007 à 21:06 +0200, Raphael Hertzog a écrit :
> in the list of things that we can do to make it more easy to backport
> packages, there's one important item: have a finer-grained system for
> generating dependencies on shared libraries. The system should have
> historical knowledge
Hello,
in the list of things that we can do to make it more easy to backport
packages, there's one important item: have a finer-grained system for
generating dependencies on shared libraries. The system should have
historical knowledges of symbols exported by libraries. Then when
generating depend
25 matches
Mail list logo
