SCIENTIFIC-LINUX-USERS Archives

November 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Oleg Sadov <[log in to unmask]>
Reply To:
Oleg Sadov <[log in to unmask]>
Date:
Wed, 16 Nov 2011 19:44:24 +0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
16/11/2011 08:01 +0100, Thomas Bendler wrote:
> Hi Yasha,
> 
> 2011/11/15 Yasha Karant <[log in to unmask]>
>         [...]
>         Although SL follows TUV, supposedly El Repo and some of the
>         other repositories actually are willing to fix the bugs in the
>         TUV distribution or to add vital functionality (such as
>         additional device drivers for hardware not supported by TUV),
>         perhaps one of these other EL compatible repositories will fix
>         this issue?
> 
> I don't think that the SL team or any other team has the man power to
> fix RHEL bugs or even more important to test them. It's one thing to
> fix a bug in a specific environment but a complete different story to
> do the same for the hole installation base. Without complex automate
> test units it is nearly impossible.

The common way -- bug reporting (and may be some information about
fixing ways -- workarounds and/or patches) in TUV's bugzilla and/or bug
trackers of upstream projects, and sending message about it into SL
mailing list. Fixes may be approved or not by TUV/upstream, but SL
community will be informed about problems and solutions.

ATOM RSS1 RSS2