SCIENTIFIC-LINUX-USERS Archives

May 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show HTML 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:
"John H. Outlan CPA" <[log in to unmask]>
Reply To:
John H. Outlan CPA
Date:
Sat, 14 May 2011 16:04:56 -0400
Content-Type:
multipart/alternative
Parts/Attachments:
text/plain (1109 bytes) , text/html (1360 bytes)
On May 14, 2011 1:36 PM, "Matthew Chan" <[log in to unmask]> wrote:
>
> Hi,
>
> Yes, there's an error being caused with epel. Manual intervention is
required.
>
> EPEL will try to update ntfsprogs to 2.0, but because testdisk requires
the libntfs.so.9 shared lib, and the EPEL build of ntfsprogs doesn't have
it, the upgrade fails.
>
> You can work around it by using --skip-broken, but that's not really a
great solution.
>
> For the 6.1 livecd release, I wouldn't mind having useful software (like
testdisk etc) on the livecd either, but I'm worried that users may be
unaware of these non-repo packages and then install the livecd like I did.
It can be a security problem if a vulnerability is discovered in a package
later on, since the package will almost never be updated. For packages like
testdisk it's probably not a problem, but we also have packages like openVPN
in the extras repo.
>
> Would it be a problem to disable the install ability of the liveCD?
>
> Matt
>

I absolutely wouldn't go that route.  The manual intervention required is
minimal.  Changing the packages and leaving things as they are would be
better/easier imo.


ATOM RSS1 RSS2