When updating a package I came across this "Error in PREUN scriptlet in rpm package".
Now further inspection revealed that there was a misplaced semicolon in %preun section of the relevant spec file.
Easily fixable but what is the proper procedure to fix this via update without having the user having to go to a terminal and run rpm -e --noscripts $oldpackage to remove the old package?
JBG
On 01/21/2012 01:06 PM, "Jóhann B. Guðmundsson" wrote:
When updating a package I came across this "Error in PREUN scriptlet in rpm package".
Now further inspection revealed that there was a misplaced semicolon in %preun section of the relevant spec file.
Easily fixable but what is the proper procedure to fix this via update without having the user having to go to a terminal and run rpm -e --noscripts $oldpackage to remove the old package?
Given the lack of response I assume that there is no proper way to handle this other than forcing users of the particular component to manually remove the relevant package after that update has been pushed.
JBG
On Sun, Jan 22, 2012 at 09:15:49AM +0000, "Jóhann B. Guðmundsson" wrote:
On 01/21/2012 01:06 PM, "Jóhann B. Guðmundsson" wrote:
When updating a package I came across this "Error in PREUN scriptlet in rpm package".
Now further inspection revealed that there was a misplaced semicolon in %preun section of the relevant spec file.
Easily fixable but what is the proper procedure to fix this via update without having the user having to go to a terminal and run rpm -e --noscripts $oldpackage to remove the old package?
Given the lack of response I assume that there is no proper way to handle this other than forcing users of the particular component to manually remove the relevant package after that update has been pushed.
You might be able to use a trigger or posttrans to fix it.
On 01/22/2012 02:51 PM, Chuck Anderson wrote:
On Sun, Jan 22, 2012 at 09:15:49AM +0000, "Jóhann B. Guðmundsson" wrote:
On 01/21/2012 01:06 PM, "Jóhann B. Guðmundsson" wrote:
When updating a package I came across this "Error in PREUN scriptlet in rpm package".
Now further inspection revealed that there was a misplaced semicolon in %preun section of the relevant spec file.
Easily fixable but what is the proper procedure to fix this via update without having the user having to go to a terminal and run rpm -e --noscripts $oldpackage to remove the old package?
Given the lack of response I assume that there is no proper way to handle this other than forcing users of the particular component to manually remove the relevant package after that update has been pushed.
You might be able to use a trigger or posttrans to fix it.
Thanks I will try that
JBG
Jóhann B. Guðmundsson wrote:
When updating a package I came across this "Error in PREUN scriptlet in rpm package".
Now further inspection revealed that there was a misplaced semicolon in %preun section of the relevant spec file.
Easily fixable but what is the proper procedure to fix this via update without having the user having to go to a terminal and run rpm -e --noscripts $oldpackage to remove the old package?
I guess one question is ... does this bad preun script cause problems when doing a pkg ugprade? If not, you're ok. If yes, then you're likely stuck with the "rpm -e --noscripts" approach.
-- rex
packaging@lists.fedoraproject.org
-
Chuck Anderson -
Jóhann B. Guðmundsson -
Rex Dieter