That sort of appears to be the case. I tried nuking it. There is still a
libasound.so. file from other RPMs. So it's likely still workable. This WAS
the main gateway machine to the Internet here for a dozen or so 'thingies' on
the network. At the moment all it is doing is spamassassin
On Fri, 27 Jan 2017, jdow wrote:
Ran yum --releasever=6.7 update sl-release
Same error going 6.6 to 6.7 as 6,6 to 6.x (6.8).
Transaction Check Error:
file /lib64/libasound.so.2.0.0 from install of alsa-lib-1.1.0-4.el6.x86_64
conflicts with file from package libasound2-1.0.24.1-35.el6.x86_64
Ran yum --releasever=6.7 update sl-release
Same error going 6.6 to 6.7 as 6,6 to 6.x (6.8).
Transaction Check Error:
file /lib64/libasound.so.2.0.0 from install of alsa-lib-1.1.0-4.el6.x86_64
conflicts with file from package libasound2-1.0.24.1-35.el6.x86_64
What now?
{^_^}
On 2017-01-27
On 01/27/2017 01:42 PM, John Pilkington wrote:
As I noted, my system seems to have updated happily. I started it from
yumex by enabling the rolling repos. But I've just been examining my
grandson's, which yesterday 'welcomed' him to emergency mode. I'm afraid
he doesn't fit the SL target user
On 01/23/2017 11:32 PM, Karel Lang AFD wrote:
Hi,
just quick search reveals quite a lot of things - eg.:
https://bugzilla.redhat.com/show_bug.cgi?id=760885
it says:
'
CD-ROM passthrough from to the host to a guest has been disabled in
Red Hat Enterprise Linux 7.0 Beta for all front ends. QEMU
As I noted, my system seems to have updated happily. I started it from
yumex by enabling the rolling repos. But I've just been examining my
grandson's, which yesterday 'welcomed' him to emergency mode. I'm afraid
he doesn't fit the SL target user profile and his access time is limited.
yum
Removing yum-conf-sl7x should perform the task.
http://ftp.scientificlinux.org/linux/scientific/7x/x86_64/release-notes/#_sl_specific_behavior_changes
Pat
On 01/27/2017 11:56 AM, Werf, C.G. van der (Carel) wrote:
On SL5 and SL6 it was easy to prevent yum from updating to a new release, by
On SL5 and SL6 it was easy to prevent yum from updating to a new release, by
disabling sl5x.repo or sl6x.repo.
Still updates for the current release were found.
On SL7 only the sl7x.repo is installed by default.
How can I prevent SL7.2 from upgrading to SL7.3, but still find updates for
SL7.2 ?
I'm fine with nux-desktop also, wasn't planning on switching. Was just
wondering if they were mixable, but seems can't be sure.
On 2017-01-27 14:49, James M. Pulver wrote:
Why would you want to use rpmfusion over nux? I've had great success
anyway with nux.
James Pulver
CLASSE Computer
-- Le (On) 2017-01-26 +0100 à (at) 00:19:55 Franchisseur Robert écrivit
(wrote): --
> -- Le (On) 2017-01-25 -0600 à (at) 13:48:55 Connie Sieh écrivit (wrote): --
>
> > What method are you using to do the install?
> > What url/media are you using?
>
>ftp/http
>I tried first
Why would you want to use rpmfusion over nux? I've had great success
anyway with nux.
James Pulver
CLASSE Computer Group
Cornell University
On 01/26/2017 03:59 PM, John Pilkington wrote:
On 26/01/17 20:42, Maarten wrote:
Great, didn't know that about rpmfusion now doing el7. Anyone know if
11 matches
Mail list logo
