Bug #1437
Template fragments conflict in RPM upgrade
Status: | CLOSED | Start date: | ||
---|---|---|---|---|
Priority: | High | Due date: | ||
Assignee: | - | % Done: | 100% | |
Category: | nethserver-base | |||
Target version: | DEV133 | |||
Security class: | Resolution: | |||
Affected version: | DEV104 | NEEDINFO: |
Description
On RPM package upgrade the post-install script triggers the nethserver-*-update
event.
The update
event is executed BEFORE the old package has been cleaned up. Thus a template fragment conflict may occur if the new and the old package contain different template fragments.
The resulting template may contain old package fragments.
Related issues
History
#1 Updated by Davide Principi almost 9 years ago
- Project changed from 61 to 1
#2 Updated by Davide Principi almost 9 years ago
Proposal¶
Replace signal-event
in post rpm trans scriptlet with a command that
- check if event-queue is enabled
- enqueue the event call
Implement a yum plugin that enables the event-queue on yum pretrans
and fires the enqueued events on yum posttrans
hooks.
Using this approach
- The installation logic is still bundled within the RPM scriptlet
- The
rpm
command can be invoked directly and events are not executed - The events are still automatically fired during an automated update procedure
- There is no need to manage the events outside the package manager (yum) layer
#3 Updated by Davide Principi almost 9 years ago
- Target version changed from DEV104 to DEV133
#4 Updated by Davide Principi almost 9 years ago
- Assignee set to Giacomo Sanchietti
#5 Updated by Giacomo Sanchietti almost 9 years ago
- Status changed from NEW to 7
See: NethServer yum plugin and RPM package rules
#6 Updated by Davide Principi over 8 years ago
- Project changed from 1 to NethServer 6