yum and groupinstall
by Tom Murray
I have setup a local repository containing several .rpm files. I created a
comps.xml file outlining the category and groups for the local repository.
However, when I issue the yum grouplist command, I get the following error:
*Failed to add groups file for repository: localRepo - comps file is
empty/damaged*
However, if I try to install one of the the packages in the repository, it
works just fine.
Here are the steps I took to create the repodata:
The comps.xml and repository are stored in the directory:
/var/www/html/myrepo/x86_64
cd /var/www/html/myrepo/x86_64
createrepo -g comps.xml .
This created a /var/www/html/myrepo/x86_64/repodata directory which contains
the comps.xml and comps.xml.gz file.
Here is my comps.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE comps PUBLIC "-//Red Hat, Inc.//DTD Comps info//EN" "comps.dtd">
<comps>
<group>
<id>NodeManager</id>
<default>true</default>
<uservisible>true</uservisible>
<display_order>1</display_order>
<name>Node Manager</name>
<description>This group manages the node system resources and
reports info back to the Service Manager.</description>
<packagelist>
<packagereq type="default">pxNodeManager-1.0-1</packagereq>
</packagelist>
</group>
<category>
<id>CustomSoftware</id>
<display_order>1</display_order>
<name>Custom Software </name>
<description>Custom Software Suite </description>
<grouplist>
<groupid>NodeManager</groupid>
</grouplist>
</category>
</comps>
13 years, 4 months
Problems with USB drive in init 3 -- do I need autofs?
by Robert Moskowitz
System is Fedora 12 in init 3 (non-gui) boot.
I have a 1.5Tb USB drive. When I reboot, typically I have had to unplug
and replug the drive or even power cycle the drive to get it found.
Well with this morning's new kernel update, i rebooted and though the
drive is showing in /media, none of its content is showing.
ls /media/d4ae05a3-c60f-489d-8159-e16c9a271f0b/
Shows nothing. What to do?
So I was HOPING that perhaps adding autofs would get this properly
mounted so I can access all the data I have on the drive.
13 years, 4 months
Fedora 14, wireless keyboards and encryption
by Chris Northwood
Hi there,
So, I'm having a problem with my Fedora 14 setup. I've recently
installed the distro on the machine, and set up full disk encryption
using the standard method in Anaconda. However, on the passphrase
screen (the one which appears as the OS starts), any input on my
wireless USB keyboard (this one:
http://www.maplin.co.uk/Module.aspx?ModuleNo=223792) doesn't work -
there appears to be no response to input from the keyboard. If I
connect a wired keyboard (this isn't a long-term solution, however -
the box is to become a media server, hidden behind my TV), then I can
enter the passphrase and continue just fine - once I get to the normal
user login screen, then I can enter my password and log in then. I
don't believe it's a BIOS problem as I can use the keyboard to
navigate around the BIOS setup screens no problem.
I did set up my machine using the wired keyboard, and only changed to
the wireless one at a later date, so I'm wondering if some relevant
kmod is missing when it's required, or something like that.
Any help to get my wireless keyboard up and running so I can enter my
passphrase with it would be much appreciated!
Regards,
Chris Northwood
13 years, 4 months
Yum strange behavior after upgrade to Release 14
by John Vo
Greetings:
I am new to the list so I will apologize for any problem with my post.
I upgraded my Fedora 13 to 14 using the "yum" method.
After the upgrade, when I ran yum upgrade, I ran into a few problem:
Error: Package: PackageKit-0.6.6-2.fc13.x86_64 (@updates/13)
Requires: PackageKit-yum-plugin = 0.6.6-2.fc13
Removing: PackageKit-yum-plugin-0.6.6-2.fc13.x86_64
(@updates/13)
PackageKit-yum-plugin = 0.6.6-2.fc13
Updated By: PackageKit-yum-plugin-0.6.9-4.fc14.x86_64 (fedora)
PackageKit-yum-plugin = 0.6.9-4.fc14
You could try using --skip-broken to work around the problem
And...many many of these..
** Found 313 pre-existing rpmdb problem(s), 'yum check' output follows:
ImageMagick-6.6.4.1-14.fc14.1.x86_64 is a duplicate with
ImageMagick-6.5.8.10-6.fc13.x86_64
PackageKit-0.6.9-4.fc14.x86_64 is a duplicate with
PackageKit-0.6.6-2.fc13.x86_64
PackageKit-device-rebind-0.6.9-4.fc14.x86_64 is a duplicate with
PackageKit-device-rebind-0.6.6-2.fc13.x86_64
PackageKit-glib-0.6.9-4.fc14.x86_64 is a duplicate with
PackageKit-glib-0.6.6-2.fc13.x86_64
PackageKit-gtk-module-0.6.9-4.fc14.x86_64 is a duplicate with
PackageKit-gtk-module-0.6.6-2.fc13.x86_64
I'm a casual Fedora users. Help please.
Thanks.
--
Best Regards,
________________________________________
John Vo
Network Administrator
Eagle Teleconferencing Services, Inc.
jvo(a)eagle.net
Direct: +1.212.200.2005
Office: +1.212.200.2000 x 105
Mobile: +1.917.836.7692
________________________________________
13 years, 4 months
Installing Openshot video editor
by orschiro@googlemail.com
Hi guys,
I'd like to install openshot. As it is not available in any repo I
picked the rpm package from here.
http://killobyte.com/openshot/
Unfortunately it needs python2.6, giving me the following error:
mlt-python-0.5.4-1.fc14.x86_64 requires python(abi) = 2.6
openshot-1.2.2-1.fc13.noarch requires python(abi) = 2.6
I'm using f14 so there's only python2.7 in the repos. Where could I
find python2.6?
--
robert
13 years, 4 months
how did I brea yum?
by Greg Woods
I have been using yum since it was first introduced and I've never seen
this one before. I can't get past it and I can no longer do any updates.
Any time I try to update anything, I get this error:
Running Transaction
Updating : rdesktop-1.6.0-9.fc14.i686
1/2
Error unpacking rpm package rdesktop-1.6.0-9.fc14.i686
error: unpacking of archive failed on file /usr/bin/rdesktop;4cf66925:
cpio: open
rdesktop-1.6.0-7.fc12.i686 was supposed to be removed but is not!
Failed:
rdesktop.i686
0:1.6.0-9.fc14
Complete!
(The output looks normal up to that point).
Anybody seen this before?
This is an i686 machine (dual core Pentium 4) which I recently upgraded
from 12->13->14, but I had done several updates before this started
happening.
--Greg
13 years, 4 months
Firefox and Opera on FC14 fail to access Globus site
by Abu Attar Musharih
Hello List,
I have two browsers, the Firefox and Opera on F14. Both can watch
without any problem
youtube videos and access almost any site except for Globus (
http://www.globus.org/ ). Using the Firefox of F7 on another box, I
found no problem of accessing that site.
Does anyone have an explanation?
Thanks in advance.
AA
13 years, 4 months
RE: Yum strange behavior after upgrade to Release 14
by Alan Gagne
> On Wed, Dec 1, 2010 at 1:07 PM, John Vo <jvo at eagle.net> wrote:
>> Greetings:
>>
>> I am new to the list so I will apologize for any problem with my post.
>>
>> I upgraded my Fedora 13 to 14 using the "yum" method.
>
> Although that method is pseudo-supported, I would try preupgrade in
> the future as recommended by
> http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
>
>> After the upgrade, when I ran yum upgrade, I ran into a few problem:
>
> Did you run yum upgrade or yum update?
>
>> Error: Package: PackageKit-0.6.6-2.fc13.x86_64 (@updates/13)
>> Requires: PackageKit-yum-plugin = 0.6.6-2.fc13
>> Removing: PackageKit-yum-plugin-0.6.6-2.fc13.x86_64
>> (@updates/13)
>> PackageKit-yum-plugin = 0.6.6-2.fc13
>> Updated By: PackageKit-yum-plugin-0.6.9-4.fc14.x86_64 (fedora)
>> PackageKit-yum-plugin = 0.6.9-4.fc14
>> You could try using --skip-broken to work around the problem
>>
>>
>> And...many many of these..
>>
>> ** Found 313 pre-existing rpmdb problem(s), 'yum check' output follows:
>> ImageMagick-6.6.4.1-14.fc14.1.x86_64 is a duplicate with
>> ImageMagick-6.5.8.10-6.fc13.x86_64
>> PackageKit-0.6.9-4.fc14.x86_64 is a duplicate with
>> PackageKit-0.6.6-2.fc13.x86_64
>> PackageKit-device-rebind-0.6.9-4.fc14.x86_64 is a duplicate with
>> PackageKit-device-rebind-0.6.6-2.fc13.x86_64
>> PackageKit-glib-0.6.9-4.fc14.x86_64 is a duplicate with
>> PackageKit-glib-0.6.6-2.fc13.x86_64
>> PackageKit-gtk-module-0.6.9-4.fc14.x86_64 is a duplicate with
>> PackageKit-gtk-module-0.6.6-2.fc13.x86_64
>>
>>
>> I'm a casual Fedora users. Help please.
>
> Don't take this the wrong way as it can be difficult to discern "tone"
> in an email but, the site I referenced specifically states:
> "Although upgrades with yum works, it is not explicitly tested as part
> of the release process by the Fedora Project. If you are not prepared
> to resolve issues on your own if things break, you should probably use
> the recommended installation methods instead."
>
> There may be a more automated method but I ran into some issues
> orphaned packages after upgrading with preupgrade and did the
> following for each problem package:
>
> Uninstall the old package:
> rpm -e --nodeps <package>
>
> Install the new package:
> yum install <package>
>
>
> Richard
I used preupgrade, but yum distro-sync did a great job of cleaning up
the packages identified by running package-cleanup --orphans.
Alan
13 years, 4 months
RE: iso dvd
by Alan Gagne
> On 12/01/2010 09:49 AM, William Stock wrote:
>> You have to burn the DVD as an .iso image.
>> If you burn it as a regular file it won't boot/run.
>> If you're using Brasero it's the bottom button (burn image).
>
> I prefer the KISS method: right click on the file in Nautilus and select
> Write to Disc. Works a charm and gets it Right every time.
Come on, have some fun. Open a terminal and growisofs.
:-)
13 years, 4 months