Is there a reason for `runImmedFileTriggers` not to chroot?
---
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/43#issuecomment-170393488___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lis
On 10 January 2016 at 10:35, Thierry Vignaud wrote:
Sadly, the current filetriggers doesn't honour rpm's chroot.
Thus it works fine with our rpm front-end (urpmi which is like yum/dns
for FC) for online updates.
But not with our installer (Drakx) which installs packages in
fix file triggers
which are otherwise broken when using a chroot (which is the case of a DVD
installer such as DrakX or Anaconda, or when using urpmi with either --root or
--urpmi-root option)
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-mana
Closed #41.
---
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/41#event-510445132___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
fix file triggers
which are otherwise broken when using a chroot (which is the case of a DVD
installer such as DrakX or Anaconda, or when using urpmi with either --root or
--urpmi-root option)
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-man
fixes file triggers
which are otherwise broken when using a chroot (which is the case of a DVD
installer such as DrakX or Anaconda, or when using urpmi with either --root or
--urpmi-root option)
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-ma
On 9 January 2016 at 22:48, Thierry Vignaud wrote:
>>> Sadly, the current filetriggers doesn't honour rpm's chroot.
>>> Thus it works fine with our rpm front-end (urpmi which is like yum/dns
>>> for FC) for online updates.
>>>
>>> But not with our installer (Drakx) which installs packages in a chr
