2009/6/18 cornel panceac <cpanceac(a)gmail.com>:
2009/6/16 cornel panceac wrote:
>
> is there a way to check this? or is this documented anywhere?
# sudo yum update
Loaded plugins: refresh-packagekit
adobe-linux-i386
| 951 B
rpmfusion-free-updates
| 3.8 kB
rpmfusion-free-updates-testing
| 3.8 kB
rpmfusion-nonfree-updates
| 3.8 kB
rpmfusion-nonfree-updates-testing
| 3.8 kB
updates/metalink
| 9.2 kB
updates
| 4.4 kB
updates/primary_db
| 1.4 MB
updates-testing/metalink
| 6.5 kB
updates-testing
| 4.0 kB
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package gdb.i586 0:6.8.50.20090302-27.fc11 set to be updated
---> Package gnome-settings-daemon.i586 0:2.26.1-7.fc11 set to be updated
---> Package gstreamer.i586 0:0.10.23-2.fc11 set to be updated
---> Package gstreamer-tools.i586 0:0.10.23-2.fc11 set to be updated
---> Package libpng.i586 2:1.2.37-1.fc11 set to be updated
---> Package orca.i586 0:2.26.2-2.fc11 set to be updated
---> Package vlgothic-fonts.noarch 0:20090612-1.fc11 set to be updated
---> Package vlgothic-fonts-common.noarch 0:20090612-1.fc11 set to be updated
Ok, you can see here, in this typical yum output the following things:
1. I use rpmfusion and flash. Which is bad.
2. The size of downloaded files for rpmfusion and updates-testing are less than 10K. These
are small files with meta repository information. So the repo was checked but it
hasn't changed since the last time yum checked it.
3. After checking the 'updates' repo yum sees that the repo was updated so it
downloads the whole package database in updates (primary_db)
4. After some calculations some packages are set to be updated.
If you need more proof check the yum source it's mostly python, so it's easy to
read.
--
NV