From: Marcus Meissner (meissner_at_suse.de)
Date: Thu Aug 02 2007 - 16:39:37 CEST
Date: Thu, 2 Aug 2007 16:39:37 +0200 From: Marcus Meissner <meissner@suse.de> Message-ID: <20070802143937.GB19119@suse.de> Subject: Re: [suse-sles-e] systemtap, anyone?
On Thu, Aug 02, 2007 at 03:18:01PM +0100, Russell Jones wrote:
> 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?
For SLES 10 we publish debuginfos for kernel and glibc. So for systemtap this
would help.
Ciao, Marcus
---------------------------------------------------------------------
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:43:17 CEST