Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hi, fresh packages might be getting to you later for few reasons:

  1. cache haven't expired since last metadata download, so dnf haven't checked if newer one is available
  2. use --refresh parameter to force checking if newer metadata is available;
  3. shorten metadata expiration time by adding/changing metadata_expire=time_in_seconds in /etc/dnf/dnf.conf
  4. updates haven't yet propagated to mirrors you're using - try forcing other mirrors just for that update (replace some-mirror-address):
  5. for updates use dnf update --repofrompath updates-mirror,http://some-mirror-address/fedora/linux/updates/$(rpm -E %fedora)/$(arch)/
  6. for updates-testing use dnf update --repofrompath updates-testing-mirror,http://some-mirror-address/fedora/linux/updates/testing/$(rpm -E %fedora)/$(arch)/.

If updates are not yet in testing, you can download packages manually from https://koji.fedoraproject.org/koji/ and install them with dnf.

If you use dnf with -v parameter, it will print some useful info, e.g. metadata creation timestamp, whether metadata cache is used.

Hi, fresh packages might be getting to you later for few reasons:

  1. cache haven't expired since last metadata download, so dnf haven't checked if newer one is available
  2. available
    • use --refresh parameter to force checking if newer metadata is available;
    • shorten metadata expiration time by adding/changing metadata_expire=time_in_seconds in /etc/dnf/dnf.conf
  3. updates haven't yet propagated to mirrors you're using - try forcing other mirrors just for that update (replace some-mirror-address):
  4. ):
    • for updates use dnf update --repofrompath updates-mirror,http://some-mirror-address/fedora/linux/updates/$(rpm -E %fedora)/$(arch)/
    • for updates-testing use dnf update --repofrompath updates-testing-mirror,http://some-mirror-address/fedora/linux/updates/testing/$(rpm -E %fedora)/$(arch)/.

If updates are not yet in testing, you can download packages manually from https://koji.fedoraproject.org/koji/ and install them with dnf.

If you use dnf with -v parameter, it will print some useful info, e.g. metadata creation timestamp, whether metadata cache is used.

Hi, fresh packages might be getting to you later for few reasons:

  1. cache haven't expired since last metadata download, so dnf haven't checked if newer one is available
    • use --refresh parameter to force checking if newer metadata is available;
    • shorten metadata expiration time by adding/changing metadata_expire=time_in_seconds in /etc/dnf/dnf.conf
  2. updates haven't yet propagated to mirrors you're using - try forcing other mirrors just for that update (replace some-mirror-address):
    • for updates use dnf update --repofrompath updates-mirror,http://some-mirror-address/fedora/linux/updates/$(rpm -E %fedora)/$(arch)/
    • for updates-testing use dnf update --repofrompath updates-testing-mirror,http://some-mirror-address/fedora/linux/updates/testing/$(rpm -E %fedora)/$(arch)/.

To install or update package which is currently in testing, append --enablerepo=updates-testing to appropriate dnf command.

If updates are not yet in testing, you can download packages manually from https://koji.fedoraproject.org/koji/ and install them with dnfdnf install path_to_.rpm_package.

If you use dnf with -v parameter, it will print some useful info, e.g. metadata creation timestamp, or whether metadata cache is being used.

Hi, fresh packages might be getting to you later for few reasons:

  1. cache haven't expired since last metadata download, so dnf haven't checked if newer one is available
    • use --refresh parameter to force checking if newer metadata is available;
    • shorten metadata expiration time by adding/changing metadata_expire=time_in_seconds in /etc/dnf/dnf.conf
  2. updates haven't yet propagated to mirrors you're using - try forcing other mirrors just for that update (replace some-mirror-address):
    • for updates use dnf update --repofrompath updates-mirror,http://some-mirror-address/fedora/linux/updates/$(rpm -E %fedora)/$(arch)/
    • for updates-testing use dnf update --repofrompath updates-testing-mirror,http://some-mirror-address/fedora/linux/updates/testing/$(rpm -E %fedora)/$(arch)/.

Testing updates

To install or update package which is currently in testing, append --enablerepo=updates-testing to appropriate dnf command.

Each update's page on https://bodhi.fedoraproject.org/ contains a code snippet (section "How to install") allowing to easily install it.

If updates are not yet in testing, testing (or not yet propagated to mirrors - previous commands didn't find updates to install), you can download packages from https://koji.fedoraproject.org/koji/builds

  • automatically cd $(mktemp -d) && koji download-build --arch=x86_64 kernel-4.20.12-200.fc29 && dnf update * where kernel-4.20.12-200.fc29 is an NVR (name-version-release) from koji
  • manually from https://koji.fedoraproject.org/koji/ and install them with dnf install path_to_.rpm_package.

If you use dnf with -v parameter, it will print some useful info, e.g. metadata creation timestamp, timestamp (you can compare it with https://bodhi.fedoraproject.org/masher/ to check whether you already have the latest one), or whether metadata cache is being used.