From: Russell Jones (russell.jones_at_cas.ox.ac.uk)
Date: Thu Aug 02 2007 - 16:18:01 CEST
Message-ID: <46B1E799.5050901@cas.ox.ac.uk> Date: Thu, 02 Aug 2007 15:18:01 +0100 From: Russell Jones <russell.jones@cas.ox.ac.uk> Subject: Re: [suse-sles-e] systemtap, anyone?
Cristian Veronesi wrote:
> Russell Jones wrote:
>
>
>> The article addresses this. See the bugzilla bug linked to. AFAICT, they
>> don't exist, and you have to either run an old kernel or compile a newer
>> kernel (and it's debuginfo) yourself. You can find the debuginfo
>> repository for OSuSE 10.2 on http://en.opensuse.org . I'm not sure about
>> SLES10, but I guess you can follow the "compile it yourself" route.
>>
>
> Thank you Russell for your explaination. I can't follow Novell's logic
> here: why they delivered a new software that won't work without
> compiling another package from source? I hope they will fix the problem
> soon or later.
>
As explained in the bug, the debuginfo for all new patches would take
40Gb or so, which would be more than many of their mirrors would accept.
They were (as of March this year) apparently looking at ways of
selectively generating debuginfo.
The SuSE team's (or their management's) view seems to be: not many
people use debuginfo, virtually no-one uses all debuginfos, and those
that do are probably capable of generating their own.
Which begs the question, why bother with the repository at all? Why not
just provide generic instructions or a mechanism for creating your own
debuginfo packages?
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Thu Aug 02 2007 - 18:24:44 CEST