linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: debian-hppa@lists.debian.org, debian-glibc@lists.debian.org,
	linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: hppa nptl switch
Date: Tue, 01 Sep 2009 17:50:27 +0200	[thread overview]
Message-ID: <4A9D42C3.70103@aurel32.net> (raw)
In-Reply-To: <119aab440909010655j148ad3b8oae5328d646ef570c@mail.gmail.com>

Carlos O'Donell a =E9crit :
> On Tue, Sep 1, 2009 at 2:08 AM, Aurelien Jarno<aurelien@aurel32.net> =
wrote:
>> Frans Pop a =E9crit :
>>> Carlos O'Donell wrote:
>>>>> In practice it shouldn't be problem at all.
>>>>> Debian should make sure that binary/library compiled
>>>>> against NPTL-hppa-glibc will require NPTL-hppa-glibc
>>>>> by proper Depends: line like "libc6 (>=3D 2.10)".
>>>> Does every package have to do this? I'm not very familiar with all=
 the
>>>> packaging requirements.
>>> It is something that should automatically get done correctly as lon=
g as
>>> the libc-dev package defines the minimum version that way.
>>>
>>> The mechanism that determines this is in /var/lib/dpkg/info/libc6.s=
hlibs.
>>> Currently this has lines like:
>>>    libc 6 libc6 (>=3D 2.9)
>>>
>> No, as glibc uses symbols files, this file is actually not used.
>> Nevertheless it is still possible to resolve all symbols to libc6 (>=
=3D 2.10).
>=20
> Once an application is rebuilt against a new libc, what prevents the
> user from downgrading libc and breaking the application?
>=20

If we make sure that the new programs are using symbols from version
GLIBC_2.10, the program should refuse to start with a lower version of
the glibc.

--=20
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
 in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-09-01 15:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.62.0908181940440.7856@sci.felk.cvut.cz>
     [not found] ` <119aab440908181851i174315c6lebacea921046bbb0@mail.gmail.com>
     [not found]   ` <20090819124816.GC2517@hall.aurel32.net>
2009-08-31  5:01     ` hppa nptl switch Carlos O'Donell
2009-08-31  8:16       ` Petr Salinger
2009-08-31 15:10         ` Carlos O'Donell
2009-08-31 16:46           ` Frans Pop
2009-08-31 16:53             ` Carlos O'Donell
2009-09-01  6:08             ` Aurelien Jarno
2009-09-01 13:55               ` Carlos O'Donell
2009-09-01 14:40                 ` Thibaut VARENE
2009-09-01 15:50                 ` Aurelien Jarno [this message]
2009-09-02  0:03                   ` Mike Frysinger
2009-09-02 14:09                     ` Carlos O'Donell
2009-09-02 14:55                       ` Aurelien Jarno
2009-09-02 15:24                         ` Carlos O'Donell
2009-09-02 15:28                           ` Aurelien Jarno

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A9D42C3.70103@aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=carlos@systemhalted.org \
    --cc=debian-glibc@lists.debian.org \
    --cc=debian-hppa@lists.debian.org \
    --cc=linux-parisc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).