Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 185412 - net-misc/asterisk-1.2.* removes unmodified config files on upgrade
Summary: net-misc/asterisk-1.2.* removes unmodified config files on upgrade
Status: RESOLVED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Tony Vroon (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-15 13:37 UTC by Miroslav Šulc
Modified: 2009-04-16 15:48 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Don't clobber configuration files upon upgrade (asterisk-1.2.27-doins.patch,929 bytes, patch)
2009-02-23 06:52 UTC, kfm 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Miroslav Šulc gentoo-dev 2007-07-15 13:37:51 UTC 
When upgrading asterisk (the last time it was to net-misc/asterisk-1.2.21.1 but it happened with the previous version too), not modified config files are removed from /etc/asterisk/ and asterisk cannot be started then. I talked about it with cardoe on irc and it came out that the problem is that asterisk ebuild relies on a bug in older portage where the config files were not removed. Unfortunately with newer versions of portage (I have sys-apps/portage-2.1.3_rc8) it works as described above.

So the solution would be to install config files in /etc/asterisk/ even on upgrades.
Comment 1 Gustavo Zacarias (RETIRED) gentoo-dev 2007-07-16 12:42:43 UTC 
Patches welcome!
Comment 2 kfm 2009-02-23 06:52:03 UTC 
Created attachment 182858 [details, diff]
Don't clobber configuration files upon upgrade
Comment 3 Mounir Lamouri (volkmar) (RETIRED) gentoo-dev 2009-04-16 15:12:00 UTC 
Reassigning to chainsaw as he is now the asterisk maintainer.
Comment 4 Tony Vroon (RETIRED) gentoo-dev 2009-04-16 15:48:38 UTC 
I believe this is no longer an issue in 1.2.32 which is currently in the tree. Should you disagree, could you please reopen this bug. Thank you.