Undefined %epoch problem (Re: rawhide report: 20150730 changes)

[Michael Schwendt]

On Thu, 30 Jul 2015 12:42:29 +0000, Fedora Rawhide Report wrote:

> Broken deps for x86_64

Surprisingly, the report is incomplete and doesn't find some unresolvable
dependencies. DNF doesn't either.

An undefined %{epoch} in a dependency is not found. This has been reported
to blktap: https://bugzilla.redhat.com/1248912

Note how DNF tells "Dependencies resolved", but later fails during the
transaction check. How could it resolve the unexpanded "%{epoch}" earlier?

$ rpm -qpR blktap-devel-3.0.0-3.fc23.git0.9.2.x86_64.rpm |grep ep
blktap(x86-64) = %{epoch}:3.0.0-3.fc23.git0.9.2

$ dnf install blktap-devel
Waiting for process with pid 2683 to finish.
Fedora - Rawhide - Developmental packages for t 1.3 MB/s |  43 MB     00:32    
Last metadata expiration check performed 0:00:17 ago on Fri Jul 31 09:33:49 2015.
Dependencies resolved.
================================================================================
 Package           Arch        Version                       Repository    Size
================================================================================
Installing:
 blktap            x86_64      3.0.0-3.fc23.git0.9.2         rawhide      245 k
 blktap-devel      x86_64      3.0.0-3.fc23.git0.9.2         rawhide       21 k

Transaction Summary
================================================================================
Install  2 Packages

Total download size: 266 k
Installed size: 793 k
Is this ok [y/N]: y
Downloading Packages:
(1/2): blktap-devel-3.0.0-3.fc23.git0.9.2.x86_6 213 kB/s |  21 kB     00:00    
(2/2): blktap-3.0.0-3.fc23.git0.9.2.x86_64.rpm  956 kB/s | 245 kB     00:00    
--------------------------------------------------------------------------------
Total                                           202 kB/s | 266 kB     00:01     
Running transaction check
Error: transaction check vs depsolve:
blktap(x86-64) = %{epoch}:3.0.0-3.fc23.git0.9.2 is needed by blktap-devel-3.0.0-3.fc23.git0.9.2.x86_64
To diagnose the problem, try running: 'rpm -Va --nofiles --nodigest'.
You probably have corrupted RPMDB, running 'rpm --rebuilddb' might fix the issue.