Bug 920615 - Question about %gconf_schema_upgrade
Summary: Question about %gconf_schema_upgrade
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: GConf2
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-12 12:56 UTC by Michael Schwendt
Modified: 2013-09-02 07:00 UTC (History)
4 users (show)

Fixed In Version: 3.2.6-3
Clone Of:
Environment:
Last Closed: 2013-09-02 07:00:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
suggested patch (825 bytes, patch)
2013-03-12 12:56 UTC, Michael Schwendt
no flags Details | Diff

Description Michael Schwendt 2013-03-12 12:56:04 UTC
Created attachment 708949 [details]
suggested patch

Description of problem:
http://lists.fedoraproject.org/pipermail/test/2013-March/114215.html

> https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#GConf
 
Why does %post run --makefile-uninstall-rule for the new .schemas file? Shouldn't it use the old copy from the previous package release that was saved in %pre in /var/lib/rpm-state/gconf? 

Attached patch shows what I mean.

Comment 1 Fedora End Of Life 2013-04-03 17:30:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 2 Ray Strode [halfline] 2013-04-11 14:11:10 UTC
You're right, we should fix this.

Comment 3 Tom "spot" Callaway 2013-04-11 14:15:01 UTC
The guidelines just say "%gconf_schema_upgrade schema1 schema2", you can correct the inner macros to reflect the proper upgrade behavior as you need to.


Note You need to log in before you can comment on or make changes to this bug.