Mailinglist Archive: opensuse (1470 mails)

< Previous Next >
Re: [opensuse] Now what? Glibc bug, vulnerability
On Sat, Feb 20, 2016 at 10:46:22AM -0800, John Andersen wrote:
On 02/20/2016 05:06 AM, Marcus Meissner wrote:
On Sat, Feb 20, 2016 at 02:00:25PM +0100, Markus Egg wrote:
Am 19/02/16 um 07:07 schrieb Wolfgang Rosenauer:
Am 19.02.2016 um 00:50 schrieb Peter Maffter:

Marcus Meissner <meissner@xxxxxxx> schrieb am 15:25 Donnerstag,
18.Februar 2016:
On Thu, Feb 18, 2016 at 03:13:36PM +0100, Florian Gleixner wrote:
...
Still building? I don't see updates for 13.2.

In openSUSE:Maintenance:4693 ... :/

Due to high OBS load (lot of checkins in the factory stagings) it is not
progressing as fast as wanted.

Ciao, Marcus


Will OpenSuSE 13.1 also be updated?

Yes.

Are there already timeplans for 13.2 and 13.1 when the updates will be
ready?

They were released last week.

http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00044.html
http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00042.html
http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00041.html

Ciao, Marcus


Are there no packages in common usage where the glibc library routines
are linked directly into the executables?

No.

A very very small set of packages links glibc statically, usually this is
limited
to the bootloader and related packages.

Someone told me this was possible, but I have no clue.

Especially with the dynamically loaded resolver, which is at problem here,
this is likely not the cause.

ciao, Marcus
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >