Product

Overview

How it works Watch it work All 35 features Screenshots How ForgeRepo™ is secured

Keep bad packages out

Malware scanning Typosquat detection Dependency confusion protection Cooling off new releases Allow lists and block lists

When something goes wrong

Kill switch Who has it Lockdown and degraded modes Vulnerability monitoring

Developers and approvals

Requests and auto approve Check, walk and review Waivers Dry run
Formats

Languages

Private npm registry PyPI proxy and private index Private NuGet feed and proxy Maven repository proxy RubyGems mirror Composer and Packagist proxy

Apple, containers and Linux

CocoaPods CDN mirror Swift package registry Docker registry mirror RPM mirror for dnf and yum APT mirror for Debian and Ubuntu

Use it as

An npm firewall Artifacts, SBOMs and lifecycle More than one node SSO, roles and allow lists
Learn

Guides

Learn secure development Secure coding Secure pipelines Unsafe vs safe Security and development

Supply chain

Supply chain attacks, 2016 to 2026 Software supply chain security
Compare Side by side, all four ForgeRepo™ vs JFrog ForgeRepo™ vs Sonatype ForgeRepo™ vs Cloudsmith
Docs

Start

Getting started Download All documentation Questions

For developers

npm setup pip setup docker login Push a Docker image CI basics

For administrators

First setup Rules and their order Six incidents, walked through Backup and upgrade
Pricing Install it
  1. Home
  2. Documentation
  3. Developer Guide
  4. When dnf cannot get a package

Linux packages (dnf and yum)

When dnf cannot get a package

A package the rules refuse is either not listed or refused on download.

dnf only shows the status code of a refusal, not the reason:

What a package the rules refuse looks like
$ dnf install -y zsh
...
Downloading Packages:
[MIRROR] zsh-5.8-9.el9.x86_64.rpm: Status code: 403 for https://packages.example.com/rpm/almalinux-9-baseos/Packages/zsh-5.8-9.el9.x86_64.rpm (IP: 10.100.138.3)
Error: Error downloading packages:
  zsh-5.8-9.el9.x86_64: Cannot download, all mirrors were already tried without success

Captured by running these commands against a real ForgeRepo™.

The refusal already opened a request. Open the address dnf printed in a browser, or look on the Requests page, to see why.

Note

On a mirror that hands out a filtered index, a refused package is not listed at all, so dnf says No match for argument.