Description of problem: Triggers like | %triggerin ... -- vpkg where 'vpkg' is the name of a virtual package (e.g. webserver), will not be executed. Version-Release number of selected component (if applicable): rpm-4.2.1-0.11 How reproducible: 100% Steps to Reproduce: 1. build rpms from attachement | rpmbuild -bb test1.spec 2. install packages | rpm -U test1-1-1.noarch.rpm test1-A-1-1.noarch.rpm 3. cat /root/test-trigger Actual results: cat: /root/test-trigger: No such file or directory Expected results: 'Trigger fired for test1-data'
Created attachment 92391 [details] spec-file
Hmmm, this is actually an RFE, as triggers are traditionally fired by package name, not provide name. I've achieved triggers fired by providename, but more than a little testing needs to happen before I commit.
Fixed for quite some time. This is rpm-4.4.5 behavior: [jbj@wellfleet test1]$ sudo rpm -Uvh *h.rpm Preparing... ########################################### [100%] 1:test1-A ########################################### [ 50%] 2:test1 ########################################### [100%] Trigger fired for test1-A