Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#26486 - [virtualbox] backup /etc/vbox/vbox.cfg when installing

Attached to Project: Community Packages
Opened by Shanto (Shanto) - Monday, 17 October 2011, 12:46 GMT
Last edited by Ionut Biru (wonder) - Wednesday, 02 November 2011, 06:46 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Ionut Biru (wonder)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I have some custom variables in /etc/vbox/vbox.cfg, but every time virtualbox gets an update, this file is overwritten by pacman. Is it possible to cover this file with a "backup =" clause in the PKGBUILD?
This task depends upon

Closed by  Ionut Biru (wonder)
Wednesday, 02 November 2011, 06:46 GMT
Reason for closing:  Implemented
Additional comments about closing:  4.1.4-4
Comment by Alexander F. Rødseth (xyproto) - Monday, 17 October 2011, 15:46 GMT
Does the upgrade also make a file named /etc/vbox/vbox.cfg.pacsave?
Comment by Karol Błażewicz (karol) - Monday, 17 October 2011, 15:52 GMT
I doubt it as it's not in the backup array (virtualbox has no backup array at all http://projects.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/virtualbox) and if it did, why would it overwrite the file anyway?
Comment by Shanto (Shanto) - Monday, 17 October 2011, 15:53 GMT
No. As far as I understand, a pacsave will be created only if you have necessary instructions regarding the file (to keep/save) in PKGBUILD.
Comment by Shanto (Shanto) - Monday, 17 October 2011, 15:55 GMT
@karol You are right. Thats the point of my bug report. I think, vbox.cfg should be put in the backup array.
Comment by Alexander F. Rødseth (xyproto) - Monday, 17 October 2011, 15:58 GMT
Ok, assigned the bug.
Comment by Shanto (Shanto) - Tuesday, 01 November 2011, 23:47 GMT
I wonder if there's any complication in applying this little fix. Wanted to make sure that the next vbox update doesn't brake all of my installations again. :(

@wonder: I hope this bug is within your radar, isn't it? It's alright if we are holding for the next release (to save bandwidth, huge compilation time of vbox, or such). Otherwise, please put a very very small chunk of your time on this. Don't recompile, just repackage, maybe?
Comment by Ionut Biru (wonder) - Tuesday, 01 November 2011, 23:48 GMT
i forgot
Comment by Shanto (Shanto) - Wednesday, 02 November 2011, 00:11 GMT
Glad I bumped it :)
- which I try not to do.

Loading...