Closed #386 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/386#event-12610248521
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint
With the above said, I'm going to close this issue now. We also plan to improve
the documentation for triggers in general (via #2860) so that should help avoid
the confusion in the future.
--
Reply to this email directly or view it on GitHub:
As mentioned above, this is indeed expected behavior; when the trigger source
is part of the transaction, the trigger is also activated, and is fed *all* the
matching prefixes. It's analogous to *all* the packages shipping files in the
`/` prefix being part of the transaction.
That said, I can
Reopening for tracking in file trigger spec revise (whenever that will happen)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Reopened #386.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/386#event-3823454237___
Rpm-maint mailing list
Documentation says "for all installed packages that contained...", nowhere does
it say installed in *this* transaction.
The "obvious" reason(s) for the behavior is that when installing the package
containing the trigger, you want to get it to do its thing on the packages that
are already
> %transfiletriggerin: Executed once after transaction for all installed
> packages that contained file(s) that matches prefix of this trigger. Also
> executed after transaction if there was a package containing this file
> trigger in that transaction and there is/are some files(s) matching
Why would you run ldconfig (for example), if there was no library installed /
changed during transaction? Just to be sure?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> and installed package set
this doesn't make any sense for me...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #386.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/386#event-1471178645___
Rpm-maint mailing list
Hmm, actually I don't think this is a bug afterall: file triggers match files
from the current transaction *and* installed package set, just like regular
triggers do. And prefix / happens to match all installed files. It'll seem more
sensible with a more reasonable prefix.
--
You are
Yay, more file trigger bugs.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/386#issuecomment-361631951___
Rpm-maint mailing
This needs to be gated by an option, in case the command being run doesn't
expect any data on standard input and exits before completely reading all input.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
If spec happens to have something like:
```
%transfiletriggerin -- /
cat
```
It would dump all files on filesystem instead of showing what's really in
transaction. I don't think that it was done in this way by design.
--
You are receiving this because you are subscribed to this thread.
Reply
14 matches
Mail list logo
