Notes on Yum Changes
by seth vidal
Here are some notes I typed up this weekend on a plane and in a truly
dull airport about yum changes in the upcoming test release.
Here they are:
Making yum repositories now:
Yum repositories are no longer created by yum-arch. There is a new
program, createrepo (http://linux.duke.edu/metadata/generate), that
creates the metadata. The metadata for rpm packages is the information
that describes the data stored in the payload of the rpm. createrepo
takes the metadata from each rpm in the repository and stores it in an
xml format that is simple and expedient to load the data from. This
makes it easier and more efficient for yum to resolve dependencies
and find out other important information about the packages a user
would want to install.
To create your own repository install the createrepo rpm and run:
create-repo /path/to/the/packages
It will recursively go through the directory you specify, find all
the rpm packages, and retrieve the pertinent metadata. Once this
command completes you should have a directory named 'repodata'
created in the directory path you specified on the command line.
The repodata directory will contain at least 4 files. They are:
repomd.xml - stores the information about the other metadata
files. It is a meta-metadata file. :) It has checksums and
timestamps for each file of the metadata.
primary.xml[.gz] - stores the critical information for listing and
dependency solving packages. It is the core of information for the
repository and it is normally the smallest of the files containing
package metadata.
filelists.xml[.gz] - stores the complete file listing for each
package. It also contains some information describing the files.
It distinguishes between files, directories and ghosted files in
the package.
other.xml[.gz] - stores any other information that is available from
the package. This file is available for completeness and convenience.
In particular, this file stores all the changelog information for
each package.
If you specified the -g option to createrepo and listed a groups file
(a comps.xml format file) then this file will also be copied to
the repodata directory.
Yum Changes:
1. Yum will no longer work with repositories generated with yum-arch.
The new format and the old format do not conlict with each other so
if you want to run createrepo and yum-arch on a single repository
that will work just fine. However, the new yum will not support
old-style repositories and there are no plans at this time to make
it possible.
2. When specifying packages on the command line and in the exclude
lists you can use complete version and arch strings now. In addition
to specifying:
yum install mypackage
you can now also specify:
yum install mypackage-1.1
The following version/arch string formats are accepted:
name
name-ver
name-ver-rel
name.arch
name-ver-rel.arch
epoch:name-ver-rel.arch
3. The config file has been enhanced in a number of ways. Inside the
config file you can now specify include=url://some/location/file at
any point. This allows you to include one config file inside another.
The file is included literally, as though typed in place. The include
option takes any url that yum is capable of handling (http, https,
ftp and file).
4. In addition to the above config change, yum also offers an
optional /etc/yum.repos.d directory for configurations. Each file
named with a .repo extension will be parsed and added to the set of
repositories listed in the yum.conf file. The format of these files
is identical to the listing of a repository in the yum.conf file:
[repository-id]
name=repository name
baseurl=url://path/to/repository
...
5. New command line options:
--obsoletes - tell yum to include obsoletes in its update processing
--enablerepo=repository-id - tell yum to enable the repository of
that id this option can be specified
multiple times on the command line.
This will override the 'enabled' option
to a repository in the configuration
file.
--disablerepo=repository-id - The logical opposite of the above.
Other new features will be added and they'll be described in more
detail then. This should give users an overview of the major changed
items in yum, so far.
hope this helps people.
-sv
19 years, 7 months
Disabling module loading
by Paul Sery
Fedora Core 1 allowed module loading to be disabled by running echo off
> /proc/modules. This doesn't appear to work in FC2.90 and I haven't
been able to find any references to its removal. Does anyone know the
status of this feature?
19 years, 7 months
Shared Libraries corrupt after rawhide update
by Ernest L. Williams Jr.
Hi,
After the rawhide update yesterday, I used my system for about an hour or two.
The last thing I did was lock the screen.
Now next morning, I launch up2date and get an error:
=================================================
/usr/lib/rpmio-4.3.so is not an ELF file
=================================================
I thought maybe this was limited to up2date or rpm, however, it worse.
If I type "ls", I get:
===================================================
ls: relocation error: /lib/i686/librt.so.1: symbol __librt_multiple_threads, \
version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference.
========================================================
The next thing I did which was probably a huge mistake!! I ran ldconfig,
oops:
ldconfig reports some bad things like so:
===========================================================
ldconfig:/lib/tls/librt.so.1 is not an ELF file - it has the wrong magic bytes
at the start.
===========================================================
The above happens with 541 or 533 kernel.
Has anyone else seen this? Is there a way arounf this avoiding a fresh
install?
--
Ernest L. Williams Jr.
SNS Control Systems Group
(865) 591-0183
ORNL
19 years, 7 months
Strang df -h output
by Harry Putnam
My setup:
*--
Software:
Linux kernel 2.6.7-1.517 Architecture i686
Fedora Core release 2.90 (FC3 Test 1)
Hardware:
model name : Intel(R) Pentium(R) 4 CPU 2.00GHz
cpu MHz : 1994.800
*--
I'm seeing output from `df -h' that I've never seen before. Not sure
when it started but I think it could only be a matter of days at most
since I last ran `df -h' for some reason.
Filesystem Size Used Avail Use% Mounted on
[...]
/dev/hda5 36G 20G 15G 58% /anex
none 253M 0 253M 0% /dev/shm
/dev/hdb9 7.6G 448M 6.7G 7% /home
/dev/hda2 15G -64Z 15G 101% /mnt/pack
/dev/hdb11 12G 4.6G 6.0G 44% /news
[...] some unnecessary stuff snipped
Note the strange output for /dev/hda2 (/mnt/pack)
What on earth does that mean?
That partition actually has 2.6 gigs of data on it by `du' reconning:
du -sh /mnt/pack
2.6G /mnt/pack
Its not a symlink or something:
ls -ld /mnt/pack
drwxr-xr-x 10 reader reader 4096 Sep 4 10:54 /mnt/pack
So what is that output telling me?
19 years, 7 months
Missing images/* in rawhide
by G.Wolfe Woodbury
Yesterday's update broke rawhide badly, the contents of the images/
directory (boot.iso and others) are gone!
Will tonight's rebuild fix it?
BTW; I couldn't boot the previous set of images, the X server froze with
no error indications on my test box. (AMD K6/2; ATI Mach 64; tulip
ethernet; standard IDE drives and CD-RW drive;320MB)
--
G.Wolfe Woodbury `- -'
RHCT U
The Line Eater is a boojum!
19 years, 7 months
Problem with today's "yum update"
by Mike Klinke
I'm guessing others will run into this with this morning's updates.
"yum update" errored out and quit with the display below.
============ yum error =============
Traceback (most recent call last):
File "/usr/share/yum-cli/yummain.py", line 139, in ?
main(sys.argv[1:])
File "/usr/share/yum-cli/yummain.py", line 94, in main
(result, resultmsgs) = base.buildTransaction()
File "/usr/lib/python2.3/site-packages/yum/__init__.py", line 130,
in buildTransaction
(rescode, restring) = self.resolveDeps()
File "/usr/lib/python2.3/site-packages/yum/depsolve.py", line 157,
in resolveDeps
(checkdep, missing, conflict, errormsgs) =
self._processConflict(dep)
File "/usr/lib/python2.3/site-packages/yum/depsolve.py", line 351,
in _processConflict
msg = '%s conflicts: %s' % (name,
rpmUtils.miscutils.formatRequire(needname, needversion, flags))
NameError: global name 'name' is not defined
=====================================
I filed a bug which was quickly marked as closed due to the problem
having been fixed in the version of yum that "yum update" was going
to download and install this morning. I manually downloaded the
new yum rpm and installed it. After running the new yum I then
received the error:
#yum update
.........
Resolving Dependencies
Error: xorg-x11-font-utils conflicts: xorg-x11-base-fonts<=
6.7.99.903-3
and after excluding "xorg-x11" the "yum update" then completed. I
presume that simply excluding "xorg-x11" would have allowed the yum
update with yesterday's version to complete. Hope this helps
someone else and I'm off to file a bug against "xorg-x11" if it
hasn't already been done.
Regards, Mike Klinke
19 years, 7 months
Nabi and gconf-editor problems
by Paul F. Johnson
Hi,
First off, how the fscking heck do I kill Nabi? I've tried going through
system-monitor and killing the process, but the darned thing just
restarts. Very annoying! (Yes, I've tried to quit it using the menu on
the app).
Second, gconf-editor seems to have died since moving to fc3t2. Anyone
else seen this?
TTFN
Paul
--
"Our enemies are innovative and resourceful - and so are we,"
"They never stop thinking about new ways to harm our country and our
people - and neither do we." - George W. Bush, Aug 2004
19 years, 7 months
update FC3T1 isos
by Harry Putnam
I think this question has been asked and answered but maybe my search
strings are taylored well enough to find it:
Are the iso's for FC3T1 ever updated to include the many updates
released since the first iso's were released?
That is, if one installs from the original FC3T1 iso's it is a long
row to get to the current updates... I wondered if the iso's are ever
updated to avoid that.
19 years, 7 months
Inodes, X and selinux w/ 541 kernel
by Jim Cornette
I just tried to boot my test installation using the 541 kernel and
recieved avc errors to the max and also could not start X. If I tried to
start X, it would freeze up at the switch to graphics portion, then do
nothing else.
Attached is the xorg.0.log which may have logged up to the point of the
computer hand.
I guess installing a clean FC2 version for this installation, then
trying FC3T2 is in the works for this system.
If interested in the avc errors, there are two messages on the selinux
list with the first boot errors, then an attempt to keep on going. (Time
to reinstall though)
Jim
--
You're at the end of the road again.
19 years, 7 months
